It is advised to use the following the steps when rebooting (as example, after implementing a hotfix/patch/update) :
- Run SourceOne Suspend for Backup script (make sure you include DiscoveryManager if this is implemented, by default, this is commented out in the scripts)
- After script has completed (approx. 5 minutes) run a new script which stops all EMC SourceOne Services (make sure you stop Job Scheduler and Address Cache as last) and turns the startup type into 'Disabled or Manual' to prevent these servers from starting again after a reboot.
- After all services are stopped, you can take a back-up of all the necessary components
BenCs
1 Rookie
•
114 Posts
2
July 24th, 2015 02:00
Answer on all your questions:
It is advised to use the following the steps when rebooting (as example, after implementing a hotfix/patch/update) :
- Run SourceOne Suspend for Backup script (make sure you include DiscoveryManager if this is implemented, by default, this is commented out in the scripts)
- After script has completed (approx. 5 minutes) run a new script which stops all EMC SourceOne Services (make sure you stop Job Scheduler and Address Cache as last) and turns the startup type into 'Disabled or Manual' to prevent these servers from starting again after a reboot.
- After all services are stopped, you can take a back-up of all the necessary components
- Implement Exchange/MS SQL/Windows updates/patches (Including Reboot)
- Test updates and patches
- Change startup type from Sourceone Services to Automatic
- Start SourceOne Services (Job scheduler and Address Cache as first)
- Run SourceOne Resume after backup script.
- Best practice: run an historical archive on a mailbox to test if everything is OK on SourceOne Side