Accelerator Troubleshooting

NetBackup Accelerator
Challenge
Customers cant complete their full backups within their backup
window

Solution
Significantly reduce time required for full backups of file systems

Features
NetBackup client reads, de-duplicates and transfers only
changes to media server and sends only metadata for changes
to NetBackup catalog
Optimized synthetic full backup generated
NTFS change journal utilized to remove need to enumerate file
system
Accelerator functionality supported with all client OS platforms
(dedupe is performed on client, media server or appliance)
2

NetBackup Accelerator

Realized Value
Full backups to NetBackup dedupe, Cloud
or OST-vendor storage pools performed in
similar amount of time as incremental
backups
Reduced CPU and I/O overhead on
NetBackup client

Accelerator Overview
Significant time reduction in performing full backups
to file systems and VMware
Align with existing deployments
Leverage existing architectural framework & infrastructure
Allow use of existing data protection management
paradigm
Seamless integration with existing NetBackup environment.
Evolutionary approach to providing a new solution

Reduce catalog data for full backups sent to Master

Server
Improve RTO and RPO
Requires storage supporting Optimized Synthetics
and Optimized Duplication, or Cloud
4

Helpful processes and services

The following processes or binaries are beneficial
for troubleshooting:
NetBackup Backup Process: bpbkar
NetBackup Legacy Client Service: bpinetd
NetBackup Backup and Restore Manager: bpbrm
NetBackup Tape Manager: bptm
NetBackup Client Service: bpcd

Enabling the change journal: bpinetd log

INF - journal service monitor does not exist
for <C:\:\\?\Volume{25f60841-c605-11ddbae6-806e6f6e6963}\>
INF - opened change
database:<C:\VxCJMon.dat>
INF - Change Database header:
INF - journal id
: 0
INF - usn low
: 0
INF - usn high
: 0
INF - number of records
: 0
INF - index first
: 0
INF - index last
: 0
INF - number of free records : 0
INF - index first free
: 0
INF - hash
: 65536

After change journal is enabled: bpinetd

log
INF - growing change database from <266240>
bytes to <278528> bytes
INF - Change Database header:
INF - journal id
: 0
INF - usn low
: 0
INF - usn high
: 0
INF - number of records
: 0
INF - index first
: 0
INF - index last
: 0
INF - number of free records : 0
INF - index first free
: 0
INF - hash
: 65536

Creating VxCJDelete.dat: bpinetd log

INF - opened delete
database:<C:\VxCJDelete.dat>
INF - Delete Database header:
INF - journal id : 0
INF - usn low
: 0
INF - usn high
: 0
INF - size
: 00081000
INF - free
: 00000fd0
INF - used
: 00080030
INF - header size : 00080030
INF - snapshot needed for volume
guid:<\\?\Volume{25f60841-c605-11dd-bae6806e6f6e6963}\> (no journal id)
INF - created change journal monitor for
<C:\:\\?\Volume{25f60841-c605-11dd-bae6806e6f6e6963}\>

Creating a snapshot: bpinetd log

INF - executing command:<C:\Program
Files\Veritas\NetBackup\bin\bpfis.exe create -owner
NBU
-WOFB -fso -fim VSS -id VxCJ-Snapshot-17156453
\\?\Volume{25f60841-c605-11dd-bae6-806e6f6e6963}\>
....lines deleted....
INF - command returned
<
INF - BACKUP START 6108
INF - FIS_ID=VxCJ-Snapshot-17156453
INF - REMAP FILE BACKUP \\?\Volume{25f60841-c60511dd- bae6-806e6f6e6963}\ USING
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\
OPTIONS:ALT_PATH_PREFIX=C:\Program
Files\Veritas\NetBackup\temp\_vrts_frzn_img_6108_1,FI
TY PE=MIRROR,MNTPOINT=\\?\Volume{25f60841-c605-11ddbae6- 806e6f6e6963}\,FSTYPE=NTFS
INF - EXIT STATUS 0: the requested operation was
successfully completed
>
INF - successfully created snapshot for volume
guid:<\\?\Volume{25f60841-c605-11dd-bae6806e6f6e6963}\>

Deleting the snapshot: bpinetd log

INF - executing command:<C:\Program
Files\Veritas\NetBackup\bin\bpfis.exe delete
-id VxCJ-Snapshot-17156453 -copy 1>
INF - command returned:
<
INF - BACKUP START 4848
INF - EXIT STATUS 0: the requested operation
was successfully completed
>
INF - successfully deleted snapshot for
volume guid:<\\?\Volume{25f60841-c605-11ddbae6- 806e6f6e6963}\>

