Ajcody-Server-Move-VM-Different-Image-OS: Difference between revisions
Line 44: | Line 44: | ||
===Moving To New VM Image=== | ===Moving To New VM Image=== | ||
# Schedule downtime on | # Schedule downtime on PROD-VM | ||
# Shutdown ZCS on | # Shutdown ZCS on PROD-VM | ||
#* Modify /etc/fstab to NOT use the /opt/zimbra partition | #* 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 | #* As a precaution, you could configure the PROD-VM image to use another hostname/ip -- just in case someone boots in later, you don't want it to effect the new server. | ||
#* Shutdown the PROD | #* Shutdown the PROD-VM | ||
#* | #* Unconfigure VM properties for PROD-VM to no longer use the /opt/zimbra disk image. | ||
#* Move/copy the /opt/zimbra disk images into the | #* Move/copy the /opt/zimbra disk images into the NEWHOST-VM's directory path or whatever is needed so the NEWHOST-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 | #** You might need to use the VM tools about moving the /opt/zimbra disk image partition to be under the image directory for the NEWHOST-VM image. | ||
#** The details/how-to on how to do this will be determined by the VMware | #** The details/how-to on how to do this will be determined by the VMware product 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 : | #** Some of my own notes on moving/copying images are here : | ||
#*** [[Ajcody-Virtualization#How-To_Setup_ESX_For_ZCS_Test_Servers]] | #*** [[Ajcody-Virtualization#How-To_Setup_ESX_For_ZCS_Test_Servers]] | ||
# Boot the | # Boot the NEWHOST-VM image | ||
# Shutdown zcs if it attempted to run via init.d | # Shutdown zcs if it attempted to run via init.d | ||
# | # Configure the NEWHOST-VM image to now use the /opt/zimbra disk partition image . You could also adjust the ip & hostname on this image to use PROD-VM's now. | ||
# Configure /etc/fstab to mount the /opt/zimbra parition | # Configure /etc/fstab to mount the /opt/zimbra parition | ||
# Move the basic zcs install directory - mv /opt/zimbra /opt/zimbra-old ; mkdir /opt/zimbra with correct perms | # Move the basic zcs install directory - mv /opt/zimbra /opt/zimbra-old ; mkdir /opt/zimbra with correct perms | ||
Line 64: | Line 64: | ||
#* Way down at the bottom of the wiki: | #* Way down at the bottom of the wiki: | ||
#** [steps 3 - 6, mostly at the end of step 4] | #** [steps 3 - 6, mostly at the end of step 4] | ||
#*** ''On NEWHOST as ROOT, rerun the installer without the -s option'' | #*** ''On NEWHOST-VM as ROOT, rerun the installer without the -s option'' | ||
#*** ''./install.sh'' | #*** ''./install.sh'' |
Revision as of 18:28, 18 November 2010
- 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?
- Create new partition for PROD vm
- Mount new partition under PROD - /opt/zimbra-temp
- Start a rsync between /opt/zimbra and /opt/zimbra-temp
- Schedule short downtime window to
- Shutdown zcs on PROD
- Do a final rsync between /opt/zimbra and /opt/zimbra-temp
- 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
- Start zimbra and confirm it works
Prepare A New ZCS Image With New OS and Basic ZCS
- Build new RHEL vm image that will be able to use the /opt/zimbra partition from PROD later.
- 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.
- Shutdown RHEL image
Moving To New VM Image
- Schedule downtime on PROD-VM
- Shutdown ZCS on PROD-VM
- Modify /etc/fstab to NOT use the /opt/zimbra partition
- As a precaution, you could configure the PROD-VM image to use another hostname/ip -- just in case someone boots in later, you don't want it to effect the new server.
- Shutdown the PROD-VM
- Unconfigure VM properties for PROD-VM to no longer use the /opt/zimbra disk image.
- Move/copy the /opt/zimbra disk images into the NEWHOST-VM's directory path or whatever is needed so the NEWHOST-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 NEWHOST-VM image.
- The details/how-to on how to do this will be determined by the VMware product 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 :
- Boot the NEWHOST-VM image
- Shutdown zcs if it attempted to run via init.d
- Configure the NEWHOST-VM image to now use the /opt/zimbra disk partition image . You could also adjust the ip & hostname on this image to use PROD-VM's now.
- Configure /etc/fstab to mount the /opt/zimbra parition
- Move the basic zcs install directory - mv /opt/zimbra /opt/zimbra-old ; mkdir /opt/zimbra with correct perms
- Mount /opt/zimbra
- 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-VM as ROOT, rerun the installer without the -s option
- ./install.sh
- [steps 3 - 6, mostly at the end of step 4]
- Way down at the bottom of the wiki: