Complete hardware replacement

[dspringer]

Hi, does anyone know of a documentary that looks at a complete hardware swap?
The server of an independent subsidiary is EOL this year and we are replacing it. Everything is on individual partitions - Veeam installation, PostgreSQL, repository. Also a connection to tape library.
I've already looked at the official migration documentation (https://helpcenter.veeam.com/docs/backu ... ml?ver=120). But it doesn't mention the repository or the PostgreSQL.

Are they simply transferred to the new server using copy+paste, with the PostgreSQL data then overwriting the data from the installation? Then import the last *.bco from the configuration backup? I can at least say that the old server already has ReFS 64kb.

There's still some way to go, but I'd like to be informed accordingly.

[Mildur]

Hi David

The server of an independent subsidiary is EOL this year and we are replacing it. Everything is on individual partitions - Veeam installation, PostgreSQL, repository. Also a connection to tape library.
I've already looked at the official migration documentation (https://helpcenter.veeam.com/docs/backu ... ml?ver=120). But it doesn't mention the repository or the PostgreSQL.

The documentation article you have linked explains how to migrate the configuration from the old server to a new backup server.
A new Server installation will also install a new PostgreSQL instance. And our configuration backup + restore wizard will transfer the the configuration from the old database to the new database. No need to copy database files around.
- Back up the configuration database of Veeam Backup & Replication.
- Restore the configuration database from the backup.

I can at least say that the old server already has ReFS 64kb.

Repository data has to be migrated manually or with Veeam Backup & Replication. But doing so manually with file copy tools or windows explorer will blow out all backup files. FastClone won't be used.

To migrate with FastClone, you could:
1.) Migrate the backup server and configuration only to the new hardware.
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]

Thanks at this point again. I spotted the post of Mirko some seconds ago. When I read both answers, I am definitely on the safe side.
Is it then sufficient if all services are stopped on the old server so that I can simply connect the volume from the old one to the new one as a repository? In this case, the move process from Veeam itself would of course be ideal. I was just not quite sure because I had read that a target drive cannot be used as a repository by 2 Veeam servers. However, this certainly referred to simultaneous use.

[Mildur]

To be safe, i would remove backup jobs and repositories from the configuration on the old backup server.
Just to be sure that the old server doesn't interact with the path.

Stopping all services may also be possible before adding the repository. Some services have to be started again because they are required for backup repositories. As long the "backup service" doesn't, everything will be great.

May I ask, is the other topic you mentioned related to your project? Is Mirko your customer? Or was it just a coincidence that the same question was raised twice? If it is indeed related, I would like to merge both topics together.

Best,
Fabian

[dspringer]

Really lucky coincidence. I think you only manage something like this once in 100 years.
For my part, I still have a little time before the changeover. But I hope he'll let us know if everything went smoothly.
But you are welcome to move my topic to him anyway. It doesn't have to exist twice.