Welcome to DEL EMC Data Domain.
How two series upgrading data Domain reference, DEL MC knowledge base article number 545332 This video was created too demonstrate the data domain upgrade process.
This is to make upgrades easier to accomplish note that this procedure is not for DD A. This video presents the following how to log into the data domain server.
Download and upload the code version. Upgrade packages perform pre and post upgrade health checks and the upgrade commands before you start, make sure you read the KB article carefully. Also check the compatibility and if MD you upgrade will be needed before you start download the target code upgrade file, then upload it to the server to do this.
Open the Dell support website and log in with your user name and password search for the target code version under the resources page, select downloads and drivers then click on data domain operating system of the target code version.
In this video, we are upgrading data domain to version 620.35. Scroll down to the last page. Then click I accept it will open a new page. Scroll down to the last page. Click on the rpm file to start download.
Once the download is complete, open the data domain manager use this admin as your user name, then type your password to log in, navigate to the maintenance tab. Click on upload upgrade package, select browse locate and select the file.
Then click ok, open Autti session type the IP address or the host name of the data domain server log in using the SIS admin account first validate the serial number and the host name of the data domain server. Do this by running the system, show serial number and host name commands.
As indicated, confirm you have the correct IP address of the server to be upgraded. Confirm this data domain is not part of an IDP. If it is part of an IDP, it should be upgraded within the IDP upgrade. Check the current code version installed by running the system show version command check if any alerts discovered if yes, determine whether it can be cleared or an action needs to be taken.
Double check to make sure the error is not a showstopper for the upgrade. Now check the file system status and make sure it state file system is enabled and running.
Confirm the post comp partition has at least 10% free space by running the DF command check if the cleaning process is running if yes, stop the cleaning process before proceeding with the upgrade check. If cloud tier is enabled.
If yes, stop any data movement or running cloud cleaning processes, check the replication configuration using replication show config command.
If it shows zero in the CTX column, it means it's ming and both servers need to be upgraded at the same time to check if any jobs are running. Run replication shows stat's command. If initialization is in progress, it needs to be stopped before proceeding with the upgrade.
If only replication jobs are running, we can proceed with the upgrade. Normally check for disc reconstructions or failed discs and perform disc reliability check. Please note that the disc reliability check is not valid for D DVD, check the network traffic and ensure that no backup service stores are running, then press control C to exit the loop check for any running NFS or CIFS jobs and stop them.
Now log into the SC mode. The default password for SC mode is the serial number check. The registry is healthy by running the checked command to validate or pass as indicated.
Finally check that the upgrade file is correctly placed in the DDR var releases directory. Now it is time to reboot the system before we start the upgrade to monitor the system.
Open a command prompt and ping the data domain IP address, ping the host IP when the host is back online, restart the putty session and log in using the sis admin account run system show serial number check that the system's state is good after the reboot list, the content of DDR vir releases to get the code version upgrade file.
The last step before starting the upgrade is to run the upgrade precheck. The upgrade precheck validates the integrity of the package do not run the upgrade if issues are detected which may cause the upgrade to fail. Once the upgrade precheck is done, make sure it states upgrade precheck found no issues.
Now, upgrade can be started to start the upgrade type system upgrade, start, then copy and paste the upgrade rpm file. When the upgrade starts, it runs the upgrade precheck again. Then it installs the code version. Finally, it reboots the data domain.
After the upgrade precheck is done, the workflow starts the installation, monitor the workflow until it reboots the server. Now it prepares the system to reboot, shutting down the file system to monitor the file system, pin the host through command line.
Once the system is online, restart the patty session, then log in monitor the upgrade by using the system upgrade, watch command. When completed the message upgrade successfully completed will be displayed.
The last step is to validate the installed version is the correct upgraded version and also check the file system status and alerts validate all checks passed.
Thank you for watching.
