Hello and welcome. This is the video tutorial on the upgrade procedure for Data Domain and Data Domain virtual edition. The first step is to download the R PM file. You can do that by logging on to dell.com/support. Just search for data domain. Yeah, once they select model to DDOS, then pick the code family here. We're doing 7.7. Yeah. Then on the drivers and downloads tab pick the target code. We did 7.7 0.5 0.20 hit download there. You'll be taken to the license agreement and then you'll see the download options. Our next step is to upload the R PM file to the data domain gui first log into the G A using your CIS admin user name and password. Next head to the maintenance uh system area.
You should take this opportunity to delete any old R PM files like I'm showing here and simply select the package and hit. Ok. You may also consider uploading the R PM file via a network share. You simply have to mount the directory show on the screen. Now DDR releases the first phase of our precheck is to verify the system and ensure it's ready for the upgrade. First, we'll log in as you log in. You'll see the data domain version right there 7.2 0.0 0.95. So now we'll check the serial number system, show serial and o next we'll check the host name. Yeah. And then finally we'll check the network settings, net show settings. Yeah. Yeah. It's a good idea to keep this handy for later.
The MT list command will help us to double check whether or not the data domain is a part of an ID P A system. We're looking for avatar trees and ESSX dot logs and trees. So we'll pull it up here. So we'll go ahead and type an empty list here. We don't see any of those listed a var or ESSX logs entries. That means we can move on if you're not sure. Or if you see those entries, please contact your system admin. You don't want to do this upgrade process on an ID P A system. Next, we'll run the H A status command. We need to be certain that the data domain is not part of a high availability pair as that has a separate upgrade procedure. We expect to see that the command is not available on this node and there we have it.
We'll move on to checking the status of the system. Our first command will be alert, show current what we're looking for here are any alerts that might be related to hardware or maybe file system issues. In this case, we just see an alert for the mail server which is safe to clear. So let's just do alerts clear ID and then the id shown in the output above and there we go, the alerts are cleared next up. We'll run a series of commands to check the file system status. Whether or not cleaning is running, if any data movement is happening or if there are any network jobs, we'll stop those. If the, if we find any here, we'll put files status. So it's enabled and running. But also lets us know that there's a cleaning going on. So we'll go ahead and say files is clean. Stop. Yes, we don't have a whole lot going on in this CD VE but we'll run through the commands.
We'll check for data movement first, data movement status and there we see the cloud is not enabled. But if it was running, we would say data movement stop moving on cloud clean status. Similar result, we don't have cloud on Clare clean stop. We'll check for replication stats. Obviously, we don't have a restorer, then we're checking the network jobs, nfs and cifs and we've got nothing running. Next step will be checking the disk space, the dis state and the reliability data. We run the DF command here. We're looking at post comp obviously, we have 100% available here, but all we need is 10%. So that's what you're looking for. As a reminder, the data domain is a passive storage device.
That means if you need to free up some space, you'll need to talk to your backup application and expire data. That way next up, we'll run dis show state we are looking for any failed reconstructing copy or absent state discs if you find any of those stop. Now in contact support, next step, we do diss show reliability dash data. We don't have a lot to show you here. But what you're looking for at the end of the output is somewhere where it will say X amount of drives are behaving normally. This will also output all the drives with all the reallocate sectors on there. If you see any above 2000 contact support, they may be eligible for a proactive replacement that we can do before the upgrade takes place. And finally, we'll move on to the pre upgrade reboot. First, we check to see the R PM files on the system with system package list.
We see ours there. So we'll move on with the grace will shut down system reboot hit. Yes, here and the system will go down. Now we're ready for step four, the upgrade, we'll be showing you how to do this on the cli and the gooey. It's important to note that this does take some time. Our DDVE here is very bare bones and it still took us about 30 minutes per upgrade. We've done a lot of work here to ensure that the upgrade goes smoothly. So please be patient and give it some time. It's very unlikely that the upgrade will get stuck. As we log in here. We'll check for alerts, alerts, show current no active alerts and then we'll take the file system status, file sys status up and running and then we'll check DF one more time to see if we got enough space and then we'll do system package list. We're going to do 7.7 0.5 0.20. So we'll copy that here. Mhm.
I'm gonna do system upgrade, precheck and then paste the file name here. Then as the precheck ends, we'll run the command again. Instead we'll do system upgrade, start with the same file name. There we go. The system will reboot during the upgrade process while it's down. We recommend to open up a ping and as soon as the system is back up, go ahead and log on and run system upgrade. Watch next. We'll show how to do the update on the gooey first. You just need to log in on the dashboard. You'll see that the file system is running right there and we have two alerts. We know that those are the security user and the male one.
So we'll just clear those up. We'll fix those after the upgrade next up. Go to system in maintenance. Pick the target code, do the upgrade precheck. And then once that finishes, you'll do the actual upgrade. As soon as you see the log in button here, the upgrade is technically finished. So we'll move on to the post check. We'll be doing this in the cli you know the drill by now, we'll do alert, show current, nothing unexpected there. File system status is up and running and capacity looks the same. Next, we'll move on to services. We're going to do a few examples here. But of course, you know, your environment better than we do. So you'll need to check them on your own. But we did NFS status here, SIF status and VTL. And with that, we have completed the DD OS upgrade.
We hope you found this video helpful and wish you the best of luck on your upgrade. Take care.
