Veeam on a new Server

[vmtech123]

If I want to stack up a new server for Veeam rather than an in place upgrade. Is there a way to do it utilizing the external SQL database and retain everything?

If I export the config, and import it, it basically tells me it's going to overwrite the database.

I'd also like to avoid doing a catalog of our tape libraries as it takes a pretty long time to do so and the document says to wait until it is finished before moving forward.

Last, we have Enterprise Manager, but it appears the VBRCatalog is on our VBR server as well. Will I lose this on my new server? Can I just copy and paste it over to the new VBR? Is it even required?

I am on the latest version of VBR 11a. I'm having an issue with Windows Updates on the server so I figured it was a good opportunity to stack up Server 2022.

Thanks

[HannesK]

Hello,

Is there a way to do it utilizing the external SQL database and retain everything?

yes. VBR and Enterprise Manager can be connected to a database that is hosted on a different machine. The Veeam Configuration Database Connection Utility is there to help

If I export the config, and import it, it basically tells me it's going to overwrite the database.

not sure what is meant here... restore can be to a new database (actually that's the most common scenario). See user guide

For Enterprise Manager, there is KB1889

I would do a full migration. Remote server sounds overkill to me.

Best regards,
Hannes

[Hindawi]

Hi vmtech,
If you need to migrate Veeam Backup & Replication to another server, you can back up its configuration database, install Veeam Backup & Replication on the target server and restore the configuration data from the backup. As a result, you will have a new Veeam Backup & Replication server with all settings, jobs and backup infrastructure elements from the old server.

It is recommended that you use Veeam Backup & Replication tools to create configuration backups and migrate the configuration database. If you use native Microsoft SQL Server tools, after migration, some information, such as secure configuration data, may not be accessible.
https://helpcenter.veeam.com/docs/backu ... ml?ver=110

Veeam Backup & Replication comes with the Veeam.Backup.DBConfig.exe utility that allows you to manage connection settings for Veeam Backup & Replication and/or Veeam Backup Enterprise Manager configuration database. Using this utility, you can:

• Connect to a different database on the same or another Microsoft SQL Server instance. If you specify a database that does not exist yet, it will be created on the selected server.
  Change authentication method for database connection. Possible methods are Microsoft Windows authentication and Microsoft SQL Server authentication.

https://helpcenter.veeam.com/docs/backu ... ml?ver=110

[vmtech123]

I did the export config, stacked up new server imported. It worked.

I was wondering in the future to save time, can I use the existing SQL DB if it is external.

My other question is can we disable the catalog of tapes if the export is taken, server is powered down then config is improted.

There would have been no changes after the export was taken, but the catalog took a few days.

[HannesK]

can I use the existing SQL DB if it is external.

hmm, I thought I answered that question already with "yes" earlier The main challenge is that the passwords were encrypted with the machine key of the old backup server. so the new backup server cannot decrypt the passwords from the remote database. that's why I linked to the configuration restore.

My other question is can we disable the catalog of tapes if the export is taken, server is powered down then config is improted.

There would have been no changes after the export was taken, but the catalog took a few days.

I got lost here. What is the goal, what do you try to achieve? The tape catalog is stored in the configuration database (SQL). The configuration backup is a dump of the SQL database.

[vmtech123]

Well I completed the migration and it worked by using the back up config and restore config as you suggested.

My main issue is the time it takes. Specifically the catalog of the tape library. It was a few days.

Because I was able to disable everything, do a clean config backup, and power down, I was just thinking that the SQL DB is intact, the catalog is good, even the index could be copied over.

When I was given the option to "restore" I think of that as being down and needing to restore a server from backup.

With the option to "migrate" to me this is an intentional operation. Perhaps the option to not catalog the library if no changes were made could be available. Better yet, have a "prepare migration" on the original server, when you activate it, it will disable all jobs etc. create a config backup with a flag set and don't allow jobs to be re-enabled on this server. When you import this to the next server it will know the backup is consistent and good from the flag.

One step further if a user is ok with a new IP for their Veaam server rather than reusing the old one, during a migration, point one server to the other. It could basically be an automatic process and copy over the index folder and more.


Either way it was a good prep to know in a DR scenario "create a new Veeam server and restore from backup" is not a quick task. I'll add 2+ days to the catalog tape libs. Other than that though, the process is easy and works extremely well.

I appreciate where you guys have gotten the Tape functionality.