Docs for the SAP repserver cover:
- Upgrading the repserver by overwriting an existing directory
- Upgrading the repserver by installing to a new directory
- Upgrading the whole repserver at once by calling the repserver executable with the "-upgr" option (aka the "one step" method)
- Upgrading the repserver using rs_init to upgrade the RSSD and all the databases connected to the repserver, but one at a time.
Unfortunately, the documentation pages covering this (within the
Replication Server Configuration Guide for UNIX) overlap and jump back and forth in describing the various scenarios making them difficult to follow.
As a service to people who might someday try this, here are my notes for doing a repserver in-place (ie. overwrite the files in the existing repserver directory) upgrade using the "one step" -upgr option (also called the "repserver upgrade utility" and the "seamless upgrade"):
- Run "admin who" to get a list of all ASE servers accessed by the repserver. Save this output.
- Do 'suspend log transfer from all'
- The docs say stop the RSSD db rep_agent, but that only applies to repservers with routes
- Run 'admin quiesce_check', wait for the repserver to be quiesced
- It doesn't actually say it here, but shutting down the old version repserver is implied. Shutdown the repserver at this point.
- Backup the RSSD
- Backup the pre-upgrade repserver/<name> directory tree
- Upgrading RSSD or ERSSD and User Databases with repserver ([sic] should say "using the one step upgrade utility") - Says, before using the repserver one step upgrade option (ie, running the repserver executable with the -upgr option) you have to: