Sticky V12 Upgrade Center

V12 Upgrade Center

V12 Upgrade Center

Show first post

103 comments

Userlevel 7
Badge +10

hey there @Aman.Nangia → Thanks for sharing this. 

Hard to determine if the above has everything covered. One thing I have learned over the years is to explicitly separate architecture changes from upgrades. And use the config backups to help with architecture changes on the destination version. 

Userlevel 7
Badge +20

To get to target picture (there are 14+ VBRs), here is my high-level plan. Pls let me know your thoughts. Thank you

 

High-level Steps

 

  1. Stand up the new VM 2022 for EM (same hostname, with different or same IP as source EM) but not on network yet. (Do NOT install EM yet)
  2. Stand up the new VM 2022 for Veeam One (same hostname, with different or same IP as source VeeamOne) but not on network yet. (Do NOT install Veeam One yet)
  3. Take source EM v11 DB backup and shutdown services on source EM and disconnect from network
  4. Take source VeeamOne v11 DB backup and shutdown services on source VeeamOne & disconnect from network
  5. Update DNS accordingly per steps 1 & 2
  6. Install same v11 build for EM on new EM VM and import sql express DB
  7. Install same v11 build for VeeamOne on new VeamOne VM and import sql express DB
  8. Validate new EM & VeeamOne, working as normal with existing VBRs (all v11 & sql express)
  9. Upgrade veeamOne to v12
  10. Upgrade EM to v12
  11. Upgrade VBRs to v12
  12. Validate EM & VeeamOne, working as normal with existing VBRs (all v12 & sql express)
  13. Take VeeamOne v12 sql express DB backup (either thru SSMS and/or dbconfig tool) & migrate its DB to SQL Standard (DB on remote machine)
  14. Take EM v12 sql express DB backup (either thru SSMS and/or dbconfig tool) & migrate its DB to SQL Standard (DB on remote machine)
  15. Validate EM & VeeamOne, working as normal with existing VBRs (all v12, SQL std for EM/VeeamOne & sql express for VBRs)

These steps look good but if the SQL Standard exists once you take backups why not restore to there to avoid steps 13/14?  Just a thought as you can direct both EM/VONE to the SQL Std box on the new Win2022 servers when ready.

Userlevel 2

steps written above

Userlevel 2

To get to target picture (there are 14+ VBRs), here is my high-level plan. Pls let me know your thoughts. Thank you

 

High-level Steps

 

  1. Stand up the new VM 2022 for EM (same hostname, with different or same IP as source EM) but not on network yet. (Do NOT install EM yet)
  2. Stand up the new VM 2022 for Veeam One (same hostname, with different or same IP as source VeeamOne) but not on network yet. (Do NOT install Veeam One yet)
  3. Take source EM v11 DB backup and shutdown services on source EM and disconnect from network
  4. Take source VeeamOne v11 DB backup and shutdown services on source VeeamOne & disconnect from network
  5. Update DNS accordingly per steps 1 & 2
  6. Install same v11 build for EM on new EM VM and import sql express DB
  7. Install same v11 build for VeeamOne on new VeamOne VM and import sql express DB
  8. Validate new EM & VeeamOne, working as normal with existing VBRs (all v11 & sql express)
  9. Upgrade veeamOne to v12
  10. Upgrade EM to v12
  11. Upgrade VBRs to v12
  12. Validate EM & VeeamOne, working as normal with existing VBRs (all v12 & sql express)
  13. Take VeeamOne v12 sql express DB backup (either thru SSMS and/or dbconfig tool) & migrate its DB to SQL Standard (DB on remote machine)
  14. Take EM v12 sql express DB backup (either thru SSMS and/or dbconfig tool) & migrate its DB to SQL Standard (DB on remote machine)
  15. Validate EM & VeeamOne, working as normal with existing VBRs (all v12, SQL std for EM/VeeamOne & sql express for VBRs)
Userlevel 7
Badge +12

You‘re welcome :)
It won‘t be an issue for the EM server. But you won‘t see (new) data or will able to restore data in EM of the already migrated VBR servers until you migrate the EM too.

 

Best,

Fabian

Userlevel 2

Minor question on above upgrade path topic: The interm period between steps 4 & 5 bcz of the qty of VBR servers (10+) which will span over 2 days say, should be ok you think bcz some VBRs will be at sql and some will be already upgraded to postgress but EM is still at sql which is only until in step5 getting migrated to postgres. Thx again

Userlevel 2

Thanks a LOT Fabian :)

Userlevel 7
Badge +12

