Can Windows based Veeam v13 config backup be restored to v13 software appliance?

[mjm599]

Hi All,

We had a VMware VM with windows 2022 installed on it and then Veeam v13 installed on that as the B&R Server.

The storage has failed and we have lost the above VM.

We have a Veeam config backup.

Could we deploy a new Veeam v13 Software Appliance (Rocky Linux) then once deployed restore the above config file that was created in the windows veeam vm?

Or do we need to deploy windows server again then install veeam v13 then restore the config?

Thanks,

[Mildur]

Hi Mjm599,

Yes, but please note that this is not a typical configuration restore and will not work out of the box.

If you plan to migrate or restore from a Windows-based Veeam Backup & Replication server to the Veeam Software Appliance, please follow the process documented in KB4800: https://www.veeam.com/kb4800
Another important source of information is the VSA Conversion Portal: https://go.veeam.com/vsa-conversion

The Windows-based source backup server must have been on the latest supported 13.0.x patch level before performing this migration. Older v13 builds are not recommended due to known migration-related issues. And you need to open a support case to request a migration key for your product license.

If your Windows-based backup server was already been upgraded to v13.1, then a configuration restore or migration to the Veeam Software Appliance is currently not possible. In that case, you would need to restore the configuration to a Windows-based backup server and wait for a future release where the migration path becomes available again.

Please review both resources I shared carefully before starting, as the migration has specific prerequisites, limitations, and post-migration considerations.

Best,
Fabian

[mjm599]

Hi Fabian,

Thanks for the reply,

As the backup server has been lost due to array failure, all we have is the veeam config backup, is there any detail in that to see what build the windows veeam B&R Server was on?

I suspect it was just on the initial v13 release.

As the original veeam server is gone it seemed like a good time to consider migrating to the software appliance rather than deploying a 2022 server then installing veeam on that, however do you think thats the only option we have if the config shows Veeam was on v13 initial build?

[Mildur]

The version can be retrieved from the configuration backup file, as it will be checked during the configuration restore. Alternatively, it can be retrieved from the log files.

However, since the original environment was lost, it may be better to restore the configuration to a Windows-based backup server running v13.0.3, and then open a support case for the migration to Veeam Software Appliance.

If you ask our support team to provide you the migration key, they will request the logs. Without logs, our support team cannot guarantee that the migration will work. There are limitations in Veeam Software Appliance with v13.0.x, and if your previous environment used any of this unsupported configuration, the migration will not work.

Best,
Fabian

[mjm599]

I have opened the backup config file and see the below detail:

r o d u c t . I d ›æ±xDcÒy÷V P r o d u c t . P l a t f o r m P r o d u c t . N a m e ! V e e a m B a c k u p a n d R e p l i c a t i o n 1 3 . 0 P r o d u c t . V e r s i o n . M a j o r
P r o d u c t . V e r s i o n . M i n o r P r o d u c t . V e r s i o n . B u i l d P r o d u c t . V e r s i o n . R e v i s i o n P r o d u c t . D a t a b a s e . A c t i v e P r o d u c t . D a t a b a s e . C o n f i g u r a t i o n s P r o d u c t . D a t a b a s e . S c h e m a Y& Y& P r o d u c t . D a t a b a s e . C o n t e n t Y& Y& B a c k u p . C r e a t i o n . T i m e wš}tðÞH B a c k u p . C r e a t i o n . D u r a t i o n ®Gáz´—Ã@ B a c k u p . J o b . N a m e B a c k u p C o n f i g u r a t i o n J o b

So would you suggest deploying the software appliance v13 and restoring the config? Or will i have to deploy windows again and restore the config that way?

Thanks,

[Mildur]

Hi Mjm599,

I cannot say based only on this.
Since restoring to Veeam Software Appliance currently requires a support case (a mandatory step), I strongly suggest opening a case and explaining to Support that you lost your backup server and are now considering restoring to Veeam Software Appliance instead of a Windows-based backup server.

Our Support team will try to determine if your previous configuration can be run on a Veeam Software Appliance, or guide you to restore to a Windows-based backup server instead.

Best,
Fabian

[mjm599]

Hi Fabian,

ok thanks for the reply, for now i have deployed windows again and restored to a new veeam installation.

We also lost the windows based Veeam proxy servers.

Can i deploy the infrastructure appliance as the new proxy servers so this moves these away from Windows while then connecting bnack to the windows veeam VBR Server?

So it would then be windows based VBR 13.0.3 server + VIA 13.0.3 Proxy VMs?

[Mildur]

Yes, you can do that.
A Windows backup server can use Veeam Infrastructure Appliance for remote components such as proxy or repository server.

Best,
Fabian

[mjm599]

ok, in terms of the specification for these VIA Proxy servers, the documentation doesnt seem clear: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

The above document details the spec as 120gb disk + 120Gb disk, so 2 disks, but that seems to be if you are deploying VIA to be the B&R Server.

For a Proxy Server, what disk would be needed and RAM / CPU? Would it be as detailed for the VMware proxy thats a single 400mb disk + 2vCPUS + 2GB RAM: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

Thanks,