Clone your existing SC 3.4 deployment with data to ensure you can safely do an upgrade independent of your current environment. If you prefer or insist on an in-place upgrade, do not mind the downtime, and have a way to perform a reliable backup/restore in the event of an upgrade issue, you can skip this step.

1. Previous stage’s collection of metrics was completed.

2. Basic familiarity with Cassandra DB, service management & log file locations

Choose either single OR multi-node below depending on your deployed topology.

SC 3.4 environment cloned.