Growing the delete database: bpinetd

log
INF - maximum allowed usn before deleting
change journal:<17592184995840>
....lines deleted....
INF - growing delete database from <528384>
bytes to <1576960> bytes
INF - Delete Database header:
INF - journal id : 128733097860000000
INF - usn low
: 2675179520
INF - usn high
: 2675233568
INF - size
: 00181000
INF - free
: 00100026
INF - used
: 00080fda
INF - header size : 00080030

Growing the change database: bpinetd

log
INF - growing change database from <278528>
bytes to <290816> bytes
INF - Change Database header:
INF - journal id
:
128733097860000000
INF - usn low
: 2675179520
INF - usn high
: 2677842672
INF - number of records
: 384
INF - index first
: 23
INF - index last
: 383
INF - number of free records : 0
INF - index first free
: 0
INF - hash
: 65536

Restarting the change database:

bpinetd log
INF - opened change
database:<C:\VxCJMon.dat>
INF - Change Database header:
INF - journal id
:
128733097860000000
INF - usn low
:
INF - usn high
:
INF - number of records
:
INF - index first
:
INF - index last
:
INF - number of free records :
INF - index first free
:
INF - hash
:

2675179520
2678812672
768
23
605
163
549
65536

Restarting the delete database: bpinetd

log
INF - opened delete
database:<C:\VxCJDelete.dat>
INF - Delete Database header:
INF - journal id : 128733097860000000
INF - usn low
: 2675179520
INF - usn high
: 2678812672
INF - size
: 00181000
INF - free
: 00089930
INF - used
: 000f76d0
INF - header size : 00080030

Setting up a volume: bpbkar log (1 of 4)

INF - volume guid:<\\?\Volume{25f60841-c60511dd-bae6-806e6f6e6963}\>
INF - mounted at:<C:\>:<\\?\Volume{25f60841c605-11dd-bae6-806e6f6e6963}\>
INF - adding to collection,
volume:<\\?\Volume{25f60841-c605-11dd-bae6806e6f6e6963}\>:<C:\>

Setting up a volume: bpbkar log (2 of 4)

INF - opened change
database:<C:\VxCJMon.dat>
INF - Change Database header:
INF - journal id
:
128733097860000000
INF - usn low
:
INF - usn high
:
INF - number of records
:
INF - index first
:
INF - index last
:
INF - number of free records :
INF - index first free
:
INF - hash
:

2675179520
2686587912
1152
23
765
54
739
65536

Setting up a volume: bpbkar log (3 of 4)

INF - opened delete
database:<C:\VxCJDelete.dat>
INF - Delete Database header:
INF - journal id : 128733097860000000
INF - usn low
: 2675179520
INF - usn high
: 2686587912
INF - size
: 00281000
INF - free
: 0006d75c
INF - used
: 002138a4
INF - header size : 00080030

Setting up a volume: bpbkar log (4 of 4)

Server Name
: microwavevm5.min.veritas.com
Policy Name
: test-c
File Directive : C:\Program
Files\Veritas\NetBackup\logs
Last USN (FULL) : 2679937632
Last USN (CINC) : 0
Last USN (DINC) : 0
backup status
: 0
Server Name
: microwavevm5.min.veritas.com
Policy Name
: test-b3
File Directive : C:\Demo\Scenario 2\Folder-0
Last USN (FULL) : 2678351232
Last USN (CINC) : 0
Last USN (DINC) : 0
backup status
: 0

Change database is open: bpbkar log

INF - opened change
database:<C:\VxCJMon.dat>
INF - Change Database header:
INF - journal id
:
128733097860000000
INF - usn low
:
INF - usn high
:
INF - number of records
:
INF - index first
:
INF - index last
:
INF - number of free records :
INF - index first free
:
INF - hash
:

2675179520
2686587912
1152
23
765
54
739
65536

Delete database is open: bpbkar log

INF - opened delete
database:<C:\VxCJDelete.dat>
INF - Delete Database header:
INF - journal id : 128733097860000000
INF - usn low
: 2675179520
INF - usn high
: 2686587912
INF - size
: 00281000
INF - free
: 0006d75c
INF - used
: 002138a4
INF - header size : 00080030

Errors when preparing for enumeration

Error

Parameter

Description

C000000
d

STATUS_INVALID_PARAM
ETER

The USN record corresponds to

an item that has been deleted
recently.

C000004
3

STATUS_SHARING_VIOLA
TION

The USN record corresponds to

an item that is currently open
exclusively by some other
process.

C000005
6

STATUS_DELETE_PENDIN
G

The USN record corresponds to

an item that has a pending
delete request against it.

Thank you!