Microsoft SQL and Postgres

[joker5893]

My Veeam server was originally set up on Veeam version 11, when Microsoft SQL Server was an available database option. Now that PostgreSQL is the primary database, what is the best course of action if I need to create a new Veeam server and restore the configuration and backups from my original server?

[vnikiforov]

Hello,

To import a v11 configuration database, you need a clean operational Veeam Backup & Replication v12 server (take the latest available 12.3 release) with a Microsoft SQL Server database backend. Note that the minimal source version supported by v12.3 configuration restore is v11a (build 11.0.1.1261).

The v12 setup only bundles PostgreSQL, so prepare the SQL backend yourself: download Microsoft SQL Server 2022 Express (the latest version supported by v12) and install it locally under a local admin account. Then run the Veeam Backup & Replication v12 setup from the ISO under the same local admin, point it to the Microsoft SQL Server instance, and install the product. Once the VBR console opens, use the configuration restore option to import your old v11 configuration.

The only question I have: why do you want to do this, and what is the goal? Veeam Backup & Replication 13.1 has changed so much that it is easier and cleaner to deploy a fresh v13.1 server and create the jobs you need.

If you prefer the config import path and hit technical difficulties or error messages along the way, please open a Veeam support case and provide full logs.

[joker5893]

Thank you for feedback. If I was to start fresh with Veeam 13 and create fresh jobs how can I go in and restore older backups that may be stored in glacier?

[vnikiforov]

Hello,

Yes, backups offloaded to Glacier by your old SOBR should stay restorable:

1. On the new v13.1 server, add the S3 buckets that held your capacity or archive tiers as object storage repositories - standalone, not as part of a SOBR.
2. Use the Import Backups option. It exists for exactly this scenario and covers both capacity tier and archive tier backups. If the offloaded backups were encrypted, have the password ready, the wizard asks for it.
3. Glacier restore points are not directly readable after import. Restore from the archive tier runs in two steps: a retrieval job first creates a temporary copy in the S3 bucket for the availability period you pick, then you restore from that retrieved point.

One thing to note: an object storage repository with imported backups cannot be used as a target for your new jobs unless you detach it.

Please note, this forum is not a support forum. Its goal is to have a direct communications channel with Product Management and R&D for features discussions and related questions.
If you face technical difficulties in the process please open a support case.