cancel
Showing results for 
Search instead for 
Did you mean: 

NBU_Catalog backup using 2 tapes

All of a sudden my catalog backup is using two tapes.

The parent job starts the two child objects.  The first job completes in under 1 minute.  The second job loads another tape and completes in just over 5 minutes.  Up until the 5th of this month the second job would use the same tape.  The catalog size is not the problem.  Each backup starts at position 1 as you will see.

 

Job 1

8/5/2008 7:00:14 AM - requesting resource Any
8/5/2008 7:00:14 AM - requesting resource pabackup.NBU_CLIENT.MAXJOBS.pabackup
8/5/2008 7:00:14 AM - requesting resource pabackup.NBU_POLICY.MAXJOBS.NBU_Catalogs
8/5/2008 7:00:14 AM - granted resource pabackup.NBU_CLIENT.MAXJOBS.pabackup
8/5/2008 7:00:14 AM - granted resource pabackup.NBU_POLICY.MAXJOBS.NBU_Catalogs
8/5/2008 7:00:14 AM - granted resource A00014
8/5/2008 7:00:14 AM - granted resource IBMULT3580-TD31
8/5/2008 7:00:14 AM - granted resource IBMTS3500-1
8/5/2008 7:00:14 AM - estimated 16858622 kbytes needed
8/5/2008 7:00:14 AM - started process bpbrm (3708)
8/5/2008 7:00:15 AM - connecting
8/5/2008 7:00:23 AM - connected; connect time: 00:00:08
8/5/2008 7:00:26 AM - mounting A00014
8/5/2008 7:00:48 AM - mounted; mount time: 00:00:22
8/5/2008 7:00:48 AM - positioning A00014 to file 1
8/5/2008 7:00:51 AM - positioned A00014; position time: 00:00:03
8/5/2008 7:00:51 AM - begin writing
8/5/2008 7:00:58 AM - end writing; write time: 00:00:07
the requested operation was successfully completed(0)

 

Job 2

8/5/2008 7:00:59 AM - requesting resource Any
8/5/2008 7:00:59 AM - requesting resource pabackup.NBU_CLIENT.MAXJOBS.pabackup
8/5/2008 7:00:59 AM - requesting resource pabackup.NBU_POLICY.MAXJOBS.NBU_Catalogs
8/5/2008 7:01:00 AM - granted resource pabackup.NBU_CLIENT.MAXJOBS.pabackup
8/5/2008 7:01:00 AM - granted resource pabackup.NBU_POLICY.MAXJOBS.NBU_Catalogs
8/5/2008 7:01:00 AM - granted resource A00017
8/5/2008 7:01:00 AM - granted resource IBMULT3580-TD30
8/5/2008 7:01:00 AM - granted resource IBMTS3500-1
8/5/2008 7:01:00 AM - estimated 16858622 kbytes needed
8/5/2008 7:01:00 AM - started process bpbrm (3996)
8/5/2008 7:01:00 AM - connecting
8/5/2008 7:01:00 AM - connected; connect time: 00:00:00
8/5/2008 7:01:03 AM - mounting A00017
8/5/2008 7:01:24 AM - mounted; mount time: 00:00:21
8/5/2008 7:01:24 AM - positioning A00017 to file 1
8/5/2008 7:01:28 AM - positioned A00017; position time: 00:00:04
8/5/2008 7:01:28 AM - begin writing
8/5/2008 7:06:26 AM - end writing; write time: 00:04:58
the requested operation was successfully completed(0)

 

So far Symantec has no answer.

 

1 Solution

Accepted Solutions
Accepted Solution!

Re: NBU_Catalog backup using 2 tapes

Leave tape alert as it is.  If indeed you have defined a cleaning slot, then this could be an issue.  What you need to do is have the tape slot defined as a data (regular) slot.  Then create a barcode rule that identifies the tape in the robotic as a cleaning tape.  NetBackup will take it from there.

View solution in original post

4 Replies

Re: NBU_Catalog backup using 2 tapes

What platform and version of NetBackup are you running.

 

I had a problem similar to this when I defined a cleaning slot within our tape drive AND NetBackup Tape Alert was enabled (which it is by default).

Re: NBU_Catalog backup using 2 tapes

Hello Ron. Windows 2003 SP2 and NetBackup Enterprise 6.5.1
I will look at the Tape alert.
Accepted Solution!

Re: NBU_Catalog backup using 2 tapes

Leave tape alert as it is.  If indeed you have defined a cleaning slot, then this could be an issue.  What you need to do is have the tape slot defined as a data (regular) slot.  Then create a barcode rule that identifies the tape in the robotic as a cleaning tape.  NetBackup will take it from there.

View solution in original post

Re: NBU_Catalog backup using 2 tapes

Thanks Ron.  That did it.  I had library based cleaning from back in the 4.x and 5.x days.  I disabled library based and reconfigured by cleaning tapes, and made sure Tape Alerts were enabled.  After cleaning the drives everything worked as it should.