accelerator troubleshooting
DESCRIPTION
Troubeshooting Netbackup AcceleratorTRANSCRIPT
Accelerator Troubleshooting
NetBackup Accelerator
• Challenge– Customers can’t 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
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
Helpful processes and services
Enabling the change journal: bpinetd log
INF - journal service monitor does not exist for <C:\:\\?\Volume{25f60841-c605-11dd-bae6-806e6f6e6963}\>
INF - opened change database:<C:\VxCJMon.dat>INF - Change Database header:INF - journal id : 0INF - usn low : 0INF - usn high : 0INF - number of records : 0INF - index first : 0INF - index last : 0INF - number of free records : 0INF - index first free : 0INF - 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 : 0INF - usn low : 0INF - usn high : 0INF - number of records : 0INF - index first : 0INF - index last : 0INF - number of free records : 0INF - index first free : 0INF - hash : 65536
Creating VxCJDelete.dat: bpinetd log
INF - opened delete database:<C:\VxCJDelete.dat>INF - Delete Database header:INF - journal id : 0INF - usn low : 0INF - usn high : 0INF - size : 00081000INF - free : 00000fd0INF - used : 00080030INF - header size : 00080030INF - snapshot needed for volume guid:<\\?\Volume{25f60841-c605-11dd-bae6-
806e6f6e6963}\> (no journal id)INF - created change journal monitor for
<C:\:\\?\Volume{25f60841-c605-11dd-bae6- 806e6f6e6963}\>
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 6108INF - FIS_ID=VxCJ-Snapshot-17156453INF - REMAP FILE BACKUP \\?\Volume{25f60841-c605-11dd- bae6-806e6f6e6963}\ USING \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\ OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_6108_1,FITYPE=MIRROR,MNTPOINT=\\?\Volume{25f60841-c605-11dd-bae6- 806e6f6e6963}\,FSTYPE=NTFSINF - EXIT STATUS 0: the requested operation was
successfully completed>INF - successfully created snapshot for volume guid:<\\?\Volume{25f60841-c605-11dd-bae6-806e6f6e6963}\>
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 4848INF - EXIT STATUS 0: the requested operation
was successfully completed>INF - successfully deleted snapshot for volume guid:<\\?\Volume{25f60841-c605-11dd-bae6- 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 : 128733097860000000INF - usn low : 2675179520INF - usn high : 2675233568INF - size : 00181000INF - free : 00100026INF - used : 00080fdaINF - header size : 00080030
Growing the change database: bpinetd log
INF - growing change database from <278528> bytes to <290816> bytesINF - Change Database header:INF - journal id : 128733097860000000INF - usn low : 2675179520INF - usn high : 2677842672INF - number of records : 384INF - index first : 23INF - index last : 383INF - number of free records : 0INF - index first free : 0INF - hash : 65536
Restarting the change database: bpinetd log
INF - opened change database:<C:\VxCJMon.dat>INF - Change Database header:INF - journal id : 128733097860000000INF - usn low : 2675179520INF - usn high : 2678812672INF - number of records : 768INF - index first : 23INF - index last : 605INF - number of free records : 163INF - index first free : 549INF - hash : 65536
Restarting the delete database: bpinetd log
INF - opened delete database:<C:\VxCJDelete.dat>INF - Delete Database header:INF - journal id : 128733097860000000INF - usn low : 2675179520INF - usn high : 2678812672INF - size : 00181000INF - free : 00089930INF - used : 000f76d0INF - header size : 00080030
Setting up a volume: bpbkar log (1 of 4)
INF - volume guid:<\\?\Volume{25f60841-c605-11dd-bae6-806e6f6e6963}\>
INF - mounted at:<C:\>:<\\?\Volume{25f60841-c605-11dd-bae6-806e6f6e6963}\>
INF - adding to collection, volume:<\\?\Volume{25f60841-c605-11dd-bae6-806e6f6e6963}\>:<C:\>
Setting up a volume: bpbkar log (2 of 4)
INF - opened change database:<C:\VxCJMon.dat>INF - Change Database header:INF - journal id : 128733097860000000INF - usn low : 2675179520INF - usn high : 2686587912INF - number of records : 1152INF - index first : 23INF - index last : 765INF - number of free records : 54INF - index first free : 739INF - hash : 65536
Setting up a volume: bpbkar log (3 of 4)
INF - opened delete database:<C:\VxCJDelete.dat>INF - Delete Database header:INF - journal id : 128733097860000000INF - usn low : 2675179520INF - usn high : 2686587912INF - size : 00281000INF - free : 0006d75cINF - used : 002138a4INF - header size : 00080030
Setting up a volume: bpbkar log (4 of 4)
Server Name : microwavevm5.min.veritas.comPolicy Name : test-cFile Directive : C:\Program Files\Veritas\NetBackup\logsLast USN (FULL) : 2679937632Last USN (CINC) : 0Last USN (DINC) : 0backup status : 0Server Name : microwavevm5.min.veritas.comPolicy Name : test-b3File Directive : C:\Demo\Scenario 2\Folder-0Last USN (FULL) : 2678351232Last USN (CINC) : 0Last USN (DINC) : 0backup status : 0
Change database is open: bpbkar log
INF - opened change database:<C:\VxCJMon.dat>INF - Change Database header:INF - journal id : 128733097860000000INF - usn low : 2675179520INF - usn high : 2686587912INF - number of records : 1152INF - index first : 23INF - index last : 765INF - number of free records : 54INF - index first free : 739INF - hash : 65536
Delete database is open: bpbkar log
INF - opened delete database:<C:\VxCJDelete.dat>INF - Delete Database header:INF - journal id : 128733097860000000INF - usn low : 2675179520INF - usn high : 2686587912INF - size : 00281000INF - free : 0006d75cINF - used : 002138a4INF - header size : 00080030
Errors when preparing for enumeration
Error Parameter Description
C000000d STATUS_INVALID_PARAMETER The USN record corresponds to an item that has been deleted recently.
C0000043 STATUS_SHARING_VIOLATION The USN record corresponds to an item that is currently open exclusively by some other process.
C0000056 STATUS_DELETE_PENDING The USN record corresponds to an item that has a pending delete request against it.
Thank you!