status code 213 and status code 2

[franck_backup]

Hi all,

I am using netbackup server 6.0MP4 on a redhat 3 server.

We had new tape libraries last week.

With these new libraries we decided to do an online hot catalog backup instead of the offline one.

I launched the wizard create a policy named catalog that will launch a full backup of the catalog each week and I added tapes inside the CatalogBackup volumes.

I checked policy's attributes: storage unit and volume pool are right.

Normal backups are working very well.

When the catalog policy is launched there are 2 jobs running.

One exit with a status code 213 (No storage units available for use).

The other one with a status code 2 (none of the requested files were backed up).

I have read the troubleshooting guide.

Some help will be really appreciated.

Thanks

[Amit_Karia]

The NetBackup (tm) scheduler process (bpsched) did not find any of its storage units available for use. Either all storage units are unavailable (DOWN) or all storage units are configured for On demand only and the policy and schedule does not require a specific storage unit.

[franck_backup]

Thanks for your answer :)

Storage units are up and not configured for On demand Only. Normal backups use the two storage units defined on my server without any problems.

I really don't understand :(

In the job details there is a file list : /usr/openv/db/staging/EMM_DATA.db. This file doesn't exist on my server.

I don't know if it's related.

Thanks

[quebek]

Hello
do You have enough free space to stage DB to /usr/openv/db/staging directory??

The mentioned file by You is created by this policy, DB is dumped to the staging dir and from there is picked up to tape.

[franck_backup]

Hi quebek,

I don't know if it's enough but I have 1.4 G free.

How can I check if it's enough ?

Thanks

[quebek]

It is only one file system like /usr/openv ?
If so try to run this
du - s /usr/openv/netbackup/db
du -s /usr/openv/volmgr/database
du -s /usr/openv/var

If sum of all these three is bigger then your 1,4 GB than You do have not enough space.

[franck_backup]

Sorry I told you something wrong I have 35G available. (/usr/openv is a link to /work/openv - /work is a 52G partition-)

du -hs /usr/openv/volmgr/database
4.0K /usr/openv/volmgr/database

du -hs /usr/openv/netbackup/db
12G /usr/openv/netbackup/db

du -hs /usr/openv/var
640K /usr/openv/var

So it's not a problem of disk space :(

[quebek]

tpconfig -d
vmoprcmd
bpstulist  -U
bppllist CATALOG_POLICY _NAME -U
where CATALOG_POLICY_NAME is Your actual policy for backing up catalog
df -h

[franck_backup]

[root@backup.server logs]# /work/openv/volmgr/bin/tpconfig -d
Id DriveName Type Residence
Drive Path Status
****************************************************************************
3 IBM.ULTRIUM-TD4.000 hcart TLD(2) DRIVE=1
nrst5a (filer.server.com) UP
4 IBM.ULTRIUM-TD4.001 hcart TLD(3) DRIVE=1
nrst6a (filer.server.com) UP

Currently defined robotics are:
TLD(2) robotic path = mc3 (filer.server.com [SCSI b/t/l = 5/61/0] ),
TLD(3) robotic path = mc4 (filer.server.com [SCSI b/t/l = 1/61/0] ),

EMM Server = backup.server.com

[root@backup.server logs]# /work/openv/volmgr/bin/vmoprcmd

HOST STATUS
Host Name Version Host Status
========================================= ======= ===========
backup.server.com 600000 ACTIVE

PENDING REQUESTS


<NONE>

DRIVE STATUS

Drive Name Label Ready RecMID ExtMID Wr.Enbl. Type
Host DrivePath Status
=============================================================================
IBM.ULTRIUM-TD4.000 No No No hcart
backup.server.com nrst5a (filer.server.com TLD

IBM.ULTRIUM-TD4.001 No No No hcart
backup.server.com nrst6a (filer.server.com TLD

[root@backup.server logs]# /work/openv/netbackup/bin/admincmd/bpstulist -U

Label: backup.server-hcart-robot-tld-2-filer
Storage Unit Type: NDMP
Host Connection: backup.server.com
Number of Drives: 1
On Demand Only: no
Max MPX/drive: 1
Density: hcart - 1/2 Inch Cartridge
Robot Type/Number: TLD / 2
Max Fragment Size: 1048576 MB
NDMP attach host: filer.server.com

Label: backup.server-hcart-robot-tld-3-filer
Storage Unit Type: NDMP
Host Connection: backup.server.com
Number of Drives: 1
On Demand Only: no
Max MPX/drive: 1
Density: hcart - 1/2 Inch Cartridge
Robot Type/Number: TLD / 3
Max Fragment Size: 1048576 MB
NDMP attach host: filer.server.com

[root@backup.server logs]# /work/openv/netbackup/bin/admincmd/bppllist Catalog -U

------------------------------------------------------------

Policy Name: Catalog

Policy Type: NBU-Catalog
Active: yes
Effective date: 05/19/2009 17:04:55
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: 1
Disaster Recovery: 0
Collect BMR info: no
Residence: backup.server-hcart-robot-tld-2-filer
Volume Pool: CatalogBackup
Keyword: (none specified)

HW/OS/Client: Linux Linux backup.server.com

Include: CATALOG_DRIVEN_BACKUP

Schedule: Full
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (4 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: CatalogBackup
Calendar sched: Enabled
Friday, Week 1
Friday, Week 2
Friday, Week 3
Friday, Week 4
Friday, Week 5
Daily Windows:
Monday 08:00:00 --> Monday 24:00:00
Tuesday 00:00:00 --> Tuesday 24:00:00
Wednesday 00:00:00 --> Wednesday 24:00:00
Thursday 00:00:00 --> Thursday 24:00:00
Friday 20:00:00 --> Monday 08:00:00

Catalog Disaster Recovery Configuration:
Email Address: backup@server.com
Disk Path: /filer
User Name: root
Pass Word: xxxx
Critical policy: (none specified)

[root@backup.server logs]# df -h

Filesystem Size Used Avail Use% Mounted on
/dev/sda2 9.7G 7.8G 1.4G 86% /
/dev/sda1 289M 16M 259M 6% /boot
none 505M 0 505M 0% /dev/shm
/dev/sda3 7.7G 450M 6.9G 7% /tmp
/dev/sda6 52G 15G 35G 29% /work

[quebek]

You do not have a media manager storage unit?
>bpstulist -U

Label: some_label
Storage Unit Type: Media Manager

Maybe this is Your issue.
Try to create yet another storage Unit of Media Manager type.
I think NBU catalog backup cannot be directed to NDMP STU type.

[franck_backup]

I created a media manager storage unit called catalog.

Storage device is TLD(2)

Label: catalog
Storage Unit Type: Media Manager
Host Connection: _STU_NO_DEV_HOST_
Number of Drives: 1
On Demand Only: no
Max MPX/drive: 1
Density: hcart - 1/2 Inch Cartridge
Robot Type/Number: TLD / 2
Max Fragment Size: 1048576 M

When I launch the catalog backup manually I get a status code 800

NBU status: 800, EMM status: No drives are available

[Amit_Karia]

There is no media server associated with this storage unit , please select media server in storage unit

[quebek]

create a disk storage unit. Direct NBU catalog backup to it. If it will be successful You have to play with Your Media Manager STUs.

[franck_backup]

Tape librairies are attached to a filer and not to the netbackup server.

When I create a storage unit if I set its storage type to media manager the media server is automatically set to any available. I can't modify it.

[quebek]

Hey
Unfortunetaly I never played with NDMP devices. I am assuming You are doing the NDMP local backup.
Maybe You should share Your tape drives with NBU server. To achieve this You would need SSO Shared Storage Option.