i am having this issue wherein the VM level backup for this one VM is failing “The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. Please check the available free space and status of the volume being protected.” Other VMs are fine. we are on SP22 ; unfortunately this has just gone out of support; however we are booking at time to upgrade to SP24; although I am not sure if being on SP22 affects the backup as other VMs are working okay. Although support did advise that if we do not upgrade; they would not be able to troubleshoot the issue further.
I am trying to setup backup for TrueNAS device which hosts both CIFS and NFS share. Looking at the NAS backups; it appears NDMP is not supported. I have a Windows proxy that can talk to the NAS device and can be used as a point to protect CIFS share; as I understand for NFS I would need to setup a linux VM. I noticed TrueNAS also has snapshot support; it is possible to leverage that?
we are helping a customer restore data from their old commserve envrioment; we had a VM level backup for the commserve; we restored it the services are working; however the credentials supplied by the customer is not working. Is there a way around it?' commvault sevrices appear to be working okay (looked at the Simpana services console; everything is showing as running)Also, is there a log file that I can check what’s going on. SQL is installed on the same VM. Also, becuase this was a old commvault system and required to be stood up to look for historical data; can we raise it with support team
This could be totally unrelated; however recently we upgraded our Commcell to 11.22.17 last week Thrusday; we pushed the MediaAgent and client upgrade this week on Monday; we are seeing increase VM level quiescing warning across different customers; the only change that seem to have happened is upgrade of Commvault VADP proxy; I know quiescing process is outside of Commvault; and we are asking customer to check their VMWARE environment however it is a bit wired that this issue started occuring after the change we made at the proxy
I was looking at the data size by client on a MA via Commvault console; saw somthing wired that file system backups were consuming few TBs of data although the customer’s file sytem was pretty small. Investigated further and it appears that none of the DDB backups are not pruned or removed since the Mediaagent was deployed last year, so all this TB of data on the MA belongs to DDB backups. Could not see any reason why that should be the case; there is only one active DDB for that MA
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.