Open virtual machine manager, navigate to virtual machine and then choose the import option.Ĭhoose the target NAS to deploy the OVA too. In this step we will import the OVA files to register the virtual machines on the target NAS and power on a VM to prove that the process works. I did not want to do this.īrowsing the shared file structure in File Station shows we now have the 3 OVA files as expected, ready to import. You may choose to recover the system config, this is automatically backed up. Launch Hyper Backup on the target NAS and click the restore/data option as shown below.Ĭlick Restore from the existing repositoryīrowse the local folder for the file to restore from.Ĭhose the folder where the backup file exists. The restoration process will unpack the HBK file referenced in the previous screenshot and restore the folder structure containing the OVA files that will allow us to import them into Virtual Machine Manager on the target NAS. We can check the backup file exists on the target NAS by browsing the shared folder structure. The job will now be created, click backup now. The default is 256 iterations, I changed mine to 3. You may choose to backup application settings as well, I was not concerned with this.ĭefine retention policy, if required. The NetBackup folder should already exist.Ĭhoose the VM_backups shared folder from the source NAS to backup. When the backup wizard launches, we need to create a job that will target a remote NAS device.Įnter the details for the target NAS and choose the backup location. Next, we will launch Hyper Backup on the source NAS, the one where we created the OVA files in step 1. This will enable us to use the NAS as a remote backup repository. I will run through the steps below but they are also detailed in Synologys guide for migration.Īssuming Hyper Backup and Hyper Backup Vault are installed on the target NAS, the next step is to enable the rsync service from the control panel on the target NAS device. Hyper backup needs to be installed on both NAS devices and a tool called Hyper Backup Vault needs to be installed on the target NAS. Hyper backup utilises a second NAS as the target for the backup files that it creates. If the shared folder does not exist, you will be asked to create one at this stage. Open Virtual Machine Manager, select the VM and choose export.Ĭhoose the shared folder to export the OVA too. To do this within Virtual Machine Manager is easy as I will demonstrate below. OVA or Open Virtualisation Format is a common way to package a virtual machine for distribution to allow the import of the virtual machine to hypervisors such as VMware ESXi or KVM. How to Step 1 – Export existing virtual machines to OVA format As this is a one-off migration, I was not too concerned about the extra time required to perform the steps. Export the virtual machines to OVA format and then back them up to a remote NAS using the Synology Hyper Backup tool. This is a one-off task, so I did not need that, although there is a 30-day trial available. Now I created a cluster fine, that part is straightforward, but to enable migration of virtual machine workloads, you need to pay for an additional Virtual Machine Manager Pro license, which again I don’t have. All I wanted to move was three virtual machines, so I thought why not try and create a Virtual Machine Manager cluster and move the virtual machines that way. Synology has a tool called Migration Assistant, which does just that, but the target NAS needs to have more available capacity than the source NAS, which I don’t have in this case so that plan was out. Now Synology provides guidance on the best way to migrate settings and data from an existing NAS to a new one, but all the available options did not quite work out for me. Similar NAS, both 6 drives bays, just one is intel CPU based and the other is AMD. I had a requirement to migrate my content from a Synology DS1621XS+ to a DS1621+.
0 Comments
Leave a Reply. |