Forum Discussion

dugga's avatar
dugga
Level 4
8 years ago

5220 Appliance - Uptime

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...
  • ejporter's avatar
    ejporter
    8 years ago

    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's avatar
    tunix2k
    8 years ago

    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

ejporter's avatar
ejporter
Level 4
8 years ago

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's avatar
    tunix2k
    Level 5
    8 years ago

    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

    • dugga's avatar
      dugga
      Level 4
      8 years ago

      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 .