I'm implementing a scripted solution aiming to handle backups of SAN attached hosts running Windows. There are a number of sample scripts out there, but I'd like to integrate this with Protection Manager for error reporting and simplified management. I'm quite aware I need to schedule local snapshots through snapdrive, I won't be able to schedule backups from PM since they would be controller based and thus inconsistent.
The "sdcli dataset" command set is showing a fair bit of promise, despite the deafening lack of documentation. I've done an empirical study of many of the available sub commands and have arrived at a solution that will:
Create a new dataset for each new physical host.
Populate the dataset with all available mount points. This will lead to the automatic creation of relevant snapvault relationships.
Register a new backup version in Protection Manager
Take local (consistent) snapshots of all mountpoints.
Transfer the snapshots to the snapvault location.
Close the backup version and ending the backup job.
Have Protection Manager handle retention of both primary and secondary snapshots (This I need to verify when the retention period is over).
There's really only one thing missing. When I create a new dataset, I can apply a policy from the sdcli command line, but I've not been able to find out how to add a resource pool to the dataset. If I can't, the handling is a bit clumsy. The new dataset is created, and then the operator has to be notified to add a resource pool. I suppose I could work a bit with the dfpm dataset command options from the DFM server itself, but I'd rather avoid having to open up for remote commands from every physical host and it's dog to the DFM server. This is a highly segmented network with several firewalls.
Any insight on this? Just this bit missing, and then I'd be happy.
I'm very interesting about this post. I'm experiencing the same situation about inconsitent snapshot in SnapDrive, because scheduled from PM.
I have a windows files server with boot on SAN Netapp lun, and another mapped lun for file sharing. SnapDrive 6.3 is installed on this server and worked fine for provsionning, connect/disconnect/resize lun/disk....
I have also OnCommand 5 installed at a remote secondary location (another active directory domain), with secondary FAS for my snapvault relatioships.The dataset was created from PM and schedule policy is applied to this dataset. The job work fine. SnapDrive detect the snapshot, but they appear inconsistant. Is because PM "discuss" directely with primary FAS and PM is not aware of the installation of snapdrive? or it's a missconfiguration issue ? I added the DFM server/credential during the installation of snapdrive on my file server.
When I expend snapshot copie of my LUNs in snapdrive, I can see the primary and secondary snapshots, so snapdrive seems to be aware of the snapvault relatioship and the secondary FAS.
What about RBAC? Do I need implement RBAC because of the separate active directory domain ? It's a user right issue?
How can I do consistent snapshot from Oncommand without script, but directly from PM ?
sdcli.exe snap create -m <hostname> -s sd_daily.0 -D e
=== Option 2 (Using Snap Creator integration)
Snap Creator as an external application has the ability to create datasets and manage retention.
Another confusing option would be to leverage sdcli script above in addition to Snap Creator "External snap" option within the profile to register snapshots to the dataset which then allows for dfpm to manage retention.