Forum Discussion

nohup's avatar
nohup
Level 3
16 years ago
Solved

Recommendations for NBU file system layout

Howdy all,

I'm getting ready to install NBU 6.5 on Linux (RHEL) and want to make sure I size and breakout the file systems correctly.  I'm looking for some advice on how folks are laying NBU Master Server out on disk.

Currently I'm considering leaving everything aside from the following directories in /usr/openv and breaking off the following subdirectories into their own file systems,  :

/usr/openv/netbackup
/usr/openv/volmgr
/usr/openv/db

I would also appreciate some direction on sizing these file systems, as well as advice on breaking off any other directories into their own file systems.   I have a fairly small environment (A couple of hundred servers), with 1 Master and 3 Media Servers.  We will be backing everything up to a PureDisk storage pool.  I have looked through the boards and did not see this covered, but if it already is in another post, please feel free to link me to it.

Thanks in advance for your input.

7.1.x and Earlier
Backup and Recovery
Configuring
Installing
NetBackup
  • Stumpr2's avatar
    Stumpr2
    16 years ago
    I would make just these four on their own filesystem and link to them

    /usr/openv/netbackup/db/images
    /usr/openv/netbackup/logs
    /usr/openv/logs
    /usr/openv/volmgr/debug

    DOCUMENTATION: Best Practice recommendations for enabling and gathering Veritas NetBackup (tm) 6.0 logging
    http://support.veritas.com/docs/282865

  • Stumpr2's avatar
    Stumpr2
    Level 6
    16 years ago
    I would make just these four on their own filesystem and link to them

    /usr/openv/netbackup/db/images
    /usr/openv/netbackup/logs
    /usr/openv/logs
    /usr/openv/volmgr/debug

    DOCUMENTATION: Best Practice recommendations for enabling and gathering Veritas NetBackup (tm) 6.0 logging
    http://support.veritas.com/docs/282865

  • Nicolai's avatar
    Nicolai
    Moderator
    16 years ago
    By creating more file system you reduces the damage you're Netbackup installation takes if the file system is filled.

    Creating one large files system *MAY* corrupt the netbackup database, if let's say you by mistake configured log level = 99 and filled the entire file system. If you had configured /usr/openv/netbackup/logs ( or /usr/openv/logs/ ) as a separate file system you wold have protected backup operation and avoided a Netbackup database corruption.
  • Stumpr2's avatar
    Stumpr2
    Level 6
    16 years ago
    Separate from /usr/openv:

    You can put ALL the logs on one filesystem.
    The image db on its own.
    But please do not put both the logs and the images on the same filesystem.
  • nohup's avatar
    nohup
    Level 3
    16 years ago
    Thanks for the input, just curious on why you would seperate the file system at

    /usr/openv/netbackup/db/images

    and not just

    /usr/openv/netbackup/db

    ?

    Also, any recommendations on sizing?

    Thanks again.

  • Stumpr2's avatar
    Stumpr2
    Level 6
    16 years ago
    I do it for simplicity.
    I use rsync to replicate the images directory on a standby DR server.
  • jnardello's avatar
    jnardello
    Moderator
    16 years ago
    Like Bob says, separate things out. I'd go with two filesystems /usr/openv and /usr/openv/logs . Softlink /usr/openv/volmgr/debug and /usr/openv/netbackup/logs back to /usr/openv/logs and get all your logs to the same place. That leaves you with just the binaries sharing space with the actual catalog.

    I'd also recommend that whatever filesystem type you create, that it be easily expandable later. =) 

    You can check out the Tuning Guide for the calculations on how large catalogs will be based on what you back up. Put that together with the retention for your various backups and you should have a decent number for what your catalog should run at. Then ask for double that. =) 

  • nohup's avatar
    nohup
    Level 3
    16 years ago
    Do you folks have any similar recommendations for the Media Servers?

    Thanks again.
  • jnardello's avatar
    jnardello
    Moderator
    16 years ago
    I'd stick with the same FS layouts on both Masters and Medias. Easier if you standardize to support it later, and the Media Servers are certainly capable of cranking out some large log files of their own when verbose and under load. Fill up their filesystem and you'll have problems there too.