I recently converted my physical hosts (three laptops) at home into virtual machines. I understood the benefits at the time but didn’t consider other areas that may be affected by the change. However, this is a good thing! Why you ask? It’s because this will serve as a learning opportunity but it will also allow me to share my experience with the tech community.
You may have heard about my Synology DS920+. There are many use cases for it and I’ve detailed a few of them for you here. One of those use cases includes using the DS920+ to create a backup repository in Veeam Backup and Replication (v11). The process to do so is outlined here for your convenience and it was very straightforward. Ok Al, where is this all going?
I recently logged into my VBR server and noticed an error. Out of curiosity, I selected the DS920+, then right-clicked on it, and then selected Rescan from choices provided.
A scan kicked off that included the messages found below along the way followed by multiple errors. I clicked on Close and then proceeded to right-click DS920+ again and then chose Properties.
With the conversion to a virtual machine, I neglected to check the IP address that was previously assigned to the physical host (which acted as my VBR server) and the Backup job found in VBR11. Now that the VM is connected to the VM Network, it has been assigned a new IP address which includes a new subnet. Unfortunately, there is no option in the Shared Folder box (greyed out in the image below) to modify the IP address when I select Properties from the image above. Once I realized this, I selected Cancel.
Next, I selected Home from the menu found in the lower-left hand corner in VBR11 and then Backup found under Jobs. Next, I selected the job (in this example, it’s called VBR Client Backup) and then right-clicked it and selected Edit from the menu.
I was then presented with the various options that I can choose from to modify any properties. For the purpose of this guide, I selected Shared Folder path from the list of options. As you can see below, the option to edit the shared folder (in this case, I had used an IP address instead of providing a FQDN – lesson learned!!) can be modified.
I replaced the previous IP of the shared folder which points to my DS920+ (aka my Veeam Backup Repository) and replaced it with the new IP of this device followed by Finish to save the changes. The changes were applied immediately and the status (found under the Last Run column) reflect this.
At this time, I felt the changes that I had made worked and didn’t expect any additional issues but unfortunately, the previously configured backup repository was still presenting problems. To circumvent this issue, I created a new backup repository and attempted to delete the previous instance.
But we’re not done yet. As soon as I clicked Yes to delete the backup repository, I immediately received this error:
To get around this, I clicked on the down arrow in the upper-left hand corner and then selected Configuration Backup. Next, select the drop-down arrow from the Configuration Backup Settings pop-up window and then choose the new configuration backup. In this example, I selected New Synology DS920+ and then OK.
From there, I was successfully able to remove the former backup repository.
Nope, we’re not done! Next, I deleted the previously configured Backup job which was created for the physical host and created a new backup job for the virtual machine.
While I’m sure there are more efficient ways of doing this, I was willing to do my part and dig deeper, albeit it took me longer than expected. However, I’m always open to feedback and you’re always welcome to provide it.
For more information about Veeam, Tech Field Day and how to become a TFD – please click on the links below:
Please take a moment to subscribe to the YouTube channel which also includes watching the various videos that were posted throughout the day. Kudos to PrimeImage Media for recording the live sessions.
Additionally, I would highly recommend Veeam’s new community program and here is where you can become a Veeam Legend.