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.

First possible reason is: If you have upgraded windows 2003 from R1 SP2 to R2, this can be the reason. Try to reinstall Service Pack 2 for R2. This should possibly solve your problem.

One of the reasons is you made a mistake writing in the script, and its giving and error and the scripts returns an error code other than zero.

In that case you will see log entries similar to this:

00:06:16.311 [15443] <4> bpbkar: INF – bpbkar exit normal
00:06:16.327 [15443] <4> bpbkar: INF – EXIT STATUS 0: the requested operation was successfully completed
00:06:16.328 [15443] <4> bpbkar: INF – setenv FINISHED=1
00:06:16.372 [15443] <4> bpbkar: INF – START bpend_notify
00:06:16.372 [15443] <4> bpbkar: /usr/openv/netbackup/bin/bpend_notify.Oracle_test oracle Oracle_test Full FULL 0
00:06:17.325 [15443] <4> bpbkar: INF – END bpend_notify
00:06:17.326 [15443] <16> bpbkar: ERR – bpend_notify returned 2
00:08:27.195 [16268] <4> bpbkar main: real locales <LC_CTYPE=en_US;LC_NUMERIC=en_US;LC_TIME=en_US;LC_COLLATE=en_US;LC_MONETARY=C;LC_MESSAGES=en_US;LC_PAPER=C;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C;LC_IDENTIFICATION=C>

admin – Keeps the logs of adminstrative commands
bpbrm – Keeps the logs of backup and restore manager
bpcd - Keeps the logs of client daemon
bpdbjobs - Keeps the logs of database manager program process
bpdm - Keeps the logs of disk manager process
bpjava-msvc - Keeps the logs of Java application server authentication service
bprd - Keeps the logs of request daemon process
bpsched - Keeps the logs of scheduler process that runs on master servers
bptm - Keeps the logs of media management process
bparchive - Keeps the logs of archive program
bpbackup - Keeps the logs of backup program
bpbkar - Keeps the logs of program that generates golden images
bplist - Keeps the logs of program that lists backed up and archived files
user-ops - directory for use by Java programsbp – client user interface process

on Master Server -> Media, right click on the tape and if selectable, click on “Unfreeze”, and try again.

4/27/2009 4:59:32 PM – Critical bpbrm(pid=7716) from client test.local: FTL – snapshot creation failed, status 156
4/27/2009 4:59:32 PM – end Flash Backup Windows , Create Snapshot; elapsed time: 00:00:08
4/27/2009 4:59:32 PM – end writing
Status 156

When you look at the bpfis logs you can see a log like this:

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:28.840 'SOAP' 6504 trivia] Sending soap request to [TCP:test.local:443]: GetSummary

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:29.043 'SOAP' 6504 trivia] Received soap response from [TCP:test.local:443]: GetSummary

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:29.043 'SOAP' 6504 trivia] Sending soap request to [TCP:test.local:443]: GetSnapshot

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:29.262 'SOAP' 6504 trivia] Received soap response from [TCP:test.local:443]: GetSnapshot

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:29.262 'vcbMounter' 6504 info] Scanning snapshot _VCB-BACKUP_

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:29.262 'vcbMounter' 6504 info] Found match: snapshot-1847

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:29.262 'vcbMounter' 6504 error] Error: Backup snapshot already exists.

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     [2009-04-27 16:59:29.262 'vcbMounter' 6504 error] An error occurred, cleaning up…

16:59:30.699 [5512.6280] <2> onlfi_vfms_logf:     Deleted directory c:\netbackup_vmware_mnt\test.local

The reason can be a remaining snapshot that vmware couldnt remove successfuly on a previous backup attempt.

Try to remove that snapshot from the server  and retry your backup.

“Robot inventory failed: Unable to open robotic path (201).”

The causes can be: (Reference: http://seer.entsupport.symantec.com/docs/269409.htm)

1. Because the library door is left open
2. The is library is not connected, offline, shutdown or in the middle of a scan
3. The library is not in SCSI mode
4. Some other software has locked the SCSI path (Like robtest)
5. SCSI path has changed.

Solutions:
1. Check that the library door is closed.
2. Check that the library is running, online and connected.
3. Check that the library is in SCSI mode.
4. Run: /usr/openv/netbackup/bin/bpps (UNIX) or <install_path>\veritas\netbackup\bin\bpps (windows)

Check that this command does not list any robtest/robtest.exe (UNIX/windows) process. If exists, kill the process

5. Open the Device Manager on windows and try to see if the “Medium Changer” is listed. It should exist for Netbackup to work.
6.  Run : /usr/openv/volmgr/bin/tpautoconf -r (UNIX) or <install_path>\veritas\volmgr\bin\tpautoconf -r (windows)

and try to see if robot is still communicating with the Operating System.
C:\Program Files\VERITAS\Volmgr\bin>tpautoconf -r
TPAC45 M4 DATA MagFile         3.05 RBD12A0007 2 0 0 0 Changer0 - -

7. If “tpautoconf -r” works, use the NetBackup Administration Console to re-browse for the robot on the Robot Control Host.

limit has been reached for requested resource NBU_POLICY.MAXJOBS.CatalogBackup

Most probably this is an issue about NBU 6.5.3. If you can look at the following bug report page:

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

The easiest way to resolve the problem is to restart netbackup daemons.

Another method is explained in the above document.

SQL> startup
ORACLE instance started.

Total System Global Area  643219456 bytes
Fixed Size                  2105256 bytes
Variable Size             419430488 bytes
Database Buffers          213909504 bytes
Redo Buffers                7774208 bytes
Database mounted.
ORA-16038: log 1 sequence# 619 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
‘/app/oracle/product/11g/databases/redo01.log’

The reason is your flash recovery area is full, you need to increase it. Try the following:

1. Startup your database if not already, it will give the same error…

2. Alter your database, then shutdown and startup again.

sqlplus "/ as sysdba"
alter system set DB_RECOVERY_FILE_DEST_SIZE = 10g;
System altered.
SQL> shutdown immediate;
SQL> startup
ORACLE instance started.

Total System Global Area  643219456 bytes
Fixed Size                  2105256 bytes
Variable Size             419430488 bytes
Database Buffers          213909504 bytes
Redo Buffers                7774208 bytes
Database mounted.
Database opened.
SQL> quit

Try your rman backups again, and they shoould work…

——————————-
Installing VRTSpbx…

Can’t locate CPI/common/CPI.pm in @INC (@INC contains: ./authentication/scripts ./perl/lib/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/5.8.8 ./perl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/site_perl/5.8.8 ./perl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/site_perl/5.8.8 ./perl/lib/site_perl /opt/VRTSperl/lib/5.8.8/sun4-solaris-thread-multi-64int /opt/VRTSperl/lib/5.8.8 /opt/VRTSperl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int /opt/VRTSperl/lib/site_perl/5.8.8 /opt/VRTSperl/lib/site_perl .) at ./installics line 7.

BEGIN failed–compilation aborted at ./installics line 7.

The ICS install for VRTSpbx was unsuccessful.

Quitting the NetBackup install.

Rerun /usr/openv/netbackup/bin/install_bp when the problem has been resolved.

1. There can be another restore process using the same resources, or a restore job is stuck. Try to resume your restore after the other restore finishes. If the restore job is stuck check netbackup/db/jobs/restart/ directory, there should be no jobs in this directory after all jobs are finished. Delete the files if there are any.

2. You might have selected multiple backup images at the same restore job. Try to restore every image one by one…

3. The image you’re trying to restore is about to expire and this message is given:  In order to be able to restore this image you need to resume your restore before the first image is expired.