MSDP POOL IS DOWN
SUMMARY We reinstall the Netbackup after a disaster. recover the catalog. However the MSDP pool is showing down. C:\Program Files\Veritas\NetBackup\bin\admincmd>nbdevquery -listdv -stype PureDisk -dp MSDP-POOL -U Disk Pool Name : MSDP-POOL Disk Type : PureDisk Disk Volume Name : PureDiskVolume Disk Media ID : @aaaam Total Capacity (GB) : 3575.86 Free Space (GB) : 1167.54 Use% : 67 Status : DOWN Flag : ReadOnWrite Flag : AdminUp Flag : InternalDown Flag : ReplicationSource Flag : ReplicationTarget Num Read Mounts : 0 Num Write Mounts : 1 Cur Read Streams : 0 Cur Write Streams : 0 Num Repl Sources : 1 Num Repl Targets : 4 Replication Source : netbackup-me.contoso.com:PureDiskVolume Replication Target : tps-bkp.contoso.com:PureDiskVolume Replication Target : tps-bkp.contoso.com:PureDiskVolume Replication Target : netbackup-me.contoso.com:PureDiskVolume Replication Target : netbackup-dr.contoso.com:PureDiskVolume We then run the below command, which UP the STATUS for few seconds and went again down. C:\Program Files\Veritas\NetBackup\bin\admincmd>nbdevconfig -changestate -stype PureDisk -dp MSDP-POOL -dv PureDiskVolume -state RESET successfully changed the state of disk volume I notice that the path is not there for MSDP pool. Below snap for reference.
Shadow copy component backup failing with error code 13
Performed a multi-stream backup and it indicated shadow copy component failed with file read failed (error code 13). Rest of the drives able to backup. Is it possible to delete the shadow copy component in the client itself or there is a solution to rectify this issue? Thanks.
how to configure alerts in opscenter for queued jobs
Hello everybody! sporadically we have a problem with a SAP log backups filling the queue on a dedicated netbackup domain. I am looking for information about configuring an alert in opscenter to monitor the number of queued jobs and send an email if that number is more then a configured value. I did not find something relevant in the opscenter admin guide so I hope that somebody having experience with similar alert would step in and share. thank you in advance!
Backup Admin died. Need to know how to gather useful information for support.
We have 2 Backup systems running. a 9.1.0 and a 8.3.0 systems. The 8.3.0 was backing up some of our legacy Unix server using clients 7.0 for most of them. We cannot login to the 8.3 system to see if the 7.0 clients will work on the 9.1.0 server (where we want to go). The 8.3 system cannot login to the interface due to error unable to login status 537 connection to the netbackup database was not successful (although the service is running, and yes, we tried to restart the service). 1) how to transfer the profiles (or a profile) from the 8.3.0 system to the 9.1? 2) how to resize the tables if I cannot login to the GUI interface on the 8.3.0 system (plenty of disk space available, like 2.5TB) https://www.veritas.com/support/en_US/article.100051777 https://www.veritas.com/support/en_US/article.100051777 Also, when we get this running, what do we need to gather to have record of for better support when needed?
Netbackup Database Extension SQL GUI
Hi, I've a failover cluster composed by two node, and on each phisycal server there is a sql instance. Server A > Instance1 ServerB > Instance2 If i open the Netbackup SQL gui on server A there is this situation: Instance1 > i see databases and on right pane i see db "unavailable" Instance2 > it's ok, i see db. If i open the Netbackup SQL gui on server B there is this situation: Instance1 > it's ok Instance2 > it's ok On Set SQL server connection properties, at Host menu, when i click on "Browser for more host" where it search for host? Please someone may help on this? Thanks and Regards
Full server Restore Fails
I have a Production server (HP ProLiant DL360 G9, RAID 50, 2.1TB SAS, Windows Server 2016 Standard, Sql Server 2017 Standard) and I try to use SDR to restore this to another Backup Server (HP ProLiant DL360 G9, RAID 50, 3.9TB SAS), My backup medium is a Quantum LTO-4 tape drive attached to the production server. I have ensured that my backup has the Simplified Disaster Recovery status and downloaded the SDR disc from the "Configuration and Settings > Create Disaster Recovery Disc" menu, When I use the disc, it connects to my network, finds the backup exec server, identifies the SDR backup and then begins the restore smoothly without issue, When the restore finishes and I go to reboot the Restored server, it gets through the UEFI BIOS stage and then shows "No bootable device found", I have tried the restore twice, once allowing the software to configure the storage leaving roughly 1.8TB unconfigured and once reconfiguring the storage manually to make use of the whole disk. On further inspection using the SDR disc and DiskPart I find that the drives are not set as bootable and the boot and system sectors do not show as boot or system as they do in diskpart on the production server. When booting with a Windows Server 2016 disc and attempting BOOTREC /FixMBR, /FixBoot and /RebuildBCD nothing happens and /RebuildBCD shows "Operating systems found:0" I have attached the SDR logs from the restore of the server and some images of the not bootable and diskpart. I've updated the ADK to the right version, Updated backup exec to version 22.2 and made a backup and sdr disc from 22.2, tried with a different USB and nothing seems to work, I have been on case with Veritas support since 29th February 2024 and they just keep asking me if the SDR disc boots and consistently trying to downgrade the case severity (I now realise after 12 years that backup exec wont restore my servers quite scary for me). I once had similar issues with the support and found someone who could help in the forums, so hoping that lightning strikes twice.
