Skip to main content

How do I migrate my VM Backup configuration to another machine?

  • Updated

Important notes before you start...

 

1. If you are migrating to a Hyper-V Host that was already managed by the previous installation or one that was added as a LOCALHOST, please note that this is not supported and a dedicated machine for VM Backup is required.

 

2. It's important to note that if a host is re-installed this will be considered as a new host by VM Backup. This means that even if the same VMs are migrated to this new host/installation, backups will still be taken from scratch. In this case there is no need to migrate the configuration as a reconfiguration will be required.

 

3. Hyper-V Cluster Support: The configuration migration tool cannot be used to move the VM Backup configuration between nodes in the same cluster. In this case a dedicated machine is required for VM Backup.

 

4. If you previously had a mixed infrastructure (Hyper-V and VMware), please note that this is not supported and it is suggested to use a dedicated machine for VM Backup.

 

5. You must be running at least 8.5.20 in order to make use of the migration tool.

 

Version 9

Section A - Migrating to a new machine

 

VM Backup automatically backs up its configuration to your configured primary locations. This allows you to restore the configuration to another machine in case of a disaster or if you need to migrate it to another machine. The configuration is saved in the 'ConfigBackup' folder in the configured backup location.

 

It is important to note that:

  • The VM Backup Console must be closed
  • The target machine being used to restore the configuration must have a clean VM Backup installation

 

To start the migration, proceed as follows:

  1. Install the latest version of VM Backup on the new machine

  2. Uninstall VM Backup from the old machine. This is a really important step; failure to do so could result in data corruption from having both consoles running at the same time.

  3. Browse to C:\Program Files\Hornetsecurity\VMBackup and right-click on "VMBackup.AttachConfig.exe" and [Run as Administrator]

  4. The AttachConfig tool will pop up:



  5. Click [Next] to proceed and leave [VM Backup] selected in this case. Then select the Backup Location by browsing to it or enter the network path as well as the network credentials for the backup location. This needs to be supplied as previously configured in the VM Backup, Backup Locations screen.

    The [Master Encryption Key] needs to be the same that was configured in the previous installation. Make sure it is entered correctly and identical as otherwise encrypted backups will start fresh.

    Once you provide all information, click [Next] and then if you are sure that the encryption key was entered correctly click [OK] to proceed.

    mceclip0.png

  6. If the tool finds multiple configuration backups within the entered backup location, you will get a choice via a drop-down menu:

    mceclip1.png
    You will see the machine name of the previous installation listed, once you pick the desired one. Click [Next]

    mceclip2.png

  7. After it goes through a couple of steps to map previous hosts etc...you will be prompted to enter credentials for any network locations you had added to the previous installation. Once all data has been entered, click [Next] or if you would like to enter them afterwards, you can skip it.



  8. You should finally get this screen that configuration has been successfully imported. You can proceed to Section B in order to complete your migration.

 

 

 

Section B - Completing your Migration

 

Next, make sure to follow the steps below in order to complete the migration:

  1. Go to [Hosts] and enter the details next to each host in order to re-authenticate to your host. From this screen, remember to assign any License Key's to the Hosts if you are using Perpetual Licensing.

  2. If your installation was connected to CP, click on the [CP] option and add the installation. This will be added as a new installation, then it's important to delete the old disconnected installation.

  3. Go to [Backup Locations] and re-enter the credentials for Network Paths, Offsite Backup Servers or the Connection String for Azure/Amazon S3/Wasabi accounts. Simply click on the pencil icon to edit the current location.

  4. If you didn't have an Offsite Backup Server (Managed by CP) Backup Location added to your VM Backup, you can skip this step. Go to Step 5.

    If you did. your location will now be marked as disconnected. You will need to go to your CP, open your Offsite Backup Server and click on [Choose VMs to Back Up]

    Select the VM Backup Installation, as you can see we are picking the new one here, old one is marked as disconnected. Then, select the Unmanaged location and match it with the Offsite Backup Server account.


    Pick the VMs you'd like to backup to the Offsite Backup Server, click [Next] and [Save]

  5. Go to [Notifications] and re-enter the credentials if you were using authentication with the SMTP server. If you didn't have this set up, you can skip this step.

  6. If your installation has a Proxy configured, click on the [Settings] icon [Proxy Settings]. If you didn't have this set up, you can skip this step.

  7. You're all good to go! All backups will now keep backing up to any existing backup data from the previous configuration.

 

