cancel
Showing results for 
Search instead for 
Did you mean: 

5220 Appliance - Uptime

dugga
Level 4

I have 2 netbackup 5220 appliance with version 2.6.0.3

The uptime for my appliance is 395 days and 207 days.

How frequent do we need to reboot the appliance.

Which all services needs to be stopped while rebooting the appliance, 

Is there any KB article on how to execute the reboot?

I just could find the CLI : Support > Reboot I couldnt gather any other details in the document.

Will this have downtime?What all postchecks should I do post upgrade?

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

ejporter
Level 4

In theory you should never need to reboot them.   Linux is honestly very stable,  netbackup on the other hand may do with a reboot every so often.  Personally, I dont schedule reboots.   I usualy have to once a year for a patch or other reasons and that seems to work.

As for the process to reboot, not to difficult.

  • cancel running jobs if any.   (You can get a away without this, but its cleaner.)
  • Login to the CLISH
  • support
  • reboot     (Note a large system may take a while to come down)
  • If you want to monitor the boot get on the console via the IPMI.
  • The MDSP pools will take a little bit to come live after the boot, give them 15- 20 minutes depending on size.
  • Run a couple of test backups and make sure the complete.

 

 

View solution in original post

tunix2k
Level 5
Partner Accredited

llo,

 

have the same experiance like @ejporter no extra reboot needed.

Best practise and suggested by veritas is to reboot the appliance prior an upgrade. Reboot will take a lot of time. I personally stop Netbackup processes and reboot then. Linux Filesystems will be checked after a long uptime. You should monitor on console via IPMI.

ciao

tunix2k

View solution in original post

3 REPLIES 3

ejporter
Level 4

In theory you should never need to reboot them.   Linux is honestly very stable,  netbackup on the other hand may do with a reboot every so often.  Personally, I dont schedule reboots.   I usualy have to once a year for a patch or other reasons and that seems to work.

As for the process to reboot, not to difficult.

  • cancel running jobs if any.   (You can get a away without this, but its cleaner.)
  • Login to the CLISH
  • support
  • reboot     (Note a large system may take a while to come down)
  • If you want to monitor the boot get on the console via the IPMI.
  • The MDSP pools will take a little bit to come live after the boot, give them 15- 20 minutes depending on size.
  • Run a couple of test backups and make sure the complete.

 

 

tunix2k
Level 5
Partner Accredited

llo,

 

have the same experiance like @ejporter no extra reboot needed.

Best practise and suggested by veritas is to reboot the appliance prior an upgrade. Reboot will take a lot of time. I personally stop Netbackup processes and reboot then. Linux Filesystems will be checked after a long uptime. You should monitor on console via IPMI.

ciao

tunix2k

Thanks alot for the response  ^_^ : ejporter and tunix2k

I'm planning for an upgrade in the coming weeks , so I would better do this reboot a day before that .