• EN
Sticky V12 Upgrade Center

V12 Upgrade Center

V12 Upgrade Center
Show first post

103 comments

Chris.Childerhose
Userlevel 7
Badge +20

Question: i will remove VBR from VEM, and do VEM DB migration to postgresql first, and in that during emco backup file creation, if i get message of doing VBR first to postgressql still (hopefully not), i will stop and migration VBR to postgresql first instead.

 

If it doesn’t give the message, i will continue with VEM to postgresql but do i need to install postgresql first like we are going to install postgressql for VBR as in this article right in the beginning ‘https://www.veeam.com/blog/switch-sql-server-postgresql-veeam.html’?

Give that a try and see.  It does not really matter if you get the message about migrating VBR first.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
A
Userlevel 2

Succesfuilly migrated to postgresql for VBR followed by VEM. Few updates/findings>

Though EM guide says to do EM first followed by VBR as we all know that is the pattern from past also. But when you backup EM DB with example 1 in ‘https://helpcenter.veeam.com/docs/backup/em/em_db_migration.html?zoom_highlight=postgresql&ver=120’, the output says to do VBR migration first to postgresql and then come and do VEM migration to postgresql. So, this is true whether VBR server has been removed from VEM or not, i had it removed and it still came. Bottomline, the EM guide should say, do VBR first or else we should change the message in the output of below (i had pasted that blue screen in previous post here).

Veeam.EM.DB.Migration.exe /file:"C:\EM Configuration\02.emco" /backupemdatabase /encryptionpassword:Password01 /encryptionhint:thatpass

 

Secondly, the example 2 for restore of VEM, uses VeeamBackupReporting_01 in url https://helpcenter.veeam.com/docs/backup/em/em_db_migration.html?zoom_highlight=postgresql&ver=120. They should remove ‘_01’ from it bcz there is no VEM db to begin with in the new install of postgresql. We should keep it the original name as VeeamBackupReporting. Reason is during setting utility, we tend to use the default DB which is VeeamBackupReporting as it pops up like that which is normal else we have to change it to append _01 to it to proceed correctly. (https://www.veeam.com/kb4409). The KB4409 is good as he uses correct restore option in above without _01. 

 

Thirdly, the default port picture of 5433 is incorrect below in settings utility> https://helpcenter.veeam.com/docs/backup/em/dbconfig_connection_settings.html?ver=120; it should be 5432, and also if i move with windows auth’on it fails to move on to next screen even though my VEM is installed as default local admin user. I had to use the user name/passwd that i had created within pgadmin in the above screen to move on. (Also, even in this article for VBR migration to postgresql https://www.veeam.com/blog/switch-sql-server-postgresql-veeam.html where the pgadmin details are noted for veeam user creation, they forgot to put down to add the password for ‘veeam’ user that you just created. Bcz that veeam account and its password is what we have to use in native authentication with the creds).

 

Also, they should put a limitation verbiage that MFA should be disabled prior to any work with migration to postgresql or config backup also. It errors out way in the end of analysis of DB’s when we are doing restore. Thx

 

ratkinsonuk
Userlevel 4
Badge +2

AWS Custom VPC Issue

If you’ve implemented custom VPC’s (using AmazonS3Regions.xml), then you’ll have an issue trying to create Protection Groups in the B&R console. The error is something like ‘Selected data centre region does not support Sts endpoints’.

This is because v12 ships with new endpoints in the default file which need adding to your custom file. E.G. :-

<Endpoint Type="STS" Fips="false">sts.eu-west-2.amazonaws.com</Endpoint>
<Endpoint Type="SSM" Fips="false">ssm.eu-west-2.amazonaws.com</Endpoint>
<Endpoint Type="SQS" Fips="false">sqs.eu-west-2.amazonaws.com</Endpoint>
<Endpoint Type="KMS" Fips="false">kms.eu-west-2.amazonaws.com</Endpoint>
<Endpoint Type="KMS" Fips="true">kms-fips.eu-west-2.amazonaws.com</Endpoint>
<Endpoint Type="S3C" Fips="false">s3-control.eu-west-2.amazonaws.com</Endpoint>

These are specific to the region you’re using, so you’ll need to grab the default region file for the exact entries.

For info, the instructions under KB4226 haven’t been updated to reflect the new entries either.

Comment


Terms & Conditions