Hi @Kamil,
The simplest way to patch your Standby CommServe is to simply do a push update to Instance002 on your standby server (the client entity with the SQL Server Agent used for database replication) from the UI. When a push is submitted to Instance002 on a Commserve marked as Standby, we automatically apply the updates to Instance001 (The Failover Commserve itself).
This affords us a few advantages :
- We can update both client entities with a single update job
- We do not attempt to start services on the Failover CommServe
- We do not attempt to apply any database-level updates (since those Databases are in a ‘Restoring’ state and will be patched via the next Replication job that completes after your Production host is updated).
If you do need to apply the updates manually on the Standby host, we do have command line operations that will initiate the install of updates and prevent database updates from being applied as well as preventing services from starting :
InstallUpdates.exe -nostartsvc -donotupdateDB -binaryOnly
If you’ve tried the Push Install method that I listed above and it didn’t work for you, it might mean that there is a problem in the configuration of the Standby CS where Instance001 and Instance002 are not properly linked together. If that is the case, we may want to troubleshoot that via a Support Incident so we can make sure you are set up for success.
-Brian Bruno
