Once the DB is restored on server2 we
need to again switch back to server 1
In server 1 which is the SCCM site server we would need to modify site settings first, to point the site to the new SQL instance. Before performing this step all the Ports or connections between the SCCM primary site server and the new SQL instance should be working. The communication should be allowed between the SCCM site server and the new SQL instance just the way it was setup for the first SQL instance.
After the SCCM site administrator is sure about the communication between SCCM site server and new SQL instance. The can proceed with SCCM site maintenance steps, The site maintenance will require to be executed where the details of the new SQL instance would be set. While setting up the new SQL instance in SCCM site server maintenance details about SQL instance need to be provided, The details include Name of the SQL instance server followed by the SQL instance name, if SQL instance name is set to default then the name of the server need to be provided. With the name of the server and the instance name, name of SQL DB also needs to be provided. This process is shown in the below screenshots.
Provide the
Server name & DB name and click on next.
Do not click
on “Launch the Configuration Manager Console after closing”.
It’s better
to reboot Server 1 so that all the SCCM related process restarts.
After the
reboot I just created two new collections on SCCM in server 1 and they were
updated in the DB present in Server2.
No comments:
Post a Comment