Difference between revisions of "Ajcody-Server-Move-VM-Different-Image-OS"

m (Prepare A New ZCS Image With New OS and Basic ZCS)
m (Moving To New VM Image)
Line 45: Line 45:
  
 
# Schedule downtime on prod
 
# Schedule downtime on prod
# Shutdown zcs on prod , unconfigure /etc/fstab to NOT use /opt/zimbra partition and unconfigured VM properties for that image to no longer use that /opt/zimbra disk image . As a precaution, you could configure the PROD image to use another hostname/ip -- just incase someone boots in later, you don't want it to effect the new server.
+
# Shutdown ZCS on prod  
# You might need to use the VM tools about moving the /opt/zimbra disk image partition to be under the image directory for the RHEL image
+
#* Modify /etc/fstab to NOT use the /opt/zimbra partition
 +
#* As a precaution, you could configure the PROD image to use another hostname/ip -- just incase someone boots in later, you don't want it to effect the new server.
 +
#* Shutdown the PROD vm
 +
#* Unconfigured VM properties for that image to no longer use that /opt/zimbra disk image.
 +
#* Move/copy the /opt/zimbra disk images into the new VM's directory path or whatever is needed so the new VM image can use the disk image.
 +
#** You might need to use the VM tools about moving the /opt/zimbra disk image partition to be under the image directory for the RHEL image.
 +
#** The details/how-to on how to do this will be determined by the VMware production and version your using. Please consult with Vmware support if you need help on this.
 +
#** Some of my own notes on moving/copying images are here :
 +
#*** [[Ajcody-Virtualization#How-To_Setup_ESX_For_ZCS_Test_Servers]]
 
# Boot the RHEL image
 
# Boot the RHEL image
 
# Shutdown zcs if it attempted to run via init.d  
 
# Shutdown zcs if it attempted to run via init.d  

Revision as of 18:21, 18 November 2010

Attention.png - This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information.


Server Move VM Different Image OS

Server Move VM Different Image OS Page

Please see: Ajcody-Server-Move-VM-Different-Image-OS

Introductory Notes

A brief over view on moving Zimbra from one VM to another VM using a different OS.

Note - Please read through Ajcody-Notes-Server-Move first since details are there for various steps mentioned below.

Setup A New Partition On PROD For ZCS

This is necessary if your current VM doesn't have dedicated partition/disk images for ZCS.

Setup a new disk partition for the PROD vm to use and then rsync the data to it [locally] on PROD. And then, reuse that underlying partitions on a new RHEL vm image?

  1. Create new partition for PROD vm
  2. Mount new partition under PROD - /opt/zimbra-temp
  3. Start a rsync between /opt/zimbra and /opt/zimbra-temp
  4. Schedule short downtime window to
    • Shutdown zcs on PROD
    • Do a final rsync between /opt/zimbra and /opt/zimbra-temp
  5. Reconfigure mounts and directory paths
    • mv /opt/zimbra /opt/zimbra-old
    • Adjust /etc/fstab to mount /opt/zimbra-temp to now be /opt/zimbra
    • Remount new partition under /opt/zimbra now
  6. Start zimbra and confirm it works

Prepare A New ZCS Image With New OS and Basic ZCS

  1. Build new RHEL vm image that will be able to use the /opt/zimbra partition from PROD later.
  2. Install ZCS of same version that is on PROD but for RHEL version your using [./install.sh -s]
    • Make sure you allocate enough free space to the root disk
    • You might want to disable ZCS from starting automatically from initd before you shutdown the image.
  3. Shutdown RHEL image

Moving To New VM Image

  1. Schedule downtime on prod
  2. Shutdown ZCS on prod
    • Modify /etc/fstab to NOT use the /opt/zimbra partition
    • As a precaution, you could configure the PROD image to use another hostname/ip -- just incase someone boots in later, you don't want it to effect the new server.
    • Shutdown the PROD vm
    • Unconfigured VM properties for that image to no longer use that /opt/zimbra disk image.
    • Move/copy the /opt/zimbra disk images into the new VM's directory path or whatever is needed so the new VM image can use the disk image.
      • You might need to use the VM tools about moving the /opt/zimbra disk image partition to be under the image directory for the RHEL image.
      • The details/how-to on how to do this will be determined by the VMware production and version your using. Please consult with Vmware support if you need help on this.
      • Some of my own notes on moving/copying images are here :
  3. Boot the RHEL image
  4. Shutdown zcs if it attempted to run via init.d
  5. Configured RHEL image to now use the /opt/zimbra disk partition image . You could also adjust the ip & hostname on this image to use PRODS now.
  6. Configure /etc/fstab to mount the /opt/zimbra parition
  7. Move the basic zcs install directory - mv /opt/zimbra /opt/zimbra-old ; mkdir /opt/zimbra with correct perms
  8. Mount /opt/zimbra
  9. Continue with the server move wiki steps after all the rsync stuff was done.
    • Way down at the bottom of the wiki:
      • [steps 3 - 6, mostly at the end of step 4]
        • On NEWHOST as ROOT, rerun the installer without the -s option
        • ./install.sh
Jump to: navigation, search