BES 4.1 Backup or redudancy?
We're running BES 4.1 and we have been asked by the business folks what would the turn around be if he we had a disaster with our BES server.
Can someone point me in the direction of a data recovery plan? What are you guys\girls using out there in case of a disaster? Should we look at program like Neverfail?
We use Neverfail and it works really well.
and make sure you don't forget the obvious ... like backups of your current production server and database. If any of your DR plans fail, this will be your best chance at a quick(er) recovery.
2 BES and SQL mirroring works well
I've implemented a high availability solution for a customer that has two BES hosts running concurrently - one in production and one at a DR site.
The primary SQL 2005 server is in the production data centre and is mirrored to the DR site using transaction log shipping.
If you lose the production data centre you have everything available in a 'hot' spare configuration. You just run a SQL script on the backup database to change it to being the primary database and 'move' the users from the offline BES to the online BES.
This last process takes about 20 minutes to successfully move 100 users. The online BES just pushes new service books to the user devices and everybody gets on with the job...except if your messaging system isn't covered by your DR strategy...
|All times are GMT -5. The time now is 01:29 PM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.