Moving to a New Server

[VBR-Noob]

Greetings. This is my first post out of necessity and my nickname says it all.... I am stung by the First lvl Support as my colleague has left the company and I still have very little experience, but I have read a lot in this forum or veeam documentation. Since the project has already started, I am supposed to continue it tomorrow and support from the service provider is not available until late afternoon (sorry for the long introduction):

I am supposed to move Veeam Backup to new hardware including repository!
I already understood that all jobs will be stopped and then a backup of the configuration will be created.
I have already prepared some things on the new hardware so that the users for the individual roles are available and also 3 partitions for system, installation and repository. The repository currently has a different drive letter. Veeam is already up to date with no Server hardening or MFA. The Database is also migrated to PostgreSQL.

What happens now? At the moment I would like to do the following in sequence:

- Copy the two Postgre databases from Server OLD to NEW and overwrite the databases created during installation of Veeam
- Copy all folder structures and files from the repository partition OLD to that of the server NEW and, as a precaution, use the same drive letter
- Import the configuration backup to the new server and hopefully be happy

Sorry if there are grammatical errors. I'm German and "my english is not the yellow from the egg". Also my Smartphone tries to autocorrect to german

[Mildur]

Hello Mirko

Welcome to the forum.

- Copy the two Postgre databases from Server OLD to NEW and overwrite the databases created during installation of Veeam

This step is not required and would also not work out of the box because of how we encrypt our credentials.
When you install the new backup server, a database will be deployed with the default configuration. This database can already be used for the backup server. No need to migrate the old databases by copy/paste of the database files.

To migrate the backup server configuration, configuration backup/restore is recommended.
You can follow this steps from our help center:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

1.) Stop running jobs and disable scheduled jobs.
2.) Save registry values that you changed or created.
3.) Back up the configuration database of Veeam Backup & Replication.
4.) Transfer all backup file to the new server. Use the same drive letter and folder path as on the original server.
5.) Install Veeam Backup & Replication on the target machine.
6.) Restore the configuration database from the backup.
7.) Finish the configuration.

Test on the new server if you can restore files before running any backup jobs. To make sure that the backup data migration was successful.

Please note:
- In case you had reFS as a volume on the original backup server, backup files will be copied in their full size to the target server. 12* 1TB on the source server may have used 1-2TB of storage. After a manual copy process, those files will use the entire space: 12 TB.

To migrate with FastClone, you could:
1.) Migrate the backup server and configuration only to the new server.
2.) Then add the old backup server as a repository server and map all jobs to the backup files on the old server
3.) Then use our backup move feature (since v12.0) to migrate all backups FastClone aware from the old machine to the new machine.

Best,
Fabian

[dspringer]

Lol. Nearly the same question I asked some minutes ago. Mildur you are always my ultimate hero

[VBR-Noob]

Danke, i will try my best and then let the external Support Check it.

[VBR-Noob]

Little Feedback for my Problem. The Topic can be closed and everything is fine. At the end I was too fast with preparation. Don't give your new repository the same drive letter and install the backup of your config without having something in the new drive... I was clicking around and my veeam made a scan of the repository. As there were no Backups existent it deleted something in the configuration.

We had to attach the old repository with SMB and then move all data. One of my jobs seemed stuck but was successfully ended 28h later. It was the Fileserver with 10 Backups... Later we mapped the jobs and also updated the chain.

Today all jobs are finished successfully and I got the Tipp to recreate a new Job with all VM and GFS instead of 6 standalone jobs.

[Mildur]

Hi Mirko

Thank you for coming back with your feedback.

Best,
Fabian

[dspringer]

Congratulations. I'll keep that in mind when the time comes for us to change the hardware. But then it will be a bit trickier anyway, as we're also switching to Linux.
(Maybe by then there will also be a tape connection when using hardened repositories )