Veeam One only supports MSSQL and will work with either VBR/EM on PostgreSQL or MSSQL.

I would first upgrade Veeam One. As Step 0 :) Historical data from MSSQL will not be lost after step 4 + 5.

  1. Upgrade Veeam One
  2. Upgrade EM but stay on MSSQL
  3. Upgrade all VBR but stay on MSSQL
  4. Migrate all VBR databases to PostgreSQL 
  5. Migrate your EM database to PostgreSQL

 

Best,

Fabian

Userlevel 2

Thanks Fabian; spot on. And for Veeam One what should i do today. As step 1a), can i upgrade him to v12 and leave it at SQL, and will he able to communicate with EM v12 (postgresql) i.e. after step 4, and also can he maintain the historical data of VBR servers at v11 SQL prior to the upgrades? Thx to let me know

Userlevel 7
Badge +12

@Aman.Nangia

VBR and EM must run on the same configuration database engine.

Enterprise Manager server on PostgreSQL cannot manage a Veeam Backup & Replication server which is still on MSSQL. Your V11 servers will not show data in a Enterprise Manager v12 with PostgreSQL database.

But if you leave the database on MSSQL, your V11 server can be managed by the Enterprise Manager v12.
 

I recommend the following approach:

  1. Upgrade EM but stay on MSSQL
  2. Upgrade all VBR but stay on MSSQL
  3. Migrate all VBR databases to PostgreSQL 
  4. Migrate your EM database to PostgreSQL

 

Best,

Fabian

Userlevel 7
Badge +20

Hi. Since it’s a multi-site Veeam architecture (all components at V11a latest build) already running in prod i.e. Ent Mgr, Veeam One, ten+ VBR (no VCSP or backups to cloud yet in any form) all at v11a. We want to upgrade the entire  environ to v12 and also move to Postgres for each component. We are looking at best strategy over a 2 week project hopefully. Question is: Can Ent Mgr at v12 (postgres) & veeam one at v12 (postgres) coexist (aka sit) with mixed VBRs (some VBRs still at 11a (sql) ready to be upgraded to v12 (postgres), and some VBRs already upgraded to v12 (upgraded to postgres also). All pointers welcome. Thx

VEM and VBR can run on Postgres but VONE does not support it yet.  Just FYI.

Userlevel 2

Hi. Since it’s a multi-site Veeam architecture (all components at V11a latest build) already running in prod i.e. Ent Mgr, Veeam One, ten+ VBR (no VCSP or backups to cloud yet in any form) all at v11a. We want to upgrade the entire  environ to v12 and also move to Postgres for each component. We are looking at best strategy over a 2 week project hopefully. Question is: Can Ent Mgr at v12 (postgres) & veeam one at v12 (postgres) coexist (aka sit) with mixed VBRs (some VBRs still at 11a (sql) ready to be upgraded to v12 (postgres), and some VBRs already upgraded to v12 (upgraded to postgres also). All pointers welcome. Thx

Userlevel 7
Badge +10

Updated today (and last month) with two updates KB4420 and KB4443.

Userlevel 1

Upgrade done, no issues: 

 

Userlevel 7
Badge +22

KB Update done without issues

Userlevel 7
Badge +17

Funny,  Veeam chose to name/number  the iso release 413 and not 412 :

 

This is the date, not the version number….

Userlevel 1

Funny,  Veeam chose to name/number  the iso release 413 and not 412 :

 

Userlevel 7
Badge +20

Combined ISO is already there isn't it ?   

 

Yes, if you use the Download ISO link it will download the one with the latest patch.

Userlevel 1

Combined ISO is already there isn't it ?   

 

Userlevel 7
Badge +10

Good to hear that the KB update for V12 went well. I updated the main part of this in Post Publish Updates on Friday. I expect we’ll have a combined ISO at some point, which I’ll note. 

Userlevel 1

I will upgrade with new iso from V11  tomorrow. 

Userlevel 7
Badge +20

@Rick Vanover

KB is now updated for the new patch release.

https://www.veeam.com/kb4420

Time to update 😎

Update was easy and no issues.  👍

Userlevel 7
Badge +8

@Rick Vanover

KB is now updated for the new patch release.

https://www.veeam.com/kb4420

Time to update 😎

Userlevel 7
Badge +12

@Rick Vanover 

KB is now updated for the new patch release.

https://www.veeam.com/kb4420

Userlevel 7
Badge +10

I heard a rumor that V12  patch release is coming soon. Any truth in it ?

Yes, there will be a comprehensive patch. I plan on updating this right away when that KB lands.

Comment