If you are using the "Other Mount Options" settings within the RM job properties, you could also select the option "Unmount replica upon job completion".
If that does not work with your setup you could also set the replica count for the snap job to one, so that each time the job runs it will first unmount and then expire the existing snap before creating a new one.
Just be sure that your backup script does not call back to the RM client pre-maturely. i.e. dont let the original script invoked by RM mount options end before the backup does.
Some years ago I had a customer who had a similar issue with backing up SQL via a Backup Exec script launched from RM/SE. We found out that by using the ¿bemcmd¿ command with the -w option the script waits until the BE job has complete before returning a value of -1 thus allowing RM/SE to unmount and complete the job¿.
AranH1
2.2K Posts
0
March 2nd, 2009 08:00
If that does not work with your setup you could also set the replica count for the snap job to one, so that each time the job runs it will first unmount and then expire the existing snap before creating a new one.
JamesBEMC
257 Posts
0
March 2nd, 2009 12:00
Just be sure that your backup script does not call back to the RM client pre-maturely. i.e. dont let the original script invoked by RM mount options end before the backup does.
Let us know how it goes!
Cheers
James.
calle2
133 Posts
0
March 2nd, 2009 13:00
Some years ago I had a customer who had a similar issue with backing up SQL via a Backup Exec script launched from RM/SE. We found out that by using the ¿bemcmd¿ command with the -w option the script waits until the BE job has complete before returning a value of -1 thus allowing RM/SE to unmount and complete the job¿.
Here is a link to the BE v10 Command Line Applet document: ftp://exftpp.symantec.com/pub/support/products/Backup_Exec_for_WindowsNT/275538.pdf
I hope this helps
Cheers
Carl
snewton1
19 Posts
0
April 23rd, 2009 18:00