The right way of upgrading the Analyst Portal with 'ServiceManagement' DB in a SQL AG

Stoyan_Chalakov

Hi Guys,

my Analyst Portal Upgrade just failed with:

"Failed to create management database  ServiceManagement on AGListenerName.domain.com : The operation cannot be performed on database "ServiceManagement" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.

ALTER DATABASE statement failed."

So I did a simple search and found this topic:

Problem Installation Always On with Cireson System Center Service Manager Portal

Because I am not quite sure, I decided to ask again about the "right" way to do this if the 'SrviceManagement' DB is in a SQL AG:

Q: If I get this right, I need to remove the DB from the AG, then point the installer to the node, holding the DB and complete the install. After the install, I can again take the DB into the AG and chnage the Web.Config file at C:\Inetpub\CiresonPortal accordingly? 

Q: Is that right? What about the SCSM DB setting?

Q: What about the failed install? Can I just attempt the Upgrade again or do I need to follow certain rollback procedures?

A big thanks in advance for your comments!

Regards!

Justin_Workman

I'm going to work backwards. 

You can just run the installer again.  No need to roll anything back.

The SCSM database setting will be fine.  It's just to populate a connection string for the portal to connect to SCSM later.  The installer doesn't actually affect(write) the ServiceManager database. 

You do in fact need to remove the ServiceManagement database from the AG, then put it back in the group once installation is complete. You should be able to point the installer to the DB itself and not have to change any configuration after installation though.

Brian_Wiest

Justin_Workman said:

You do in fact need to remove the ServiceManagement database from the AG, then put it back in the group once installation is complete. You should be able to point the installer to the DB itself and not have to change any configuration after installation though.

Just to be clear Point the installer to the DB itself via the listener. When you remove the DB from the AG the listener will still see it on the primary instance. After the install is complete add the DB back to the AG and then you can verify the server remains up after a fail over.

Justin_Workman

I'm going to work backwards. 

You can just run the installer again.  No need to roll anything back.

The SCSM database setting will be fine.  It's just to populate a connection string for the portal to connect to SCSM later.  The installer doesn't actually affect(write) the ServiceManager database. 

You do in fact need to remove the ServiceManagement database from the AG, then put it back in the group once installation is complete. You should be able to point the installer to the DB itself and not have to change any configuration after installation though.

Stoyan_Chalakov

Hi Justin,

thanks for the clear reply. 

Wish you are great weekend!

Regards,
Stoyan

Brian_Wiest

Justin_Workman said:

You do in fact need to remove the ServiceManagement database from the AG, then put it back in the group once installation is complete. You should be able to point the installer to the DB itself and not have to change any configuration after installation though.

Just to be clear Point the installer to the DB itself via the listener. When you remove the DB from the AG the listener will still see it on the primary instance. After the install is complete add the DB back to the AG and then you can verify the server remains up after a fail over.