[THIN] Re: Replicate server - break mirror

  • From: "Jim Kerr" <jim@xxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Mon, 2 May 2005 10:03:34 -0400

99% of my customers do the same as you do Brian.  It works great.  If it 
doesn't it is user error.  :)
  ----- Original Message ----- 
  From: RMC - Brian Hill 
  To: 'thin@xxxxxxxxxxxxx' 
  Sent: Monday, May 02, 2005 10:03 AM
  Subject: [THIN] Re: Replicate server - break mirror


  I've been ghosting servers for years without issue, and you are the first 
I've ever heard say it's a problem.

  Brian

  -----Original Message-----
  From: Callahan, Michael [mailto:MichaelCallahan@xxxxxxxxxxxxxxxx]
  Sent: Monday, May 02, 2005 8:27 AM
  To: thin@xxxxxxxxxxxxx
  Subject: [THIN] Re: Replicate server - break mirror


  I would recommend against this approach - had a guy in my org who was fond of 
doing this and we had to go back and reinstall the OS on most of his servers 
due to various problems.  In my opinion it is a sloppy way of provisioning an 
OS.  Use Ghost, Altiris or a scripted RIS/unattended install for provisioning 
your servers.

  Michael
    -----Original Message-----
    From: RMC - Brian Hill [mailto:brian.hill@xxxxxxxxxx]
    Sent: Saturday, April 30, 2005 10:44 AM
    To: 'thin@xxxxxxxxxxxxx'
    Subject: [THIN] Re: Replicate server - break mirror


    I would use Ghost instead.

    Brian

    -----Original Message-----
    From: Chris Grecsek [mailto:cgrecsek@xxxxxxxxxxxxx]
    Sent: Friday, April 29, 2005 6:38 PM
    To: thin@xxxxxxxxxxxxx
    Subject: [THIN] Replicate server - break mirror


    A while back a few people mentioned that they were replicating their Citrix 
servers by breaking mirror sets and then simply moving one of the mirrored 
drives to the new server. They also mentioned that they had a set of procedures 
for doing this and were willing to share. I'm looking to adopt this methodology 
as it seems to be the easiest and was hoping that someone would be willing to 
share those procedures? 

     

    Thanks!  

  ********** Confidentiality Notice **********
  This electronic transmission and any attached documents or other
  writings are confidential and are for the sole use of the intended
  recipient(s) identified above. This message may contain information
  that is privileged, confidential or otherwise protected from disclosure
  under applicable law. If the receiver of this information is not the
  intended recipient, or the employee, or agent responsible for delivering
  the information to the intended recipient, you are hereby notified that
  any use, reading, dissemination, distribution, copying or storage of this
  information is strictly prohibited. If you have received this information in
  error, please notify the sender by return email and delete the electronic
  transmission, including all attachments from your system.

Other related posts: