GENERAL ERROR: Jobs sit in queue and never start when using newly added storage unit Page 1 of 3

Document ID: 277123

http://support.veritas.com/docs/277123
E-Mail this document to a colleague

GENERAL ERROR: Jobs sit in queue and never start when using newly added
storage unit

Exact Error Message

<8> req_stunit_available: didn't find valid storage unit
<STUname> in stunit group, or storage unit list
<16> log_in_errorDB: didn't find valid storage unit
<STUname> in stunit group, or storage unit list

Details:
Overview:
Adding a new storage unit will not make it immediately available for backups. After
creating a new storage unit, the VERITAS NetBackup (tm) processes need to be
restarted. Any attempt to back up or restore to the new storage unit will cause the job to
queue and never run.

Troubleshooting:
Verify the new storage unit <STUname> appears in the configuration using the
bpstulist command:

# cd /usr/openv/netbackup/bin/admincmd
# ./bpstulist -label <STUname> -U
Label: server-dlt2
Storage Unit Type: Media Manager
Host Connection: server
Number of Drives: 1
On Demand Only: no
Max MPX/drive: 2
Density: dlt2 - DLT Cartridge 2
Robot Type: (not robotic)
Max Fragment Size: 1048576 MB

Master Server Log Files:

The /usr/openv/netbackup/logs/bpsched/log.<date> on the master server will show the
following error when trying to use the new storage unit:

<8> req_stunit_available: didn't find valid storage unit

<STUname> in stunit group, or storage unit list

file://H:\study\netbackup\Upload_site_done\done\New Folder\GENERAL ERROR Jobs sit in queue and nev... 7/6/2010

GENERAL ERROR: Jobs sit in queue and never start when using newly added storage unit Page 2 of 3

<16> log_in_errorDB: didn't find valid storage unit

<STUname> in stunit group, or storage unit list

Resolution:
The bpschedreq command can be used to read the storage unit configuration. This
may offer a way to allow NetBackup to recognize the storage unit without having to restart
NetBackup:

# /usr/openv/netbackup/bin/admincmd
# ./bpschedreq -read_stunits

The command will return no output. This command will cause the main bpsched process
to read the list of storage units. If successful, the queued jobs should start going active. If
the jobs remain queued, the only other option is to cancel the jobs and restart the
NetBackup services.

The NetBackup daemons should be restarted after adding a new storage unit. This is
needed to get the new storage unit to be recognized by the NetBackup daemons.

When no backups or restores are running, issue the command:

# /usr/openv/netbackup/bin/goodies/netbackup stop
# /usr/openv/netbackup/bin/goodies/netbackup start

Then retry the backup operation. The new storage unit will now be available for use.

Note: The bpschedreq -read_stunits command may not have an effect on all
environments, depending upon size and configuration. Additionally, for this command to
be effective, the bpsched process must be running. To be completely sure that any
storage unit changes have taken effect, restart NetBackup services/daemons on the
master server when there is no job activity.

Products Applied:
NetBackup DataCenter 4.5
NetBackup Enterprise Server 5.0, 5.1

Last Updated: February 27 2006 11:57 PM

GMT
Expires on: 365 days from publish date
Subscribe to receive critical updates

file://H:\study\netbackup\Upload_site_done\done\New Folder\GENERAL ERROR Jobs sit in queue and nev... 7/6/2010

GENERAL ERROR: Jobs sit in queue and never start when using newly added storage unit Page 3 of 3

Application: Configuration, Device Management

NetBackup Enterprise Server
Application: Configuration, Device Management
Solaris
Application: Informational

Languages:
English (US)

Operating Systems:
Solaris
8.0

Symantec World Headquarters:

20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com/,
Tech Support Web: http://entsupport.symantec.com/,
E-Mail Support:
http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com/ or
ftp://ftp.entsupport.symantec.com/

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY
OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC
SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT
APPLY.

file://H:\study\netbackup\Upload_site_done\done\New Folder\GENERAL ERROR Jobs sit in queue and nev... 7/6/2010