Naming Storage Units and Groups in NetBackup

From World History Wiki
Jump to: navigation, search
World History Wiki is Brought to you by:
S.J.'s Adventures


These documents are for entertainment purposes only. Use at your own risk. This site is in no way affiliated with Veritas or NetBackup, and any trademarks are those of their respective companies.

If you need assistance with anything NetBackup and/or Disaster Recovery related, You can find me on linkedIn.

Standardizing the naming of Storage Units, Storage Groups, and Storage Lifecycle Policies will help insure consistency and clarity in the configuration of storage targets used within your NetBackup environment. When looking at the names for storage components within NetBackup, it will be clear what devices and methodologies are being used for a particular backup.

For more details on configuring these components of NetBackup, see How to install and configure NetBackup 7.6 and Media Server De-Duplication Pools#Create Storage Unit.

Media Server Deduplication Pools

Storage Servers

Storage servers are generally named after the server its self. Make sure that if you are using a backup interface, to use that interfaces, and force NetBackup to use that interface when configuring the MSDP.

Disk Pools

Disk pools should be named with two parts. Something to not which server it's on, and then the name of the disk volume; which is usually PureDiskVolume. Separating them with a dash (-) is probably best.

Server Name Disk volume Name
server PureDiskVolume

Storage Units

NOTE: Some of these naming conventions are not automatically designated by wizards and must be customized.

Naming

NetBackup's Default Storage Unit naming is made up of a server name, media type, media-mechanism, mechanism type and number, and a location. Staying consistent with this naming convention is a good way to insure consistency across the board. Although you can have multiple media servers involved within a single storage unit, it's usually best to limit each storage unit to a single media server, and instead use Storage Unit Groups.

Using all lowercase, along with a dash (-) to separate fields, can help differentiate them from STU groups, Policies and SLPs.

Server Name Media Type Mechanism Mechanism Type Robot, Directory, or Location
server# hcart, hcart2, dlt1, etc. robot, vtl, ndmp, etc. tld, acsls, etc. 0, 1, 2, 3, etc.
server# disk dsu, lsu, advnc, medsrv, ost, etc. dsu_name, lsu_name, dedup, etc. de-dup_appliance_name, directory_name, nas_share_name, etc.
server# cloud ost lsu_name storage_server_name

Configuration

Tape Devices themselves are usually given default NetBackup names; which are typical sufficient for identification. Other devices, such as Storage Servers, LSU's, drive names, etc, will need to be given their own specific naming conventions as well.

No one Storage Unit should be allowed to use all the resources available within a single robot or Storage Server, unless it is dedicated to a particular media server or all Media servers are configured to use the Storage Unit.

Storage Unit Groups

Storage Units Groups should be used everywhere possible to streamline usage of storage targets, provide for fail over, and prevent having to edit policies and SLPs.

They should be named to describe what they are meant to be used for, but generic enough to not require creating new one's frequently.

Using ALL CAPS along with a dash (-) as separator, will help differentiate them from from STUs, Policies and SLPs.

Server(s) Primary Media type & Destination Secondary Media type & Destination Tertiary Media type & Destination (optional)
ALL OST_APPLIANCE1 OST_APPLIANCE2 TAPE_TLD0
SERVER# TAPE_TLD1 TAPE_TLD2 DSU_DRIVE_NAME
SERVER#_SERVER#_SERVER# DISK_MSDP DISK_MSDP DISK_MSDP

Storage LifeCycle Policies

Storage Lifecycle Policy names should be very specific and reflect not only the type of storage they go to, including the server(s) as applicable, but also the retention (which can be implied by a "schedule" name), and where subsequent copies of the data are made.

For certain features to work with SLP's, the 1st or primary destination for the backup will determine how and were subsequent copies can be created. Thus it is an important key feature of the SLP, and should be indicated as such in the name. It also means a good understand of the environment and the capabilities of each piece of equipment is also important to understanding the naming convention and function of each SLP.

When configuring SLPs, use Storage Unite Groups to reduce the need for editing it directly. Editing an SLP will change its version number, which can create undesirable results. It's usually best to instead create a new SLP, rather then doing any significant editing to an existing SLP. Keeping the naming convention specific, will help enforce this rule of creating new instead of editing existing.

Using ALL CAPS, and separating each field with an underscores (_) can help differentiate them from from STUs, STU groups, and Policies.

Server(s) Primary destination Frequency/Schedule
(& retention if not implied).
Secondary destination Tertiary destination
ALL OST-APPLIANCE1 HOURLY-2WEEKS OST-APPLIANCE2-1WEEK TLD0-1MONTH
SERVER# DSU-DRIVE DAILY-1WEEK TLD0-1MONTH
SERVER# OST-APPLIANCE1-2MONTH MONTHLY-SYNTH OST-APPLIANCE2-2MONTH TLD0-7YEARS

For more details on SLP's see Understanding NetBackup Storage Lifecycle Policies



Back to NetBackup