Forum Discussion

Level 4

10 years ago

nbdecommission - "partial" decommissions, skipping OST disk

I am migrating ~ 300 to 400 media server in 14 NB domains from tape to Data Domain.

When I am done, I will be required to decommission "most" of the tape libraries (maybe 14 of 20) and tape drives from the media servers.

The remaining images will need to be accessible to media servers designated for legacy restore consolidation.

None of the media servers are being retired. All of them will continue to write to OST Disk Pools.

Is there a way to run the nbdecommission wizard for a partial decommission, skipping OST devices? If so, it would be far simpler than writing a manual process.

7.5

Backup and Recovery

Managing Backup Devices

NetBackup

Uninstall

UNIX

RiaanBadenhorst
10 years ago
Hi,

Understood. What you can do is use the 'nbdecommision -oldserver SERVERNAME -list_ref' command. It would show you where there are references to the media server in question so you can action the specific cleanup.

It might help a bit.

See output below.

[root@ora11g-01 logs]# nbdecommission -oldserver app-01 -list_ref
Server app-01 is a member of the following media sharing groups:
    UNRESTRICTED_SHARING_GROUP

Media referencing server app-01

Following media are owned by app-01:
    MEDIA:1018L4

Media generation rules on host app-01:

Drive paths found on server app-01
Following drive paths are found on server app-01:
    IBM.ULT3580-TD5.000    -    /dev/nst1    TLD(0)    0x00000000
    IBM.ULT3580-TD5.001    -    /dev/nst0    TLD(0)    0x00000000

Robots attached to app-01
Following robots are connected to app-01:
    TLD(0)

Processing tape storage units

Storage unit app-01-hcart2-robot-tld-0: host app-01, robot TLD(0)
Storage unit app-01-hcart2-robot-tld-0 is a member of storage unit group tape_stus_app-01

Processing basic disk storage units

Processing SnapVault/NearStore disk storage units

Processing advanced disks
app-01 is not a AdvancedDisk storage server

Processing shared disks
app-01 is not a SharedDisk storage server

Processing OST devices
List of storage servers accessible to app-01:

Storage Server: app-01
Server Type: PureDisk (9)
Disk Pool: dp_disk_app-01
Media Server: app-01
Media ID: @aaaab (PureDiskVolume)
Following images reside on media @aaaab:
IMAGE app-01 10 app-01_1417662952 fs_daily 0 Daily 0 4 2529 1423019752 0 0
FRAG 1 1 90816 0 0 0 0 @aaaab app-01 262144 0 0 -1 1024 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1423019752 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443183 oracle_daily 4 Daily 0 4 1 1422799983 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799983 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443157 oracle_daily 4 Daily 0 4 1 1422799957 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799957 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443124 oracle_daily 4 Daily 0 4 1 1422799924 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799924 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443048 oracle_daily 4 Daily 0 4 5 1422799848 0 0
FRAG 1 1 1438880 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799848 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711215 oracle_daily 4 Daily 0 4 1 1421068015 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421068015 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711178 oracle_daily 4 Daily 0 4 1 1421067978 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421067978 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711146 oracle_daily 4 Daily 0 4 1 1421067946 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421067946 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711015 oracle_daily 4 Daily 0 4 5 1421067815 0 0
FRAG 1 1 1423520 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421067815 0 4 6 *NULL*
Disk pool dp_disk_app-01 (PureDisk) is referenced by the following storage units:
    stu_disk_app-01

Storage unit stu_disk_app-01: host app-01
Storage unit stu_disk_app-01 is referenced by policy flashbackup_daily
Storage unit stu_disk_app-01 is referenced by policy fs_daily
Storage unit stu_disk_app-01 is referenced by policy oracle_daily

Processing storage life cycles

Process backup policies

Processing Fibre Transports
app-01 is not a Fibre Transport server

Processing bp.conf file/Windows registry on the NetBackup media servers

Processing bp.conf file/Windows registry on the NetBackup master server
Processing config file on ora11g-01
Configuration file on the master server ora11g-01:
SERVER = app-01

RiaanBadenhorst
Level 6
10 years ago
Hi

nbdecommission is not the right tool to use here. All you need to do is expire the images on tape, and then delete all drives and robots.

How are you managing the duplications? I'm sure you've got most of the logic in that process already.
verbose5
Level 4
10 years ago
The images will be left on their current tape media until their scheduled expiration dates. There is no plan to duplicate or expire them manually.

The large majority of images will expire in few months. A small fraction of leftover images will expire in a year or more (or never).

The leftover images will need to be re-assigned to one media server in each domain that will retain a library with the required types of tape drives.

