2011-09-05 06:53 AM
in a recent snapmirror process, on the destination filer was showing the data transfered etc and that it had finished and was idle. when i try to connect Luns to my exchange the files, specifically the log files had a different timestamp than the actual source filer and thus exchange could not start.
any comment on what might have casued the data not to be fully mirrored but to show them as mirrored?
Solved! SEE THE SOLUTION
2011-09-05 07:09 AM
That’s not going to work, at least as simple as you expect it.
Either you have to use consistency group API to create write-order consistent snapshots across three volumes (e.g. utilizing SnapCreator) or you need to be quite careful in which order you create snapshots and do manual recover of database on remote side.
The simplest way for you would probably be Snap Manager for Exchange that integrates with SnapMirror and automates database recovery on remote side.
2011-09-05 07:14 AM
So basically you are suggesting to configure snapmanager for exchange to take snapshots and then update the dr site. after that i will be able to disconnect my exchange from Primary site, and connect it to the Dr site and have everything working?
2011-09-05 07:18 AM
Please do not forget that replicating (consistent) data is just a part of overall disaster recovery setup. There is quite a bit to be done on Microsoft side as well to be able to run Exchange on DR site.
2011-09-05 07:33 AM
You could start with Snap Manager for Exchange documentation ☺ specifically with disaster recovery chapter: https://now.netapp.com/NOW/knowledge/docs/SnapManager/relsme602/html/software/admin/GUID-141E8E86-AB9F-4585-87C2-69D1AC4EA0FE.html
Current version of SME/Exchange automate many tasks that had to be done manually before; you could review this KB (that exactly how I have done it in the past): https://kb.netapp.com/support/index?page=content&id=1011643. This KB also contains some reference to Microsoft documentation.
And of course Microsoft has detailed guides about Exchange disaster recovery planning and implementation. Data replication is just a tiny (albeit quite important) part of it.