Version 8

Section A - Migrating to a new machine

 

VM Backup automatically backs up its configuration to your configured primary locations. This allows you to restore the configuration to another machine in case of a disaster or if you need to migrate it to another machine. The configuration is saved in the 'ConfigBackup' folder in the configured backup location.

 

It is important to note that:

  • The VM Backup Console must be closed
  • The target machine being used to restore the configuration must have a clean VM Backup installation

 

To start the migration, proceed as follows:

  1. Install the latest version of VM Backup V8 on the new machine

  2. Uninstall VM Backup from the old machine. This is a really important step; failure to do so could result in data corruption from having both consoles running at the same time.

  3. Browse to C:\Program Files\Altaro\Altaro Backup and right-click on "AttachConfig.exe" and [Run as Administrator]

  4. The AttachConfig tool will pop up:



  5. Click [Next] to proceed and leave [VM Backup] selected in this case. Then select the Backup Location by browsing to it or enter the network path as well as the network credentials for the backup location. This needs to be supplied as previously configured in the VM Backup, Backup Locations screen.

    The [Master Encryption Key] needs to be the same that was configured in the previous installation. Make sure it is entered correctly and identical as otherwise encrypted backups will start fresh.

    Once you provide all information, click [Next] and then if you are sure that the encryption key was entered correctly click [OK] to proceed.



  6. If the tool finds multiple configuration backups within the entered backup location, you will get a choice via a drop-down menu:


    You will see the machine name of the previous installation listed, once you pick the desired one. Click [Next]



  7. After it goes through a couple of steps to map previous hosts etc...you will be prompted to enter credentials for any network locations you had added to the previous installation. Once all data has been entered, click [Next] or if you would like to enter them afterwards, you can skip it.



  8. You should finally get this screen that configuration has been successfully imported. You can proceed to Section B in order to complete your migration.

 

 

 

Section B - Completing your Migration

 

Next, make sure to follow the steps below in order to complete the migration:

  1. Go to [Hosts] and enter the details next to each host in order to re-authenticate to your host. From this screen, remember to assign any License Key's to the Hosts if you are using Perpetual Licensing.

  2. If your installation was connected to CP, click on the [CP] option and add the installation. This will be added as a new installation, then it's important to delete the old disconnected installation.

  3. Go to [Backup Locations] and re-enter the credentials for Network Paths, Offsite Backup Servers or the Connection String for Azure/Amazon S3/Wasabi accounts. Simply click on the pencil icon to edit the current location.

  4. If you didn't have an Offsite Backup Server (Managed by CP) Backup Location added to your VM Backup, you can skip this step. Go to Step 5.

    If you did. your location will now be marked as disconnected. You will need to go to your CP, open your Offsite Backup Server and click on [Choose VMs to Back Up]

    Select the VM Backup Installation, as you can see we are picking the new one here, old one is marked as disconnected. Then, select the Unmanaged location and match it with the Offsite Backup Server account.


    Pick the VMs you'd like to backup to the Offsite Backup Server, click [Next] and [Save]

  5. Go to [Notifications] and re-enter the credentials if you were using authentication with the SMTP server. If you didn't have this set up, you can skip this step.

  6. If your installation has a Proxy configured, click on the [Settings] icon [Proxy Settings]. If you didn't have this set up, you can skip this step.

  7. You're all good to go! All backups will now keep backing up to any existing backup data from the previous configuration.

Related articles

Articles in this section
See more

Privacy Policy / Legal Notice