SnapCenter restore issue

[bogdan]

Hello,

Anyone can help with the below errors message in Snapcenter version 4,when i try to make a restore?

The Secondary backups aren’t showing up in the restore wizard because when I mark the secondary storage system as ‘Secondary’ it does not seem to save the setting as the tick box is clear when I go back to check.

The guest file restores fail with:

‘Error: Failure while attaching disk to guest: Unable to mount datastores:....... in Backup: 13.Failed to create volume clone for volume 10......... ‘

and

‘Error: Failed to create the volume clone. Cannot create volume. Reason: aggregate'' name '' is not in aggr-list of Vserver ''name’'

I have configured the restore and backup Run As Credentials as per the instructions but it looks like it’s a security rights issue.

Thank you

[Spaceball]

try using storage configuration without having the checkbox "secondary" checked for dp-svm.

This checkbox is not relevant in sc4.0, as your primary storage "knows" it's dp/xdp svm by NetApp config.

This parameter/checbox will be removed in sc4.1

[bogdan]

Hello, It’s always unchecked ,already grey out for me

[matte · Accepted solution]

Hi

i think you've already found the issue. You cannot create a clone.. hence the restore fails.

aggregate xxx is not in aggr-list of Vserver xxx.     
 
means you need to add the aggregate in the aggr list of the vserver
The aggr-list is a parameter that defines the list of aggregates assigned to a Vserver. This parameter is used only for aggregate-related volume provisioning operations. When a Vserver is created, it has an empty aggr-list, which means that the Vserver administrator cannot perform any volume provisioning operations. If the aggr-list of a Vserver is empty or does not contain the proper vserver list you cannot perform any provisioning operations that require an aggregate name. For example, volume create and flexclone create (the availability of these commands depends on the role assigned to the Vserver administrator).  The operation is not disruptive, and with that basically you allow the clone operation required by the mount-sdsnapshot command
 
 
Current aggregate assignments can be viewed by running this command from the Cserver:
cserver::> vserver show -vserver verservername

Look for the line that shows List of Aggregates assigned.
Then you need to assign the aggregates specified in the error message to the vserver in question. (This might give a warning that the aggregate is in use with other vservers, this can be safely ignored. This command only allows the vserver in question the ability to perform operations such as FlexClone.)
>From the Cserver command line:

cserver::> vserver modify -vserver vservername -aggr-list aggrname
 
obviously if you prefer you can do that via onCommand GUI