Is it possible for a snapmirror update command (one not mediated by SnapDrive) to temporarily halt I/O on the source disk?  More to the point, is it possible for a snapmirror update command to harm the source server if that server is an active Exchange 2003 box?

 

We do own SnapDrive for Exchange, but installing it is not an option at this time. 

 

This snapmirror solution is being suggested as an emergency solution to replicate our Exchange database for the next few days, while our operations team tries to figure out why DoubleTake has failed for four days in a row.  They understand that without SnapDrive’s VSS goodness there is a good chance of data loss on the target end, but they’d like to give this a shot on the theory that it’s better than nothing.

 

But it’s only better than nothing if it doesn’t interfere with the production (source) server, hence my inquiry.  If there is any chance of an I/O suspension that could take the production server offline, then obviously this is a nonstarter. 

 

Many thanks.

This e-mail, including any attachment(s), is intended solely for use by the named addressee(s). If you are not the intended recipient, you are not authorized to disclose, copy, distribute or retain this message, without written authorization from Jennison Associates LLC ("Jennison"). This e-mail may contain proprietary, confidential or privileged information. If you have received this message in error, please notify the sender immediately. If you have requested Jennison to e-mail any account information to you or your designee, you are deemed to have consented to electronic delivery of information from Jennison. E-mail messages are not secure and may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient.