If your backup server is on the same network as the DAG servers, make sure that you can resolve the DAG server’s MAC address.

You can check it by “arp -a” from a command prompt.

1.0  Gathering initial NBCC information
1.1  Obtaining initial NetBackup configuration information

NBCC is being run on NetBackup master server
backupserver
NBCC version 7.1 Gather mode = full

NBCC command line = C:\Program Files\Veritas\NetBackup\bin\support\NBCC.exe

OS name  = MSWin32

OS version = Microsoft Windows [Version 5.2.3790]

NetBackup Install path = C:\Program Files\Veritas\

> dir output\nbcc\backupserver_NBCC_20110330_223514 2>&1

Parsed output for “bytes free”

4 Dir(s)  567.705.044.480 bytes free

The filesystem for the
output\nbcc\backupserver_NBCC_20110330_223514
directory either doesn’t have 1024000 KB of space available.
Evaluate the space available and the potential space requirements
needed by NBCC to perform the consistency checks and look at the
potential usage of the -kbfree command line switch.
Report complete, closing the
.\output\nbcc\backupserver_NBCC_20110330_223514\nbcc-info.txt
output file.

The problem is most probably your regional settings. NBCC fails while parsing the “bytes free” as it contains dots (“.”) instead of commas (“,”).

You should change it according to the following Technote:

GENERAL ERROR: “NBCC encountered an error condition of some type!” and “directory doesn’t have 1024000 KB of space available” when running the NBCC tool on a server with non English language setting.

Or if you’re using NetBackup 7.1, the following technote can be helpful to you:

GENERAL ERROR: NBCC fails with the following error message “directory either doesn’t have 1024000 KB of space available”

(master_server)/var/adm>bpexpdate -d 0 -m LT1007
Media LT1007 is due to expire at 03/20/2011 19:48:19
Are you sure that the data on this media is not critical to
your business, and you are sure you want to delete LT1007 y/n (n)? y
requested media id is not assigned to this host in the EMM database
(master_server)/var/adm>

Check your Media list and ensure that the media that you’re trying to expire is not assigned to another host. If it’s assigned to another media server, you can expire your media by adding the “-host media_server” switch to the command:

(master_server)/var/adm>bpexpdate -d 0 -m LT1007 -host other_media_server
Media LT1007 is due to expire at 03/20/2011 19:48:19
Are you sure that the data on this media is not critical to
your business, and you are sure you want to delete LT1007 y/n (n)? y
(master_server)/var/adm>

It’s hard to know without testing but, it seems like, backing up an Oracle database with 10 channels, which is running with 24 cpu’s, through a 16 cpu’ed media server is a bit too much… I think 6 is a good number, but I intend to try again at a later time with 8 channels.

Eventually, 8 channels means around 200Mbytes/sec, while 6 channels means around 150Mbytes/sec, which is a significant difference of 50Mbytes/sec… :)

USAGE:
nbftconfig [-addclient] [-deleteclient] [-changeclient] [-rescanclient]
[-listclients] [-addserver] [-deleteserver] [-changeserver]
[-listservers] [-listtargets] [-listactive] [-setconfig]
[-getconfig] [-verbose] [-help]

For detailed usage of each operation, use:
nbftconfig -help <operation>

[root@mediaserver admincmd]# ./nbftconfig -help -addclient

USAGE:
nbftconfig -[ac]addclient -C <client_name> [-M <master_server>]
[-ftpref <preferred | always | never>
-ftwait <minutes> -ftrwait <minutes>]
Note:
1. If -M option is not used, local machine’s master server is assumed
2. If preferences are not provided, master server defaults are used
3. -ftwait and -ftrwait are required only if -ftpref is set to “preferred”

[root@mediaserver admincmd]# ./nbftconfig -help -deleteclient

USAGE:
nbftconfig -[dc]deleteclient <client_name>

1. Licences are still installed according to your default hostname, get_license_key script should be corrected if you want to manage with your installation hostname.

Change the following line(line 61):
PING_CMD=”ping -c 1 \${HOST} 2>/dev/null | grep \”1 packets received\”"
to
PING_CMD=”ping -c 1 \${HOST} 2>/dev/null | grep \”1 received\”"

2. /usr/openv/volmgr/vm.conf is not created and while you are trying to configure your devices, it is created according to your default hostname. My suggestion is to create manually and insert your hostname, before doing any device configuration from the master.

If you don’t, you are very likely to see the following message on your shared tape drives’ Properties:

No shared storage option license installed

I’m really not very sure if vm.conf is the reason, but i was able to solve this problem by manually creating it…

3. You are very likely to receive an error message at the end on the device configuration wizard:

“Restarting the Media Manager device daemon” will fail, and you will not be elligible to create your storage unit.

Don’t loose too much time, open a case to Enterprise Support via phone or MySupport

In the meantime you can try these:

Check if you still have some pending activies on the system:

(nbu)/usr/openv/netbackup/logs/admin>/usr/openv/volmgr/bin/vmoprcmd

HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
nbu                                    700000    ACTIVE
nbu_dmz                                700000    ACTIVE

PENDING REQUESTS

<NONE>

DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM3-SCSI-VTL.000  No      No                     No        hcart3
nbu                    /dev/rmt/4cbn                        TLD

HP.ULTRIUM3-SCSI-VTL.001  No      No                     No        hcart3
nbu                    /dev/rmt/5cbn                        TLD

HP.ULTRIUM3-SCSI-VTL.002  No      No                     No        hcart3
nbu                    /dev/rmt/6cbn                        TLD

HP.ULTRIUM3-SCSI-VTL.003  No      No                     No        hcart3
nbu                    /dev/rmt/7cbn                        TLD

HP.ULTRIUM3-SCSI.000     No      No                     No        hcart3
nbu                    /dev/rmt/8cbn                        DOWN-TLD
nbu                    /dev/rmt/1cbn                        TLD
nbu_dmz                /dev/nst1                            TLD
nbu_dmz                /dev/nst5                            SCAN-TLD

HP.ULTRIUM3-SCSI.001     No      No                     No        hcart3
nbu                    /dev/rmt/0cbn                        TLD
nbu                    /dev/rmt/11cbn                       TLD
nbu_dmz                /dev/nst3                            TLD
nbu_dmz                /dev/nst7                            SCAN-TLD

HP.ULTRIUM3-SCSI.002     Yes     Yes    000032          Yes       hcart3
nbu                    /dev/rmt/3cbn                        TLD
nbu                    /dev/rmt/10cbn                       TLD
nbu_dmz                /dev/nst0                            TLD
nbu_dmz                /dev/nst4                            SCAN-TLD

HP.ULTRIUM3-SCSI.003     No      No                     No        hcart3
nbu                    /dev/rmt/2cbn                        TLD
nbu                    /dev/rmt/9cbn                        TLD
nbu_dmz                /dev/nst2                            TLD
nbu_dmz                /dev/nst6                            SCAN-TLD

If you see pending requests, you can try rebooting your servers and see if that works…

Also check if you have and requests or allocations on nbrb

(nbu)/usr/openv/netbackup/logs/admin>/usr/openv/netbackup/bin/admincmd/nbrbutil -dump

Allocation Requests
(AllocationRequestSeq )

Allocations
(AllocationSeq )

MDS allocations in EMM:

if you don’t have any active jobs running, you can try to reset all of them.

(nbu)/usr/openv/netbackup/logs/admin>/usr/openv/netbackup/bin/admincmd/nbrbutil -resetAll

One more thing, it may be irrelevant but, i corrected my locale settings inside /etc/default/init file and rebooted.

These maybe helpful to you, but not guaranteed. Better contact Technical Support immediately…

root@veritas # vmoprcmd -devmon

HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
veritas                                    700000    ACTIVE
veritas_2                                700000    ACTIVE

PENDING REQUESTS

<NONE>

DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM3-SCSI-VTL.000  Yes     Yes    1E000Y  1E000Y  Yes       hcart3
veritas                    /dev/rmt/4cbn                        ACTIVE

HP.ULTRIUM3-SCSI-VTL.001  Yes     Yes    1E000P  1E000P  Yes       hcart3
veritas                    /dev/rmt/5cbn                        ACTIVE

HP.ULTRIUM3-SCSI-VTL.002  Yes     Yes    1E000W  1E000W  Yes       hcart3
veritas                    /dev/rmt/6cbn                        ACTIVE

HP.ULTRIUM3-SCSI-VTL.003  Yes     Yes    1E000L  1E000L  Yes       hcart3
veritas                    /dev/rmt/7cbn                        ACTIVE

HP.ULTRIUM3-SCSI.000     Yes     Yes    000015  000015  Yes       hcart3
veritas                    /dev/rmt/8cbn                        TLD
veritas                    /dev/rmt/0cbn                        ACTIVE
veritas_2                /dev/nst1                            TLD
veritas_2                /dev/nst5                            SCAN-TLD

HP.ULTRIUM3-SCSI.001     No      No                     No        hcart3
veritas                    /dev/rmt/1cbn                        TLD
veritas                    /dev/rmt/9cbn                        TLD
veritas_2                /dev/nst3                            TLD
veritas_2                /dev/nst7                            SCAN-TLD

HP.ULTRIUM3-SCSI.002     No      No                     No        hcart3
veritas                    /dev/rmt/2cbn                        TLD
veritas                    /dev/rmt/10cbn                       TLD
veritas_2                /dev/nst4                            DOWN-TLD
veritas_2                /dev/nst0                            SCAN-TLD

HP.ULTRIUM3-SCSI.003     No      No                     No        hcart3
veritas                    /dev/rmt/3cbn                        TLD
veritas                    /dev/rmt/11cbn                       TLD
veritas_2                /dev/nst2                            TLD
veritas_2                /dev/nst6                            SCAN-TLD

Reference: http://seer.entsupport.symantec.com/docs/265914.htm

16.11.2009 17:13:47 – expected media FSD300; found media D300L4
16.11.2009 17:13:47 – end Label; elapsed time: 00:03:43
media manager found wrong tape in drive(93)

From GUI, after clicking right-clicking on your tape, ensure that “Verify media label before performing operation” checkbox is cleared.

Then retry your labeling operaiton.

incorrect media found in drive index 0, expected FSD300, found D300L4, FREEZING FSD300

Reference : http://seer.entsupport.symantec.com/docs/276993.htm

Try to re-label your tapes, using the GUI or the bplabel command.

ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 2

the cause is possibly your are trying to restore your database to an NFS mount point which is not mounted correctly.

The following is for Solaris 10:

Change your /etc/vfstab entry

From:

Nfs_Host:/nfs/oracle – /oradata   nfs   –   yes   -

To:

Nfs_Host:/nfs/oracle – /oradata   nfs   –   yes   hard, bg,proto=tcp, vers=3, suid, rsize=32768, wsize=32768, intr,noac

Then, unmount and re-mount your volumes through /etc/vfstab

“Missing Path” or “Unused element address”

There can be many reasons causing this error, but you can try the folllowing:

Update your drivers from the following url, then delete and re-configure tape drives on Netbackup.

http://seer.entsupport.symantec.com/docs/287850.htm

http://seer.entsupport.symantec.com/docs/276755.htm

It fails with an error like : “dependant services fail to start”

Try to reinstall Service Pack 2 on to your client, and after the reboot the service should come up without problems.

ORA-28001: the password has expired

As stated, your rman user’s password has expired. You should either change the password, and of course change password in every RMAN script as well.

Or you can do something like this:

1. Create a new profile which has no password expiry

2. Alter your rman user to the new profile

sqlplus /as sysdba

CREATE PROFILE rman_PROFILE

LIMIT

PASSWORD_LIFE_TIME UNLIMITED;

alter user rman PROFILE rman_PROFILE;

Now, you can retry your backup.

Reference : http://www.orafaq.com/forum/t/82806/0/

server name not found in the NetBackup configuration

1. You were trying to expire a media from emm database:

bpexpdate -m media_id -d 0

Solution: Try to add -host media_server_hostname to end of the command

bpexpdate -m media_id -d 0 -host media_server

Please add your knowledge about this error…

Thanks.

05/31/2009 11:24:48 – Warning bpbrm (pid=14316) from client exchangeServer: WRN – Exchange database recovery may have failed. Please check the event log for further details.
05/31/2009 11:27:02 – end reading; read time: 0:03:36
05/31/2009 11:27:03 – Warning bpbrm (pid=14316) from client exchangeServer: WRN – Exchange database recovery may have failed. Please check the event log for further details.
05/31/2009 11:27:04 – Error bpbrm (pid=14316) client restore EXIT STATUS 185: tar did not find all the files to be restored
05/31/2009 11:27:04 – restored from image exchange2_1243565471; restore time: 0:04:24
05/31/2009 11:27:15 – end Restore; elapsed time 0:21:45
the requested operation was partially successful (1)

After backing up your files, and while dismounted, remove every file from the database and log directories and re-try your backup again.

For example: You have a database named First Storage Group. Database files reside in d:\db\First Storage Group and Db log files reside in d:\logs\First Storage Group

After backing up them, go into these directories and delete everything in, then re-try your restore.

Not the most efficient way, but works. Any other solutions are always welcome :)

There can be many reasons for having this error. One i faced was, when the system has McAfee Enterprise Virusscan installed and configured. The “access protection” can block your update and you can have this problem.

As suggested, Disable “access protection” while the update, and it should update successfuly.

Note : This is actually an incomplete troubleshooting tip. Please share your knowledge about this problem.

Thanks.