SnapCreator and Protection Manager using default pm backup policy behavior

[olson]

NTAP_PM_UPDATE=Y

NTAP_DFM_DATA_SET=orion:snapcreator_test/oriontest1,oriontest2

NTAP_PM_RUN_BACKUP=Y

     Snap creator appears to only grabs the first relationship per volume to update. It this by design and is there any way to force it to grab multiple relationships per volume?

the volume oriontest1 has two vault relationships one to non-qtree data - and one to a qtree within the volume.

[ktenzer]

This sonds like configuration issue in the dataset. What you need to do is make sure the qtrees are in the dataset not the volume, this means non-qtree qtree "-". My guess is that in the dataset you have the volume itself and the qtree and that PM is only vaulting the qtree not non-qtree. What you should have is the "-" which represents non qtree data and the qtree.

Snap Creator will read the dataset members, you should see this in the output. Snap Creator should read the non-qtree-data and the the qtree and then register the snapshot with those members. Can you also send output of the logfile, this would show if dataset members are registered correctly?

For a workround solution you can have SC do the snapvault if you want to. Just turn on NTAP_SNAPVAULT_UPDATE=Y and set SNAPVAULT_VOLUMES to whatever you have in VOLUMES.

Regards,

Keith

[olson]

Keith,

          I have one more follow on question. Is it a requirement to have snapcreator create the dataset or can I use a existing policy to manage the backup archives?

Thanks Again,

John

[ktenzer · Accepted solution]

Hi John,

Yes is is a requirement that SC create dataset either through GUI or CLI. The dataset which SC creates is an application dataset. PM will not acknowledge SC snapshots unless the dataset is application dataset.

SC will create a blank dataset so you should be able to re-build it quickly.

Here is a video on how to do this in GUI using existing relationships:

https://communities.netapp.com/videos/1998

Regards,

Keith