Ajcody-Server-Move-VM-Different-Image-OS: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
{| | {{BC|Zeta Alliance}} <!-- Note, this will also add [[Category: Zeta Alliance]] to bottom of wiki page. --> | ||
__FORCETOC__ <!-- Will force a TOC regards of size of article. __NOTOC__ if no TOC is wanted. --> | |||
<div class="col-md-12 ibox-content"> | |||
==Server Move VM Different Image OS== <!-- Normally will reflect page title. Is listed at very top of page. --> | |||
{{KB|{{ZETA}}|{{ZCS 8.6}}|{{ZCS 8.0}}|{{ZCS 7.0}}|}} <!-- Can only handle 3 ZCS versions. --> | |||
==Server Move VM Different Image OS== | {{WIP}} | ||
===Server Move VM Different Image OS Page=== | ===Server Move VM Different Image OS Page=== |
Latest revision as of 13:36, 21 June 2016
Server Move VM Different Image OS
- This article is a Work in Progress, and may be unfinished or missing sections.
Server Move VM Different Image OS Page
Please see: Ajcody-Server-Move-VM-Different-Image-OS
Introductory Notes
- Note - Please read through Ajcody-Notes-Server-Move first since details are there for various steps mentioned below.
A brief over view on moving Zimbra from one VM to another VM using a different OS.
Setup A New Partition On PROD-VM For ZCS
This is necessary if your current PROD-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-VM. Then we'll reuse that underlying partitions on a new NEWHOST-VM image later.
- Create new partition for PROD-VM
- Mount new partition under PROD-VM - /opt/zimbra-temp
- Start a rsync between /opt/zimbra and /opt/zimbra-temp on PROD-VM locally.
- Schedule short downtime window to:
- Shutdown zcs on PROD-VM
- 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 NEWHOST-VM image that will be able to use the /opt/zimbra partition [dedicated disk image] from PROD-VM.
- Meaning, the disk image for /opt/zimbra used on PROD will be accessible for the NEWHOST-VM vm configuration. It might be on a SAN, same local disk storage, or be copied/transferred between storage nodes.
- Install ZCS of same version that is on PROD-VM but for OS 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 NEWHOST-VM 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: