I figured out how to setup the SMSQL5.0 snapvault integration with Protection Manager (4.0). I used a combination of the TR-3768 and the SMSQL 5.0 Installation and configuration Guide. In the TR there was stated to select the protection policy "Remote Backups Only". Strange enough this policy has by default a throthle "Nightly Transfer Window", that prevents transfer during office hours and therebye the conformance failed. This was solved through changing the throthle to None.
My question: Is the snapvault transfer initiated by the snapmanager or by the protection manager ? If it is the first, what does the schedule from the PM do then ? If it is the last, doesn't this result in inconsistent snapshots ?
SMSQL quieces the database(s) then takes a snapshot on the primary using Snapdrive. It then uses Snapdrive to communicate with Protection Manager which then starts the snapvault transfer using the snapshot on the primary just taken.
You can define your own protection policy that doesn't have a throttle set. It just has to be a policy that does the equivalent of "remote backup only".
I KB58272 they say that the user that connects the OM should have GlobalFullControl. I gave the user the role GlobalDataProtection. This was enough to let the user create the data set and I thought it would be enough to get the protection rolling (role details: manage backups and datasets). Probably this is not enough, so I will change the role to GlobalFullControl.
I find this really drastic (why did they implemented the rbac then in the first place) and this isn't (good) documented in the install/administration guide or best practices !
The backup retention change is for trial, because at this time I only have my snapvault comming over to the second tier, but no retention at all. I set no throttle (not needed) and had set a daily schedule at 1PM. This is actually the time the snapvault is triggered at this moment. Since we want the snapmanager to trigger it, I changed it to a new one "Monthly - No schedule" !
If I look at the job overview in PM I see this for the data set: Could not find any backups to transfer on Primary data node of application dataset SnapMgr_SQLServer_RMGINFRA01(20434).
If I check it on the dfm server:
C:\>dfpm backup list SnapMgr_SQLServer_RMGINFRA01 There are no backups.
From what I read in the doc kb58938, I should see at least one or more entries like these here (even if the snapvault transfer doesn't work):
10121 02 Jun 2010 01:15:20 unlimited Primary data 06-02-2010_01.14.49
If I snap list one of the volumes on the primary that are part of the data set, I see the following snapshots:
roesnap1> snap list rmginfra01data Volume rmginfra01data working...
We had our backup jobs already running (created before integration with PM took place). It wasn't described in the Best Practices either, but you have to change the backup job to. It doesn't ends after integration is finished !
If you create a new job with Backup Wizard, at Verification Settings tab there is a section Backup Archiving Options, where you must select "Archive Backup to Secondary Storage" (see picture attached). It's that simple !
Hopefully this will help ohter people that want to integrate snapmanager - snapdrive with Protection Manager.