DOC-1882-upgrade-db-offline

modules/installation/pages/upgrade.adoc

@@ -7,7 +7,8 @@ TigerGraph to TigerGraph {page-component-version}.
 
 ===  Check release notes for changes in functionality
 
-IMPORTANT: Always check the xref:release-notes:index.adoc[] for all the versions between your current version and your target version, for deprecated features, known issues, or other behavioral changes.
+[IMPORTANT]
+Always check the xref:release-notes:index.adoc[] for all the versions between your current version and your target version, for deprecated features, known issues, or other behavioral changes.
 You may need to make migration changes to your TigerGraph application either before or after the upgrade.
 If you have any questions or uncertainty, please contact TigerGraph Support.
 
@@ -19,15 +20,26 @@ As a precaution, it is always a good idea to make a full backup before performin
 System upgrade does not support version rollback at this time.
 ====
 
-=== Preparation from a version older than 3.2
+=== Prepare a pre-3.2 database
 
 . First perform a backup xref:backup-and-restore:index.adoc[using GBAR (Graph Backup and Restore)] on your existing installation.
 . *Restore* your installation with GBAR to rebuild it.
 This step is necessary because TigerGraph 3.2 made major changes to the Graph Storage Engine and a restore is needed to remove certain files that would make the upgrade operation fail.
 . Ensure that the restore is completely finished and there are no pending graph modifications (schema change, insert, update, or delete) before starting the upgrade.
 You can do this by calling the xref:tigergraph-server:API:built-in-endpoints.adoc#_rebuild_graph_engine[/rebuildnow] endpoint and waiting until there are no more PullDelta messages being printed in the logs.
 
-=== Upgrading a CRR system
+=== Ensure that the database is inactive
+
+[IMPORTANT]
+Ensure that the database will be inactive throughout the upgrade process.
+
+. Stop any new database requests.
+. Ensure that all previous operations such as queries, loading jobs, schema changes, and data updates and deletions are completely finished.
+Check the appropriate logs.
+Call the xref:tigergraph-server:API:built-in-endpoints.adoc#_rebuild_graph_engine[/rebuildnow] endpoint to force the data store to consume all pending updates and then wait until there are no more PullDelta messages being printed in the logs.
+
+== Upgrading a CRR system
+
 To upgrade the TigerGraph software on a CRR system, follow this sequence of steps.
 
 1. Disable CRR on your DR cluster.