Currently I have implemented synthetic backup with the following schedule

[Paulo_Mendez]

Currently I have implemented synthetic backup with the following schedule:

Full: Saturday disk

Incremental: Daily Disc

Synthetic Backup daily tapes after ending incremental backup to disk

Because she is waiting for more than 5 hours?
Is there any way to reduce this time?.

The environment is Windows 2008 R2 with Netbackup 7.1 (Master and Media Servers)


Provide details of job

17-01-2012 2:10:00 - Info nbjm(pid=4684) starting backup job (jobid=169) for client serv-archivos, policy w_sintetico_serv-archivos, schedule diarioCinta  
17-01-2012 2:10:00 - Info nbjm(pid=4684) requesting NO_STORAGE_UNIT resources from RB for backup job (jobid=169, request id:{767DED75-73B8-4B3C-A384-1FA46F22B403})  
17-01-2012 2:10:00 - requesting resource sun245.NBU_CLIENT.MAXJOBS.serv-archivos
17-01-2012 2:10:00 - requesting resource sun245.NBU_POLICY.MAXJOBS.w_sintetico_serv-archivos
17-01-2012 2:10:00 - begin
17-01-2012 2:10:00 - begin Query Database
17-01-2012 2:10:00 - granted resource sun245.NBU_CLIENT.MAXJOBS.serv-archivos
17-01-2012 2:10:00 - granted resource sun245.NBU_POLICY.MAXJOBS.w_sintetico_serv-archivos
17-01-2012 2:10:00 - estimated 259777120 Kbytes needed
17-01-2012 2:10:00 - begin Parent Job
17-01-2012 2:10:00 - begin Synthetic, Start Notify Script
17-01-2012 2:10:00 - Info RUNCMD(pid=7512) started            
17-01-2012 2:10:00 - Info RUNCMD(pid=7512) exiting with status: 0         
Status 0
17-01-2012 2:10:00 - end Synthetic, Start Notify Script; elapsed time: 00:00:00
17-01-2012 2:10:00 - begin Synthetic, Execute Script
17-01-2012 2:10:00 - started process bpbrm (2196)
17-01-2012 2:10:00 - end Synthetic, Execute Script; elapsed time: 00:00:00
17-01-2012 2:10:00 - begin Process Extents
17-01-2012 2:10:06 - end Process Extents; elapsed time: 00:00:06
17-01-2012 2:10:06 - end Parent Job; elapsed time: 00:00:06
17-01-2012 2:10:06 - begin Request Resources
17-01-2012 2:10:06 - requesting resource sun245-hcart2-robot-tld-0
17-01-2012 2:10:06 - reserving resource 0056L5
17-01-2012 2:10:06 - awaiting resource 0056L5 Reason: Media is in use, Media Server: N/A,
     Robot Number: NONE, Robot Type: NONE, Media ID: 0056L5, Drive Name: N/A,
     Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
    
17-01-2012 2:33:13 - awaiting resource sun245-hcart2-robot-tld-0 - No drives are available
17-01-2012 4:04:53 - awaiting resource 0056L5 Reason: Media is in use, Media Server: N/A,
     Robot Number: NONE, Robot Type: NONE, Media ID: 0056L5, Drive Name: N/A,
     Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
    
17-01-2012 4:19:54 - awaiting resource sun245-hcart2-robot-tld-0 Reason: Drives are in use, Media Server: sun245,
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: wSintetico, Storage Unit: sun245-hcart2-robot-tld-0, Drive Scan Host: N/A
    
17-01-2012 4:21:29 - awaiting resource 0056L5 Reason: Media is in use, Media Server: N/A,
     Robot Number: NONE, Robot Type: NONE, Media ID: 0056L5, Drive Name: N/A,
     Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
    
17-01-2012 7:55:48 - reserved resource 0056L5
17-01-2012 7:55:48 - granted resource 0058L5
17-01-2012 7:55:48 - granted resource IBM.ULTRIUM-HH5.000
17-01-2012 7:55:48 - granted resource sun245-hcart2-robot-tld-0
17-01-2012 7:55:49 - end Request Resources; elapsed time: 05:45:43
17-01-2012 7:55:49 - end Query Database; elapsed time: 05:45:49
17-01-2012 7:55:49 - begin Organize Readers
17-01-2012 7:55:49 - begin synthetic writer to serv-archivos_1326769506
17-01-2012 7:55:49 - begin synthetic reader 1 for 3 extents from serv-archivos_1326769505 on F:\stagings\semanal
17-01-2012 7:55:49 - end Organize Readers; elapsed time: 00:00:00
17-01-2012 7:55:49 - Info bptm(pid=7228) start            
17-01-2012 7:55:50 - Info bpdm(pid=6324) started            
17-01-2012 7:55:50 - started process bpdm (6324)
17-01-2012 7:55:50 - started process bptm (7228)
17-01-2012 7:55:50 - Info bpdm(pid=6324) reading backup image          
17-01-2012 7:55:50 - Info bptm(pid=7228) using 524288 data buffer size        
17-01-2012 7:55:50 - Info bptm(pid=7228) setting receive network buffer to 2098176 bytes      
17-01-2012 7:55:50 - Info bptm(pid=7228) using 128 data buffers         
17-01-2012 7:55:50 - Info bpdm(pid=6324) using 128 data buffers         
17-01-2012 7:55:50 - Info bpdm(pid=6324) spawning a child process         
17-01-2012 7:55:50 - Info bpbrm(pid=6324) child pid: 4032          
17-01-2012 7:55:50 - Info bptm(pid=7228) start backup           
17-01-2012 7:55:50 - Info bptm(pid=7228) backup child process is pid 8088.1028       
17-01-2012 7:55:50 - Info bptm(pid=7228) Waiting for mount of media id 0058L5 (copy 1) on server sun245.
17-01-2012 7:55:50 - mounting 0058L5
17-01-2012 7:55:50 - Info bpdm(pid=4032) started            
17-01-2012 7:55:50 - started process bpdm (4032)
17-01-2012 7:55:50 - sending extents 0-2 to reader 1
17-01-2012 7:55:50 - Info bptm(pid=8088) start            
17-01-2012 7:55:50 - started process bptm (8088)
17-01-2012 7:55:50 - begin reading
17-01-2012 7:56:27 - Info bptm(pid=7228) media id 0058L5 mounted on drive index 0, drivepath {6,0,0,0}, drivename IBM.ULTRIUM-HH5.000, copy 1
17-01-2012 7:56:27 - mounted; mount time: 00:00:37
17-01-2012 7:58:18 - end reading; read time: 00:02:28
17-01-2012 7:58:18 - begin reading
17-01-2012 7:58:54 - end reading; read time: 00:00:36
17-01-2012 7:58:54 - begin reading
17-01-2012 7:58:58 - end reading; read time: 00:00:04
17-01-2012 7:58:58 - Info bpdm(pid=6324) completed reading backup image         
17-01-2012 7:58:58 - end synthetic reader 1; read time: 00:03:09
17-01-2012 7:58:58 - Info bpdm(pid=6324) EXITING with status 0         
17-01-2012 7:58:58 - begin synthetic reader 2 for 121 extents from serv-archivos_1326683101 on 0056L5
17-01-2012 7:58:58 - requesting resource 0056L5
17-01-2012 7:58:58 - granted resource 0056L5
17-01-2012 7:58:58 - granted resource IBM.ULTRIUM-HH5.002
17-01-2012 7:58:59 - Info bptm(pid=7912) Waiting for mount of media id 0056L5 (copy 1) on server sun245.
17-01-2012 7:58:59 - started process bptm (7912)
17-01-2012 7:58:59 - mounting 0056L5
17-01-2012 7:58:59 - Info bptm(pid=7912) INF - Waiting for mount of media id 0056L5 on server sun245 for reading.
17-01-2012 7:58:59 - sending extents 3-123 to reader 2
17-01-2012 7:59:34 - mounted; mount time: 00:00:35
17-01-2012 7:59:34 - Info bptm(pid=7912) 0056L5            
17-01-2012 7:59:34 - Info bptm(pid=7912) INF - Waiting for positioning of media id 0056L5 on server sun245 for reading.
17-01-2012 7:59:34 - positioning 0056L5 to file 31
17-01-2012 8:01:40 - positioned 0056L5; position time: 00:02:06
17-01-2012 8:01:40 - begin reading
17-01-2012 10:07:21 - Info bptm(pid=7228) waited for full buffer 215879 times, delayed 457708 times    
17-01-2012 10:07:21 - end reading; read time: 02:05:41
17-01-2012 10:07:22 - end synthetic reader 2; read time: 02:08:24
17-01-2012 10:07:26 - end synthetic writer to serv-archivos_1326769506; write time 02:11:37
17-01-2012 10:07:26 - Info bptm(pid=7228) EXITING with status 0 <----------        
17-01-2012 10:07:30 - end ; elapsed time: 07:57:30
17-01-2012 10:07:30 - end writing
Status 0
17-01-2012 10:07:30 - end operation
17-01-2012 10:07:30 - begin Synthetic, End Notify Script
17-01-2012 10:07:30 - Info RUNCMD(pid=6208) started            
17-01-2012 10:07:30 - Info RUNCMD(pid=6208) exiting with status: 0         
Status 0
17-01-2012 10:07:30 - end Synthetic, End Notify Script; elapsed time: 00:00:00
Status 0
17-01-2012 10:07:30 - end operation
the requested operation was successfully completed(0)

[Mark_Solutions]

Looks to me as though the Synthetic is reading from tape not disk

You need to do your synthetic to disk as well so that it is ready for the next weeks synthetic as it becomes the new full back that will be used

So Real full to disk (then staged to tape)

Then Diffs to disk (and staged to tape if you wish)

Then Sysnthetic to disk (and staged to tape)

You need enough disk space for the 2 full backups plus the incrementals, otherwise it will start to read from tape instead of disk if the last full (whether real or synthetic) has been expired from disk

Hope this helps

[Will_Restore]

You could set up a unique volume pool for your schedule diarioCinta so there is no media contention with other jobs.

[Paulo_Mendez]

Wrobbins

On the other hand because I asked two synthetic backup tapes,
Just synthetic backup should be performed only with a tape LTO5?
How I can reduce the time of the synthetic backup?
How I can do that only use a single backup tape for each synthetic?

The execution times are:
1:30
2:00
2:10
two at 2:30, 2:30
3:00

What happens is that several synthetic backups with a volume pool named "wsintetico"

Some finish on time, but others take longer, as described above,
One because the media is in use and also because the required synthetic occasions following previous half is still in use,
I have 3 Drive LTO5 ,

[Mark_Solutions · Accepted solution]

To do this at its fastest follow what i have said in my earlier post - do everything on disk and then duplicate it later