cancel
Showing results for 
Search instead for 
Did you mean: 

Checkpoints and backups with big execution windows

Dan_Vargas
Level 4

Hi,

 

Checkpoints seem to not be working on my environment. Well, that's not accurate: For the same windows  host, checkpoints seem to work for regular folders (like de G: drive) but not for my DFSR folders (copied via SCC\User Data\DFSRFolders)

 

  I'm talking about a very big and slow full backup takes 35-40h to complete. Last time it failed after 30h and it restarted from scratch, not using any checkpoints. It started on a Saturday early morning and failes on a Sunday afternoon. As I said, the backup for the G: drive did resume from the checkpint and

Any idea why? My Clean-up property  "Move backup job from incomplete state to done state" was set to 6h (will change it to 24h) and "Schedule backup attempts" is set to "2 tries per 3h".

 

From the logs of the job that was able to resume the backup I see this:

 

04/06/2016 09:31:46 - Info nbjm(pid=5080) resumed backup (backupid=SERVERNAME_1464976812) job for client SERVERNAME, policy SERVERNAME, schedule Full on storage unit TLD3
04/06/2016 09:31:49 - Info bpbrm(pid=1968) SERVERNAME is the host to backup data from     
04/06/2016 09:31:49 - Info bptm(pid=7660) using 65536 data buffer size        
04/06/2016 09:31:49 - Info bpbrm(pid=1968) telling media manager to start backup on client     
04/06/2016 09:31:49 - Info bptm(pid=7660) using 128 data buffers         
04/06/2016 09:31:49 - Info bptm(pid=7660) resuming backup-id SERVERNAME_1464976812 copy 1 at fragment 91, 512 blocks: 344496263  
04/06/2016 09:31:57 - Info bpbrm(pid=5320) sending bpsched msg: CONNECTING TO CLIENT FOR SERVERNAME_1464976812    

 

But the one that didn't resume the backup doesn't mention the line where it states what fragment it should be using:

 

05/06/2016 19:26:05 - Info nbjm(pid=5080) resumed backup (backupid=SERVERNAME_1465017500) job for client SERVERNAME, policy SERVERNAME_DFSR2, schedule Full on storage unit TLD0
05/06/2016 19:26:12 - Info bpbrm(pid=7712) SERVERNAME is the host to backup data from     
05/06/2016 19:26:12 - Info bptm(pid=9132) using 65536 data buffer size        
05/06/2016 19:26:12 - Info bpbrm(pid=7712) telling media manager to start backup on client     
05/06/2016 19:26:12 - Info bptm(pid=9132) using 128 data buffers         
05/06/2016 19:26:16 - Info bpbrm(pid=8560) sending bpsched msg: CONNECTING TO CLIENT FOR SERVERNAME_1465017500     
05/06/2016 19:26:16 - connecting

=====

Thanks!

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Will_Restore
Level 6

Don't think Checkpoint supports SCC just regular filesystems. Having trouble finding the definitive document though. 

 

Ah, here we go:

https://www.veritas.com/support/en_US/article.000044231

The following pertain to Windows clients:

  • Checkpoint restart is not supported for the backup selections that are indicated by a UNC path.

  • No checkpoints are taken during a System State backup.

  • No checkpoints are taken during a Windows disk image (raw) backup.

  • No checkpoints are taken for the remainder of the backup after NetBackup encounters Single-instance Store (SIS).

 

View solution in original post

4 REPLIES 4

Will_Restore
Level 6

Don't think Checkpoint supports SCC just regular filesystems. Having trouble finding the definitive document though. 

 

Ah, here we go:

https://www.veritas.com/support/en_US/article.000044231

The following pertain to Windows clients:

  • Checkpoint restart is not supported for the backup selections that are indicated by a UNC path.

  • No checkpoints are taken during a System State backup.

  • No checkpoints are taken during a Windows disk image (raw) backup.

  • No checkpoints are taken for the remainder of the backup after NetBackup encounters Single-instance Store (SIS).

 

Dan_Vargas
Level 4

Thanks Will, I saw that in the admin guide, but I don't see SCC referenced there and if I'm not mistaken SS is different from SCC.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I am with Will - thinking that checkpoints may not be supported for SCC.

Is checkpoint option available when you create a separate policy for Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\ ?

bpbkar log on the client will confirm if checkpoints are taken for SCC during backup - possibly with logging level between 1 and 3.

Dan_Vargas
Level 4

Talked yesterday with Veritas. They said that anything that uses VSS doesn't support checkpoints :(

 

Thanks guys!