Just curious - if you don't have a SAN at your DR site, are you going to be able to adequately conduct business in a DR scenario?
Jim Jim Holmgren Director of Technology Infrastructure XLHealth Corporation The Warehouse at Camden Yards 351 West Camden Street, Suite 100 Baltimore, MD 21201 410.625.2200 (main) 443.524.8573 (direct) 443-506.2400 (cell) www.xlhealth.com<http://www.xlhealth.com/> From: Derrenbacker, L. Jonathan [mailto:jderrenbac...@keitercpa.com] Sent: Monday, November 26, 2012 1:41 PM To: NT System Admin Issues Subject: Replicating VMs to DR? For those who replicate their Virtual Servers to their Disaster Recovery site, I'm curious who uses what method. I don't have a second SAN in my disaster recovery site right now, and I'm looking for other methods to replicate my VMs without SAN-to-SAN. There's always the option of just taking a Veeam or Vranger backup and copying that to DR via robocopy every day. But something more real-time would be nice... Anyone have opinions/ideas? Thanks, Jon [cid:image001.png@01CDCBDD.D5B12620] Jon Derrenbacker | Systems Engineer Manager | Keiter 4401 Dominion Boulevard, 2nd Floor, Glen Allen, VA 23060 phone: 804-273-6221 | fax: 804-747-3632 | keitercpa.com<http://www.keitercpa.com/> Experience | Knowledge | Relationships | Insight Note: This communication, including any attachments, may contain privileged or other confidential information. If you are not the intended recipient, or believe you have received this communication in error, do not print, copy, retransmit, disseminate, or otherwise use the information contained within. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by the IRS, we inform you that any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding any penalties under the Internal Revenue Code or (ii) promoting, marketing or recommending to another party any transaction(s) or tax-related matter(s) addressed herein. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or protected health information. Under the Federal Law (HIPAA), the intended recipient is obligated to keep this information secure and confidential. Any disclosure to third parties without authorization from the affiliate or as permitted by law is prohibited and punishable under Federal Law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. NOTA DE CONFIDENCIALIDAD: Este facsÃmile, incluyendo lo adjunto, es para el uso exclusivo del destinatario(s) y puede contener información confidencial y/o información protegida de salud. En virtud de la Ley Federal (HIPAA), el destinatario tiene la obligación de mantener esta información segura y confidencial. Cualquier divulgación a terceros sin la autorización de los miembros de lo permitido por la ley está prohibido y penado en virtud de la Ley Federal. Si usted no es el destinatario, por favor, póngase en contacto con el remitente por teléfono y destruir todas las copias del mensaje original ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
<<inline: image001.png>>
