Quantcast
Channel: All Data Protection posts
Viewing all articles
Browse latest Browse all 3485

Re: SnapCenter issues and questions

$
0
0

Hey Neerajd,

 

Thanks for the offer of assistance, I won't turn that down! I have VM quiesced backup jobs configured on production clusters running CDOT 8.3.1 to protect NFS datastores hosting mostly VMs with archive/Snapvault setup to a dedicated 8.3.2 CDOT cluster. Using SnapCenter 1.0.1 for policies integrated into VSC in order to apply Snapmirror labels/Netapp Protection policies to retain these VM consistent snapshots on said archive storage. It worked ok initially but I think as load has increased/client migrated more data to CDOT systems they have begun to fail with various errors.

 

1. Failed on 'SNAPCENTERVMNAME'. Activity 'Discovering Resources# failed with error: Discover resource enumeration returns null or emtpy

2. Failed on 'SNAPCENTERVMNAME'. Activity 'Unquiescing Applications' failed with error: The operation has timed out

3. Failed on 'SNAPCENTERVMNAME'. Activity 'Creating Snapshot' failed with error: Create snapshot "Snapname" failed: Error: The credentials for the storage system 4. STORAGESYSTEMNAME.domain.com is not configured.. Activity 'Unquiescing Applications' failed with error: the operation has timed out.

 

I had occurance of error #3 yesterday across most jobs that ran after 11PM, ones running before and one after 8AM for the SnapCenter VM Solely/without Snapvault completed ok. I checked the credentials in both VSC and SC and they were good as expected. I restarted the OnCommand service on the VSC server and restarted the SnapCenter services and it has not reoccured today but some have now failed with error #1. Yestesterday I also reviewed each of the 7 jobs containing 34 datastores in total with Snapvault setup suffering issues and checked schedules due to the above regarding some failing/some completing. I tweaked some where the jobs overran/were running at the same time; however the SnapCenter machine was not busy according to vSphere data it was just encase it helped. Does this sound like it helped or was this a temporary error do you think?

Regarding todays failure for 3 jobs suffering error #1, coincidently yesterday I noticed while trying to edit alert settings for these jobs and another one that is now completing successfully that I cannot save settings due to error "Select the compatible entities for BACKUPJOBNAME Backup Job", for the one job of these which is now working; I removed datastores until I found one that it was complaining about and allowed me to save the job config after removing but I cannot add it back due to the same error. It is an NFS datastore and is available so I'm not sure where to go if you could help with this?

 

Thanks,

Gareth

 

 

 

 


Viewing all articles
Browse latest Browse all 3485

Trending Articles