02-15-2013 03:13 AM
I have a very unusual problem in my environment currently - duplications of one specific Exchange database intermittently hang on a regular basis, but then run successfully on the next attempt if they are cancelled. I've provided logs and NBSUs to Symantec Support and they're investigating it at the moment, although it seems to have confused them so far!
In an attempt to continue trying to troubleshoot this myself as well, I have been considering delaying when SLP duplications start following a backup using the DUPLICATION_SESSION_INTERVAL_MINUTES parameter in the LIFECYCLE_PARAMETERS file.
However, ideally I'd like to delay duplication overnight but have the usual default of 5 minutes during the day for any manual backups. Is there any way of achieving this, with or without using the LIFECYCLE_PARAMETERS file?
Solved! Go to Solution.
02-15-2013 03:26 AM
Best way is to just deactivate the SLPs before you go home (just right click) and then activate them again the next morning
Or use Windows scheduler to run the commands needed (preferably to run a .bat file with them all in - running as administrator):
nbstlutil inactive -lifecycle lifecyclename
Then when you want them re-activated use
nbstlutil active -lifecycle lifecyclename
Is it an exchange GRT duplications that causes the issues or a normal one?
02-15-2013 03:26 AM
Best way is to just deactivate the SLPs before you go home (just right click) and then activate them again the next morning
Or use Windows scheduler to run the commands needed (preferably to run a .bat file with them all in - running as administrator):
nbstlutil inactive -lifecycle lifecyclename
Then when you want them re-activated use
nbstlutil active -lifecycle lifecyclename
Is it an exchange GRT duplications that causes the issues or a normal one?
02-15-2013 06:01 PM
Using cron (Unix) or scheduler (Windows) to schedule a change of the value DUPLICATION_SESSION_INTERVAL_MINUTES in LIFECYCLE_PARAMETERS.
02-21-2013 03:38 AM
Thanks for the help guys, scheduling .bat files to deactivate/reactivate them or change the interval sounds good - I just wanted to make sure I wasn't missing any other way of doing it.
It's a normal Exchange backup, no GRT. Support have escalated my case now so hopefully the logs will give us some clues!