[2013-12-05 13:51:35,638] ERROR: SCF-00019: SnapVault relationship for [sv01]:[cmexch02_data02_vault001] does not exist, Exiting!
Both primary and vault Vservers are resolvable from the Snap Creator server host (through DNS). Lower case are used everywhere. Vserver names and volumes have been specified using Snap Creator GUI so they should match correct upper/lower case.
Running a manual snapmirror update on the vault site returns successfully (nothing is transferred since there are no new snapshots on the primary volume):
The SC version used is the latest community version (4.1c). I tried the backup with the following Snapshot options in the config file:
I would expect this to match the daily backup performed by SME.
When I run the backup, however, the first (oldest) snapshot is selected. Furthermore it seems like the snapshot "selection" occurs prior to performing the actual SME/Exchange backup. Could something be configured incorrectly?
I'll attach screenshot and logs from the last backup attempt.
Yeah the snapshot list happens when SC does storage discovery. You would want to snapshot to already exist but you could maybe change the workflow xml file and run discovery after the snapshot is taken or you could run SME and make sure snapshot is there before calling config which is supposed to do something with snapshot.
Under scServer/engine/etc/workflow are the XMLs. You can edit backup.xml and add a second storageDiscovery task after the task which is calling SME
Nope the only parameter besides turning on external snapshots is NTAP_EXTERNAL_SNAPSHOT_REGEX, maybe try changing your regex to NTAP_EXTERNAL_SNAPSHOT_REGEX=__daily. It seems like SC is not matching the correct snapshots.