NBU restore VMs from AIR_Gapped DR site into Main site
we are checking the possibility to restore a VM from AIR_Gap replication location back into the main site's Vcenter1 main site: NBU1+Vcenter1 DR site: NBU2+Vcenter2 VM initially resides on Vcenter1 of main site, NBU 10.2.0.1 (flex instance) takes backup of this VM and replicate its backup image to WORM in DR (NBU2). in case we got disaster in main site and NBU1 in main site is crashed, can we restore the VM from WORM/AIR-Gap (NBU2) into Vcenter1? is it only that we need to add Vcenter1 into NBU2? thanks,
The discrepancy in "file counts" between replicated backup job
Hi, We have 2 Netbackup instances, one is at the primary site, and another is at the DR site. And, the primary instance replicates all the backups to the DR instance every day. And our backup system's auditor yesterday noticed that, even for the backup from the same VM, the Files counts at its primary backup is different to its replication at the DR (see below) So, I'm wondering if anyone could help me to answer the below 2 questions (from our auditor) What caused this discrepancy in “File counts” ? Is “this discrepancy” a problem ? Thanks, Kelvin
How to create a replication (AIR) duration report
Hi, hope you all guys doing well. I'm new in OpsCenter and were having a hard time to create a specific report for AIR jobs. We want to make a report that contains the ff. Job Type: Replication Client Name Policy Name Job Duration Job File Count Throughput KB/sec) Schedule/Level Type: Schedule Name:Is there any NBU command/syntax to check the duration&speed of each completed AIR/replication job?
Hi guys, I just want to know if there's a specific NBU command/syntax to get the duration and speed of replication that lapse in Activity Monitor. I've tried the command "nbstlutil" but there's no output I needed. Hoping someone can help me thank you. :( # /usr/openv/netbackup/bin/admincmd/nbstlutil repllist -U -sincetime 2021/04/03 | more /find PROD-VMWPSAPDB01_1617382856 Image: Master Server : VMLPNBUINF01 Backup ID : PROD-VMWPSAPDB01_1617382856 Client : PROD-VMWPSAPDB01 Backup Time : 1617382856 (2021/04/03 01:00:56) Policy : VMWPSAPDB01_AIR_BACKUP Client Type : 40 Schedule Type : 0 Storage Lifecycle Policy : Monthly_HO_TO_DR Storage Lifecycle State : 3 (COMPLETE) Storage Lifecycle Is Inactive : false Time In Process : 1617410995 (2021/04/03 08:49:55) Data Classification ID : (none specified) Version Number : 1 OriginMasterServer : (none specified) OriginMasterServerID : {00000000-0000-0000-0000-000000000000} Import From Replica Time : 0 (0 secs) Required Expiration Date : 0 (0 secs) Created Date Time : 1617382856 (2021/04/03 01:00:56) Copy: Master Server : VMLPNBUINF01 Backup ID : PROD-VMWPSAPDB01_1617382856 Copy Number : 102 Copy Type : 3 (REPLICATE_TO_REMOTE_MASTER) Expire Time : 1648918856 (2022/04/03 01:00:56) Expire LC Time : 1648918856 (2022/04/03 01:00:56) Try To Keep Time : 1648918856 (2022/04/03 01:00:56) Residence : *Remote*Master*:Monthly_HO_TO_DR Copy State : 5 (COPYCOMPLETE) Job ID : 70850 Retention Type : 0 (FIXED) MPX State : 0 (false) RetryCount : 4 Last Retry Time : 1621258574 (2021/05/17 21:36:14) Source : 1 Destination ID : (none specified) Replica: : 0 DataFormat : 0 (DF_UNDEFINED) SLP Index : 2 Replication Target: Source Master Server: VMLPNBUINF01 Backup ID : PROD-VMWPSAPDB01_1617382856 Copy Number : 102 Target Machine : PMLRMSDPINF01 Target Info : PureDiskVolume Remote Master : (none specified)
AIR Import jobs not starting after reinstall NetBackup
Hello specialists, I have a question about not starting AIR Import jobs after we reinstalled 1 of the masterson a new server with newer Windows version and restored the Catalog. We run NetBackup 8.1.2 on W2016 Datacenter (on the old server it wasWindows 2012 R2 Datacenter), we write to Data Domains and replicate with AIR. Before shutting down 1 of the oldmasters we stopped Replication on both masters with "nbstlutil inactive -destination *Remote*Master*". After succesfull installation of NetBackup and restore of the Catalog (we kept the same hostname and IP for the new server) we activated replications again with "nbstlutil active -destination *Remote*Master*". After some 30 minutes replications started on both masters, imports started on the not-reinstalled master. However on the reinstalled master import jobs did not start for over 12 hour. I tried different solutions from this forum to no result. However: We have a small test environment with a 3rd and 4th master writing to the same Data Domains to completely different mtrees as the production environment. These test mtrees (both source and target)are of course not configured in the production environment. Now the trick: After configuring on the reinstalled master a Diskpool and STU on the test mtrees theimports began to run. So my problem has been solved but in a somewhat illogical way. Can this be explained? Kind regards, Peter
