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.
Jon, There is no I/O disruption.
David Byte byte@web-host.net
___________________________________ If guns cause crime, spoons and forks cause obesity and pencils cause misspelled words. ___________________________________
On Aug 25, 2011, at 9:46 AM, Jon Hill wrote:
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._______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
On 8/25/2011 7:46 AM, Jon Hill wrote:
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.
snapmirror initialize, update, etc.. will not halt io on the source, it will however impact network (if they run over the same path, but this can be minimized) your snapmirrored copy will not be in a consistent state (am assuming you are using luns) on the dest side you will then have to do some steps to restore the exchange.
You might be able to do something with a script to use the inbuilt VSS in windows, I wouldn't know where to start though
From experience though, the chance of mounting that database is pretty low, as the logs won't match the database.
Cheers
Matt
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jon Hill Sent: 25 August 2011 15:46 To: toasters@teaparty.net Subject: snapmirroring Exchange
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.
________________________________ _____________________________________________________________ This e-mail (including all attachments) is confidential and may be privileged. It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at help@generalatlantic.com . Thank You.
It won't effect storage IO and if you have your logs + DB on the same file system you should retain crash consistency. If they are on separate volumes you will probably need sync snapmirror which is much more network intensive but should give you the best chance of it coming back up more or less cleanly. We've had good results doing the former.
Jeremy Page | Office: 336-547-5399 | Cell: 336-602-7274 | On Call: 336-430-815| jeremypage@yahoo.com
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jon Hill Sent: Thursday, August 25, 2011 10:46 AM To: toasters@teaparty.net Subject: snapmirroring Exchange
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.
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.
-
Chaim Rieger -
David Byte -
Davies, Matt -
Jon Hill -
Page, Jeremy