Central admin server

[koos147]

Good day,

Around a year ago we went from Veritas to Veeam.
by that time we installed it on the backup server and configured it to backup all Hyper-V servers.
The same server has the tape drives connected. and duplicate it to an off-site location where the backup is placed on a de-duplication storage.
It runs smooth. but now it is time to replace the hardware, and i was looking in the setup.

In the Veritas time. we had a VM with the backup application who hold all the catalogs and dispatched the jobs to the real backup servers.
we had this vm in replica to the off-site location so we where always able to restore a backup from one of the 2 storage servers.
the vm itself was largley the database with catalogs and didn't do the load.

Can we do the same with veeam?
I have installed the enterprise manager on a VM. but as far as i can see i still need to install and configure the B&R software on the backup server.
the enterprise manager is only monitoring the jobs (as far as i understand)
the off-site server only has a agent. no server. so we can't use it to restore backups when the primary site is down. (yes, we have the data.... so yes we can restore in the end. but would be better if it is ready to go)

Any thoughs / advise would be great.

[david.domask]

Hi Mark, welcome to the forums.

For migrating the Veeam Backup and Replication installation to another server, the process is outlined here in our User Guide. In short the process involves just installing Veeam Backup and Replication on the desired server, then using the Configuration Restore/Migration tool to migrate the Configuration Database to the new Veeam server.*

You are correct, Enterprise Manager serves as a single-pane-of-glass for managing your Veeam environments, so on the replacement server, you'll simply need to follow the process outlined in the User Guide link above.

If I understand your question right about how to accomplish an off-site Veeam server while you're preparing the new Veeam server, use the same process outlined above, but it also will require that Veeam Backup and Replication is installed on the machine you plan to migrate the Veeam Configuration Database to.

* Veeam Configuration Database is likely equivalent to the backup catalog you're used to with other products -- the Configuration Database has the Session history, backup catalog, job configurations, and a lot more, and should be always be used for migrating. There are two modes with the Configuration Database Restore, Restore and Migrate. Both will work, but Restore has some extra steps during the process that Migrate will handle.

[koos147]

Good day David,

Thanks for the quick response. the migrate to new server is clear to me. it was just a good moment to stand still and check our setup.

The actual question will be, what happens when we lose our primary site?

For now i guess that we need to manual install the software on the off-site repository and restore the configuration backup file from there?

With Veritas we could just simply order the off-site server to start the restore. (no i don't promote Veritas, there are to many reasons that we switched to Veeam)
we preferer to have the off-site server ready for the worst.

If we install the software in a VM. and make both backup servers "only a repository" will all data flow via the vm. or will the agent on Hyper-V send the data directly to the repository?