Upgrading Hardened Repository ISO v2 to Veeam Infrastructure Appliance

[sys92]

Few days back I logged case: Veeam Support - Case # 08088429 they said upgrade is seem less, only repository path will change

But I see in new VHR-13 there is no "single use credentials creation" option. don't know how this connects back to 12.3.2.4854 ?

Additionally Admin and Security officer account with MFA is enforced. No information on after how many days password will expire.

If someone has to connect from 12.3.2.4854 to Veeam Hardened Repository upgraded via Veeam Infrastructure Appliance ISO no details provided.

[david.domask]

Hi sys92,

I split your post from the previous topic into a new one as your questions are a bit off topic.

If you upgrade an existing Hardened Repository deployed from the Harden Repository ISO v2 to the Veeam Infrastructure Appliance, the connection will be done using certificate based authentication as Support explained in the topic.

MFA indeed is currently enforced by default on v13.0.x; 13.1 will give the option to disable MFA if desired.

Password expiry is 60 days on 13.0.x, this will be configurable from the Host Management Console in 13.1

If someone has to connect from 12.3.2.4854 to Veeam Hardened Repository upgraded via Veeam Infrastructure Appliance ISO no details provided.

Not sure I understand correctly, but once the existing Hardened Repo deployed from the ISOv2 is updated to the Veeam Infrastructure Appliance, you will not be able to connect it to v12 backup servers, only v13.

[sys92]

I managed to downgrade, below are how to do so

1. Boot through v2 ISO -- live system
2. Login with vhradmin as username and password, it will ask you to change password
3. Now you have to rename logical volume created using lvrename command to match old lv name.
4. Now you can mount and verify your data using existing scripts
5. Again boot from v2 ISO, re-install without loosing data
6. Configure network, password etc
7. Under network menu get onetime ssh credentials veeamsvc
6. Open veeam 12 console, under linux host property reconnect using one time credentials.

Now you can use linux repo without any data loss