Preparing to Upgrade Ambari

Be sure to review the Ambari 2.6.0.0 Release Notes for Known Issues and Behavioral Changes.
You must have root, administrative, or root-equivalent authorization on the Ambari server host and all servers in the cluster.
You must backup the Ambari Server database.
You must make a safe copy of the Ambari Server configuration file found at /etc/ambari-server/conf/ambari.properties.
Plan to upgrade the Ambari Metrics service:
- Record the location of the Metrics Collector component before you begin the upgrade process.
- You must stop the Ambari Metrics service from Ambari Web.
- After upgrading Ambari, you must also upgrade Ambari Metrics System and add the Grafana component.
Optional: You may add the following property to the ambari.properties file.
stack.upgrade.bypass.prechecks=true
Adding this property allows the Express Upgrade process to start,if pre-check failures occur.
If your cluster has no access to the Internet, you must set up a local repository before you continue.

	Note
	During Ambari upgrade, the existing `/var/lib/ambari-server/ambari-env.sh` file is overwritten. A backup copy of `ambari-env.sh` (with extension `.rpmsave`) is created. If you have manually modified `ambari-env.sh` (for example, to change Ambari Server heap size), you will need to re-apply your changes to the new file manually.

​Preparing to Upgrade Ambari