If nbdecommission is not the right tool, then I assume the process will be a series of "bpimage -movedb" commands to assign them to the correct media server, followed by a series of "tpconfig -delete" commands to remove the drives and libraries from the other media servers.

I had hoped the nbdecommission command could be used here for the automatically inspecting policies and storage units for cofirmation that each media server was no longer in use by any policy for tape backups. It is a large environment with many policies, and human error can lead to code 219's and other errors after tape drive configurations are removed.
RiaanBadenhorst
Level 6
10 years ago
Hi,

Understood. What you can do is use the 'nbdecommision -oldserver SERVERNAME -list_ref' command. It would show you where there are references to the media server in question so you can action the specific cleanup.

It might help a bit.

See output below.

[root@ora11g-01 logs]# nbdecommission -oldserver app-01 -list_ref
Server app-01 is a member of the following media sharing groups:
    UNRESTRICTED_SHARING_GROUP

Media referencing server app-01

Following media are owned by app-01:
    MEDIA:1018L4

Media generation rules on host app-01:

Drive paths found on server app-01
Following drive paths are found on server app-01:
    IBM.ULT3580-TD5.000    -    /dev/nst1    TLD(0)    0x00000000
    IBM.ULT3580-TD5.001    -    /dev/nst0    TLD(0)    0x00000000

Robots attached to app-01
Following robots are connected to app-01:
    TLD(0)

Processing tape storage units

Storage unit app-01-hcart2-robot-tld-0: host app-01, robot TLD(0)
Storage unit app-01-hcart2-robot-tld-0 is a member of storage unit group tape_stus_app-01

Processing basic disk storage units

Processing SnapVault/NearStore disk storage units

Processing advanced disks
app-01 is not a AdvancedDisk storage server

Processing shared disks
app-01 is not a SharedDisk storage server

Processing OST devices
List of storage servers accessible to app-01:

Storage Server: app-01
Server Type: PureDisk (9)
Disk Pool: dp_disk_app-01
Media Server: app-01
Media ID: @aaaab (PureDiskVolume)
Following images reside on media @aaaab:
IMAGE app-01 10 app-01_1417662952 fs_daily 0 Daily 0 4 2529 1423019752 0 0
FRAG 1 1 90816 0 0 0 0 @aaaab app-01 262144 0 0 -1 1024 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1423019752 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443183 oracle_daily 4 Daily 0 4 1 1422799983 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799983 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443157 oracle_daily 4 Daily 0 4 1 1422799957 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799957 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443124 oracle_daily 4 Daily 0 4 1 1422799924 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799924 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1417443048 oracle_daily 4 Daily 0 4 5 1422799848 0 0
FRAG 1 1 1438880 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1422799848 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711215 oracle_daily 4 Daily 0 4 1 1421068015 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421068015 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711178 oracle_daily 4 Daily 0 4 1 1421067978 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421067978 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711146 oracle_daily 4 Daily 0 4 1 1421067946 0 0
FRAG 1 1 9760 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421067946 0 4 6 *NULL*
IMAGE ora11g-01 10 ora11g-01_1415711015 oracle_daily 4 Daily 0 4 5 1421067815 0 0
FRAG 1 1 1423520 0 0 0 0 @aaaab app-01 262144 0 0 -1 0 1;PureDisk;app-01;dp_disk_app-01;PureDiskVolume;0 1421067815 0 4 6 *NULL*
Disk pool dp_disk_app-01 (PureDisk) is referenced by the following storage units:
    stu_disk_app-01

Storage unit stu_disk_app-01: host app-01
Storage unit stu_disk_app-01 is referenced by policy flashbackup_daily
Storage unit stu_disk_app-01 is referenced by policy fs_daily
Storage unit stu_disk_app-01 is referenced by policy oracle_daily

Processing storage life cycles

Process backup policies

Processing Fibre Transports
app-01 is not a Fibre Transport server

Processing bp.conf file/Windows registry on the NetBackup media servers

Processing bp.conf file/Windows registry on the NetBackup master server
Processing config file on ora11g-01
Configuration file on the master server ora11g-01:
SERVER = app-01
verbose5
Level 4
10 years ago
The -list_ref option looks like exactly what I needed. Thank you for the guidance.
RiaanBadenhorst
Level 6
10 years ago

Pleasure

Forum Discussion

nbdecommission - "partial" decommissions, skipping OST disk

Related Content

Decommission Enterprise vault server

Analyze "partially successful" restore information

"backup partially successful" with status code 1

Decommissioning Enterprise Vault

nbdecommission issue

Recent Discussions

Netbackup KMS

Getting ms-windows assets via api

installation of 8.1.2 is failing in windows 2016 standard server.

Inquiry regarding using Netbackup appliances across domain

BMR: Could not read saved configuration file=X:\bmrcli.xml