Can't login to the netbackup WebUI
Cannot access the netbackup WebUI, using 8.1.2. The login page comes up asking for user name and password. I either get an "you are not authorized" message or "Enter a valid user name or password" message depending on using an admin or user account. I belive the nbsecadmin account is used to set this up? there is no documentaion on the nbsecadmin credentials here so the password is not known. the default appliance PW doesn't work so I assume someone at install set it. I'm thinking of resetting this nbsecadmin account PW but unsure of the implications. I believe but could be wrong that this account is strickly for the WebUI?
NetBackup PowerShell Cmdlets how to use it
Hi all, on the official Veritas page on the GitHub there is a section for NetBackup PowerShell Cmdlets (https://github.com/VeritasOS/nb-powershell). Since I am not so strong in Powershell scripting I would like to ask you how to compile these scripts. I was able to list Cmdlets - see below. However, I do not know how to make these cmdlets working (e.g. Get-NBAlert). Should I download e.g. GetAlert.cs and then somehow compile it? Any help much appreciated! PS > Get-Command -Module NBCmdlets CommandType Name ModuleName ----------- ---- ---------- Cmdlet Add-NBRecoverVMWareInstantAccessMount NBCmdlets Cmdlet Get-AppDetails NBCmdlets Cmdlet Get-NBAccessPermissions NBCmdlets Cmdlet Get-NBAccessRoles NBCmdlets Cmdlet Get-NBAccessRules NBCmdlets Cmdlet Get-NBAlert NBCmdlet .....
error occurred during initialization, check configuration file (103) in lotus notes client servers
Would like also to seek assistance in error encountered from two new notes server backup, please see logs below. We encounter the error on 2 lotus notes server when we change the policy type from windows to lotus notes. lotus notes OS: Windows server 2016 02/18/2019 15:23:19 - Info nbjm (pid=17552) starting backup job (jobid=992276) for client SW00314531, policy PROD_SW00314531_WDB, schedule Weekly 02/18/2019 15:23:19 - Info nbjm (pid=17552) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=992276, request id:{2F6BAB92-3B12-409A-9FDE-D311935566E8}) 02/18/2019 15:23:19 - requesting resource bdowcbs10_stu 02/18/2019 15:23:19 - requesting resource bdowcbs07.NBU_CLIENT.MAXJOBS.SW00314531 02/18/2019 15:23:19 - requesting resource bdowcbs07.NBU_POLICY.MAXJOBS.PROD_SW00314531_WDB 02/18/2019 15:23:19 - granted resource bdowcbs07.NBU_CLIENT.MAXJOBS.SW00314531 02/18/2019 15:23:19 - granted resource bdowcbs07.NBU_POLICY.MAXJOBS.PROD_SW00314531_WDB 02/18/2019 15:23:19 - granted resource MediaID=@aaaaf;DiskVolume=PureDiskVolume;DiskPool=bdowcbs10_dp;Path=PureDiskVolume;StorageServer=bdowcbs10;MediaServer=bdowcbs10 02/18/2019 15:23:19 - granted resource bdowcbs10_stu 02/18/2019 15:23:20 - estimated 0 kbytes needed 02/18/2019 15:23:20 - Info nbjm (pid=17552) started backup (backupid=SW00314531_1550474599) job for client SW00314531, policy PROD_SW00314531_WDB, schedule Weekly on storage unit bdowcbs10_stu 02/18/2019 15:23:22 - Info bpbrm (pid=9760) SW00314531 is the host to backup data from 02/18/2019 15:23:22 - Info bpbrm (pid=9760) reading file list for client 02/18/2019 15:23:22 - started process bpbrm (pid=9760) 02/18/2019 15:23:23 - connecting 02/18/2019 15:23:24 - Info bpbrm (pid=9760) starting bpbkar32 on client 02/18/2019 15:23:24 - Info bpbkar32 (pid=19728) Backup started 02/18/2019 15:23:24 - Info bpbkar32 (pid=19728) change time comparison:<disabled> 02/18/2019 15:23:24 - Info bpbkar32 (pid=19728) archive bit processing:<enabled> 02/18/2019 15:23:24 - Info bptm (pid=15424) start 02/18/2019 15:23:24 - Info bptm (pid=15424) using 262144 data buffer size 02/18/2019 15:23:24 - Info bptm (pid=15424) setting receive network buffer to 1049600 bytes 02/18/2019 15:23:24 - Info bptm (pid=15424) using 30 data buffers 02/18/2019 15:23:24 - connected; connect time: 0:00:00 02/18/2019 15:23:27 - Info bptm (pid=15424) start backup 02/18/2019 15:23:30 - Info bptm (pid=15424) backup child process is pid 5028.16380 02/18/2019 15:23:30 - Info bptm (pid=5028) start 02/18/2019 15:23:30 - Error bptm (pid=5028) socket operation failed - 10054 (at ../child.c.1276) 02/18/2019 15:23:30 - Error bptm (pid=5028) unable to perform read from client socket, connection may have been broken 02/18/2019 15:23:30 - begin writing 02/18/2019 15:23:34 - Info bdowcbs10 (pid=15424) StorageServer=PureDisk:bdowcbs10; Report=PDDO Stats for (bdowcbs10): scanned: 3 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled 02/18/2019 15:23:35 - Error bpbrm (pid=9760) could not send server status message 02/18/2019 15:23:35 - Info bpbkar32 (pid=19728) done. status: 103: error occurred during initialization, check configuration file 02/18/2019 15:23:35 - end writing; write time: 0:00:05 error occurred during initialization, check configuration file (103)
New Exchange 2019 features and new headaches
FYI: New 8.2 environment backing up Ip-Less DAG on new Exchange 2019 running on Windows 2019 Core Servers. Backup is working ok, restores not so much. We suspect that a new feature in Exchange 2019 causes the restore to fail at the commit/mount database stage. In Exchange 2019 they have implemented a SSD cache database, for quicker searches etc, that are referenced by all mail databases. When you restore an entire database, eg EXDB01, to a recovery database, eg RDB01 , the recovery database have no reference to the cache and mounting the database fails. Progress log filename : N:\Program Files\Veritas\NetBackup\Logs\user_ops\nbadmin\logs\jbp9FAC.tmp.log Restore Job Id=145846 Restore started 08/14/2019 10:33:14 10:33:14 (145846.xxx) Found (4 608) files in (1) images for Restore Job ID 145846.xxx 10:33:25 (145847.xxx) Found (4 608) files in (1) images for Restore Job ID 145847.xxx 10:33:33 (145847.xxx) Searched ( 10) files of (4 608) files for Restore Job ID 145847.xxx 10:33:33 (145847.001) Restoring from copy 1 of image created 2019-08-14 10:27:26 from policy Silver_Exchange2019_DAG 10:33:53 (145847.001) INF - Beginning restore from server xstobup01.ref.xxx.xx to client XSTOEX41.REF.XXX.XX (client_hostname XSTOEX41.REF.XXX.XX). 10:33:55 (145847.001) TAR - Microsoft Exchange Database Availability Groups:\ 10:33:55 (145847.001) TAR - Microsoft Exchange Database Availability Groups:\xstoexdag41\ 10:33:55 (145847.001) TAR - Microsoft Exchange Database Availability Groups:\xstoexdag41\Microsoft Information Store\ 10:33:55 (145847.001) TAR - Microsoft Exchange Database Availability Groups:\xstoexdag41\Microsoft Information Store\EXDB01\ 10:33:55 (145847.001) MNR - The file was renamed to the following: 10:33:55 (145847.001) UTF - Microsoft Information Store:\RDB01\ 10:34:22 (145847.001) TAR - Microsoft Exchange Database Availability Groups:\xstoexdag41\Microsoft Information Store\EXDB01\Database 10:34:23 (145847.001) MNR - The file was renamed to the following: 10:34:23 (145847.001) UTF - Microsoft Information Store:\RDB01\Database 10:34:26 (145847.001) TAR - Microsoft Exchange Database Availability Groups:\xstoexdag41\Microsoft Information Store\EXDB01\Logs_1565771088 10:34:27 (145847.001) MNR - The file was renamed to the following: 10:34:27 (145847.001) UTF - Microsoft Information Store:\RDB01\Logs_1565771088 10:34:36 (145847.001) INF - There are no jobs remaining for this restore request. Exchange database recovery will be performed. 10:34:37 (145847.001) INF - After restoring a Microsoft Exchange LCR, CCR, or DAG database, you must use the Exchange Management Shell to resume replication. 10:35:01 (145847.001) WRN - MountDatabase failed with error(0x0) for machine xstoexdag41, storage group RDB01, database RDB01 10:35:01 (145847.001) WRN - Exchange database recovery may have failed. Please check the event log for further details. 10:35:01 (145847.001) ERR - An Exchange restore error was detected. You may need to manually mount the Database stores to successfully finish the restore. 10:35:01 (145847.001) INF - TAR EXITING WITH STATUS = 5 10:35:01 (145847.001) INF - TAR RESTORED 6 OF 6 FILES SUCCESSFULLY 10:35:01 (145847.001) INF - TAR KEPT 0 EXISTING FILES 10:35:01 (145847.001) INF - TAR PARTIALLY RESTORED 0 FILES 10:35:01 (145847.001) Status of restore from copy 1 of image created 2019-08-14 10:27:26 = tar did not find all the files to be restored 10:35:01 INF - Server status = 5 10:35:02 (145846.xxx) INF - Status = the restore failed to recover the requested files. 10:35:02 INF - Server status = 2810 10:35:02 (145847.xxx) INF - Status = MS-Exchange-Server policy restore error. FROM EXCHANGE SERVERS ERROR LOG: msexchangerepl (5708,U,98,15.02.0330.008) RDB01\XSTOEX41: Database recovery failed with error -1216 because it encountered references to a database, C:\ExchangeMetaCacheDbs\EXDB01\EXDB01.mcdb\EXDB01-mcdb.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. I have just now started a case with Veritas support.
Netbackup Appliance Error
Hello, Can someone help me ? I need help..suddenly I have issued with our customer NBU appliance version 3.0/netbackup 8.0. When I opened the Netbackup Java Console for the Appliance, i see these options greyed out 1) Configure Disk Storage Servers 2) Configure Cloud Storage Servers 3) Configure Disk Pool When I click on the Policy, I got the below error: NBARSMgmt_i::queryApplicationMetadata: Error detected during execution of query. Please check the logs for more details (2) (Status 2) When I click on Activity Monitor, i get this error message : The Activity Monitor failed because of Connection to bpjob deamon on server failed. For more details, refer to the log files When i click on Device Monitor, I get the below message : Device Monitor, Database system error(220) Database server is down. check for low disk space (Don't know why i see this message, because the NBU appliance is very free : 300 GB used out of 13000 GB When i click on the Login Activity shortcut, i see System Error 130. This appliance we have stopped all the backup but customer is keeping it for restoration purposes. Attached together with this is the nbu processes currently running, issued via command line. I also received email notification on this Your appliance has encountered the following error(s): • The MSDP is configured, however the system failed to retrieve MSDP getmode or tlog status information. Contact Veritas Technical Support for more assistance. o Time of event: 2021-01-27 18:41:32 (+08:00) o UMI Event code: V-475-109-1000 o Component Type: MSDP o Component: MSDP Partition o Status: Not Available o State: CRITICAL o Additional information about this error is available at following link: V-475-109-1000
Need help on configuring Optimized Duplication between 2 Quantum DXi
Need help on configuring Optimized Duplication between 2 Quantum DXi I am having solaris master server running in 7.7.3 version, we are having 3 remote sites which are having local backups happening to there own local Dxi boxes (3 Dxi boxes) - each of 5 TB capcity - model Dxi4700 we have one main site where we has around 180 TB quantum Dxi box - model DXi6802 Our requirement is to do a optimized duplciation from the remote site DXi box to main site DXi box. I had established the connectivity and firewall rules were added for the respective ports and DXi replication configuraitons were done to enabled the opt dup. SLPs are also created with source backup --> remote (source) site DXi STU and Duplication --> targe site Dxi STU Now when i run backup and monitored the Duplication job it was giving below errors: errors are bolded below: Can you please help me on this to fix this issue? Also it would be great if you share me the steps to configure opt dup from one Dxi to another Dxi. Detailed status from the activity monitor: 04/03/2017 21:32:26 - requesting resource LCM_stu_ds03ss01_remote_dup 04/03/2017 21:33:23 - granted resource LCM_stu_ds03ss01_remote_dup 04/03/2017 21:33:23 - started process RUNCMD (pid=2321) 04/03/2017 21:33:24 - begin Duplicate 04/03/2017 21:33:24 - ended process 0 (pid=2321) 04/03/2017 21:33:24 - requesting resource stu_ds03ss01_remote_dup 04/03/2017 21:33:24 - reserving resource aaaa_ 04/03/2017 21:34:25 - resource aaaa_ reserved 04/03/2017 21:34:25 - granted resource MediaID=@aaaaK;DiskVolume=_PhysicalLSU;DiskPool=dp_xrxsenbuds03ss01;Path=_PhysicalLSU;StorageServer=xrxsenbuds03ss01_10.173.133.25;MediaServer=xrxsenbumed04 04/03/2017 21:34:25 - granted resource stu_ds03ss01_remote_dup 04/03/2017 21:34:25 - requesting resource aaaa_ 04/03/2017 21:34:26 - Info Duplicate (pid=2321) Initiating optimized duplication from aaaa_ to @aaaaK 04/03/2017 21:34:26 - Info bpduplicate (pid=2321) Suspend window close behavior is not supported for optimized duplications 04/03/2017 21:34:26 - Info bpduplicate (pid=2321) window close behavior: Continue processing the current image 04/03/2017 21:34:26 - granted resource MediaID=@aaaa_;DiskVolume=_PhysicalLSU;DiskPool=dp_disk_Secaucus;Path=_PhysicalLSU;StorageServer=SS-Secaucus-DXi_10.159.72.90;MediaServer=xrxsenbumed04 04/03/2017 21:34:27 - Info bpdm (pid=62088) started 04/03/2017 21:34:27 - started process bpdm (pid=62088) 04/03/2017 21:34:28 - Info bpdm (pid=62088) requesting nbjm for media 04/03/2017 21:34:31 - begin writing 04/03/2017 21:34:31 - end writing; write time: 0:00:00 04/03/2017 21:50:35 - Critical bpdm (pid=62088) sts_close_handle failed: 2060022 software error 04/03/2017 21:50:45 - Critical bpdm (pid=62088) sts_close_handle failed: 2060014 operation aborted 04/03/2017 22:06:43 - Critical bpdm (pid=62088) sts_close_handle failed: 2060022 software error 04/03/2017 22:06:43 - Warning bpdm (pid=62088) source image close failed: error 2060022: software error 04/03/2017 22:06:43 - Critical bpdm (pid=62088) sts_close_handle failed: 2060014 operation aborted 04/03/2017 22:06:43 - Critical bpdm (pid=62088) destination image close failed: error 2060014: operation aborted 04/03/2017 22:07:32 - Error bpduplicate (pid=2321) host xrxsenbumed04 backup id servus-newjers3.nam.gad.schneider-electric.com_1491260523 optimized duplication failed, media write error (84). 04/03/2017 22:07:32 - Error bpduplicate (pid=2321) Duplicate of backupid servus-newjers3.nam.gad.schneider-electric.com_1491260523 failed, media write error (84). 04/03/2017 22:07:32 - requesting resource aaaa_ 04/03/2017 22:07:34 - Info bpdm (pid=73803) started 04/03/2017 22:07:34 - started process bpdm (pid=73803) 04/03/2017 22:07:34 - granted resource MediaID=@aaaa_;DiskVolume=_PhysicalLSU;DiskPool=dp_disk_Secaucus;Path=_PhysicalLSU;StorageServer=SS-Secaucus-DXi_10.159.72.90;MediaServer=xrxsenbumed04 04/03/2017 22:07:36 - Info bpdm (pid=73803) requesting nbjm for media 04/03/2017 22:07:40 - begin writing 04/03/2017 22:07:40 - end writing; write time: 0:00:00 04/03/2017 22:23:31 - Critical bpdm (pid=73803) sts_close_handle failed: 2060022 software error 04/03/2017 22:23:41 - Critical bpdm (pid=73803) sts_close_handle failed: 2060014 operation aborted 04/03/2017 22:23:43 - begin writing 04/03/2017 22:23:43 - end writing; write time: 0:00:00 04/03/2017 22:39:32 - Critical bpdm (pid=73803) sts_close_handle failed: 2060022 software error 04/03/2017 22:39:42 - Critical bpdm (pid=73803) sts_close_handle failed: 2060014 operation aborted 04/03/2017 22:55:33 - Critical bpdm (pid=73803) sts_close_handle failed: 2060022 software error 04/03/2017 22:55:33 - Warning bpdm (pid=73803) source image close failed: error 2060022: software error 04/03/2017 22:55:33 - Critical bpdm (pid=73803) sts_close_handle failed: 2060014 operation aborted 04/03/2017 22:55:33 - Critical bpdm (pid=73803) destination image close failed: error 2060014: operation aborted 04/03/2017 22:55:34 - Error bpduplicate (pid=2321) host xrxsenbumed04 backup id servus-newjers3.nam.gad.schneider-electric.com_1491260571 optimized duplication failed, media write error (84). 04/03/2017 22:55:34 - Error bpduplicate (pid=2321) Duplicate of backupid servus-newjers3.nam.gad.schneider-electric.com_1491260571 failed, media write error (84). 04/03/2017 22:55:34 - requesting resource aaaa_ 04/03/2017 22:55:35 - Info bpdm (pid=92140) started 04/03/2017 22:55:35 - started process bpdm (pid=92140) 04/03/2017 22:55:35 - granted resource MediaID=@aaaa_;DiskVolume=_PhysicalLSU;DiskPool=dp_disk_Secaucus;Path=_PhysicalLSU;StorageServer=SS-Secaucus-DXi_10.159.72.90;MediaServer=xrxsenbumed04 04/03/2017 22:55:36 - Info bpdm (pid=92140) requesting nbjm for media 04/03/2017 22:55:39 - begin writing 04/03/2017 22:55:39 - end writing; write time: 0:00:00 04/03/2017 23:11:41 - Critical bpdm (pid=92140) sts_close_handle failed: 2060022 software error 04/03/2017 23:11:52 - Critical bpdm (pid=92140) sts_close_handle failed: 2060014 operation aborted 04/03/2017 23:28:24 - Critical bpdm (pid=92140) sts_close_handle failed: 2060022 software error 04/03/2017 23:28:24 - Warning bpdm (pid=92140) source image close failed: error 2060022: software error 04/03/2017 23:28:24 - Critical bpdm (pid=92140) sts_close_handle failed: 2060014 operation aborted 04/03/2017 23:28:24 - Critical bpdm (pid=92140) destination image close failed: error 2060014: operation aborted 04/03/2017 23:29:04 - Error bpduplicate (pid=2321) host xrxsenbumed04 backup id servus-newjers3.nam.gad.schneider-electric.com_1491260572 optimized duplication failed, media write error (84). 04/03/2017 23:29:04 - Error bpduplicate (pid=2321) Duplicate of backupid servus-newjers3.nam.gad.schneider-electric.com_1491260572 failed, media write error (84). 04/03/2017 23:29:04 - Error bpduplicate (pid=2321) Status = no images were successfully processed. 04/03/2017 23:29:04 - Error bpduplicate (pid=2321) Continuing with normal duplication. 04/03/2017 23:29:04 - requesting resource stu_ds03ss01_remote_dup 04/03/2017 23:29:04 - requesting resource aaaa_ 04/03/2017 23:29:04 - reserving resource aaaa_ 04/03/2017 23:30:16 - Info bpduplicate (pid=2321) window close behavior: Suspend 04/03/2017 23:30:16 - resource aaaa_ reserved 04/03/2017 23:30:16 - granted resource MediaID=@aaaaK;DiskVolume=_PhysicalLSU;DiskPool=dp_xrxsenbuds03ss01;Path=_PhysicalLSU;StorageServer=xrxsenbuds03ss01_10.173.133.25;MediaServer=xrxsenbumed04 04/03/2017 23:30:16 - granted resource stu_ds03ss01_remote_dup 04/03/2017 23:30:16 - granted resource MediaID=@aaaa_;DiskVolume=_PhysicalLSU;DiskPool=dp_disk_Secaucus;Path=_PhysicalLSU;StorageServer=SS-Secaucus-DXi_10.159.72.90;MediaServer=xrxsenbumstr01 04/03/2017 23:30:17 - Info bptm (pid=104851) start 04/03/2017 23:30:17 - started process bptm (pid=104851) 04/03/2017 23:30:17 - Info bptm (pid=104851) using 131072 data buffer size 04/03/2017 23:30:17 - Info bptm (pid=104851) setting receive network buffer to 131072 bytes 04/03/2017 23:30:17 - Info bptm (pid=104851) using 128 data buffers 04/03/2017 23:30:18 - Info bptm (pid=104851) start backup 04/03/2017 23:30:20 - Info bpdm (pid=15926) started 04/03/2017 23:30:20 - started process bpdm (pid=15926) 04/03/2017 23:30:20 - Info bpdm (pid=15926) reading backup image 04/03/2017 23:30:20 - Info bptm (pid=104851) setting receive network buffer to 131072 bytes 04/03/2017 23:30:20 - Info bptm (pid=104851) backup child process is pid 104871 04/03/2017 23:30:21 - Info bpdm (pid=15926) using 128 data buffers 04/03/2017 23:30:21 - Info bpdm (pid=15926) spawning a child process 04/03/2017 23:30:21 - Info bpbrm (pid=15926) child pid: 15943 04/03/2017 23:30:21 - Info bpdm (pid=15926) requesting nbjm for media 04/03/2017 23:30:24 - begin reading 04/03/2017 23:30:38 - Info bptm (pid=104851) waited for full buffer 498 times, delayed 1065 times 04/03/2017 23:30:38 - end reading; read time: 0:00:14 04/03/2017 23:30:38 - Info bpdm (pid=15926) completed reading backup image 04/03/2017 23:30:52 - Info bptm (pid=104851) setting receive network buffer to 131072 bytes 04/03/2017 23:30:52 - Info bptm (pid=104851) backup child process is pid 104959 04/03/2017 23:30:53 - Info bpdm (pid=15926) using 128 data buffers 04/03/2017 23:30:53 - Info bpdm (pid=15926) spawning a child process 04/03/2017 23:30:53 - Info bpbrm (pid=15926) child pid: 16337 04/03/2017 23:30:53 - begin reading 04/03/2017 23:30:54 - end reading; read time: 0:00:01 04/03/2017 23:30:54 - begin reading 04/03/2017 23:30:55 - Info bptm (pid=104851) waited for full buffer 25 times, delayed 182 times 04/03/2017 23:30:55 - end reading; read time: 0:00:01 04/03/2017 23:30:55 - Info bpdm (pid=15926) completed reading backup image 04/03/2017 23:31:08 - Info bptm (pid=104851) setting receive network buffer to 131072 bytes 04/03/2017 23:31:08 - Info bptm (pid=104851) backup child process is pid 105280 04/03/2017 23:31:08 - Info bpdm (pid=15926) using 128 data buffers 04/03/2017 23:31:08 - Info bpdm (pid=15926) spawning a child process 04/03/2017 23:31:08 - Info bpbrm (pid=15926) child pid: 16528 04/03/2017 23:31:08 - begin reading 04/03/2017 23:31:58 - Info bptm (pid=104851) waited for full buffer 1120 times, delayed 3055 times 04/03/2017 23:31:58 - end reading; read time: 0:00:50 04/03/2017 23:31:58 - Info bpdm (pid=15926) completed reading backup image 04/03/2017 23:31:58 - Info bpdm (pid=15926) EXITING with status 0 04/03/2017 23:32:17 - Info bptm (pid=104851) EXITING with status 0 <---------- 04/03/2017 23:32:17 - end Duplicate; elapsed time 1:58:53 The requested operation was partially successful (1)