Problems loading tape media into drive of library (NetBackup 8.x)
Hello everybody, we use NetBackup 8.x for restores of old tapes. This worked for a very long time. Today we needed to re-issue the certificate in order to login to the NetBackup Administration console. After this was fixed, we tried to restore one VMware virtual machine. The tape library firmware has been updated to a new version a couple of weeks ago, so we had to configure the updated tape library with the new firmware with the 'Configure Storage Devices'-wizard. The tape library with the old firmware had been removed from the infrastructure. Master and Media server are connected (it's the same machine). Under Devices the drive and the tape libary is ENABLED. Media server is active for Tape and Disk as well. Under Device Monitor the corresponding drive is not 'READY', it states No. So as soon as we try to restore a VMware virtual machine, the job is waiting for a pending request and it does not move on automatically. When we deny the request, the job is cancelled, otherwise it waits forever for the tape media to be loaded in the only available drive of the tape library. What can we do or how do we re-configure the infrastructure? Any advice? Thanks DiWiDiwi
How to migrate MSDP data to a new master server during NetBackup master server migration
Hello, I'd like to seek expert advice regarding my NetBackup migration plan. Due to the End of Support (EOS) for CentOS 7.9, I am planning to migrate to a new server running Rocky Linux 8.10. At the same time, I plan to install NetBackup 10.5 to maintain compatibility. Current Environment Master Server: CentOS 7.9 NetBackup Version: 10.1.1 Storage: MSDP (Local Disk) Target Environment Master Server: Rocky Linux 8.10 NetBackup Version: 10.5 Storage: MSDP (Local Disk) My goal is to fully migrate the NetBackup environment, including the NetBackup catalog and MSDP data, from the existing master server to the new master server. Migration Procedure (as I understand it) I expect the migration process to follow these steps: 1. Transfer the catalog backup from the existing master server to the new master server. 2. Shut down the existing master server. 3. Configure the new master server with the same settings as the existing master server. 4. Copy the MSDP data stored on the existing master server (local disk) to the new master server. 5. Perform a catalog recovery on the new master server using the transferred catalog backup. 6. Verify communication with the backup clients. I would like to confirm whether this procedure is correct. Additionally, I am unsure which feature or method should be used to replicate or migrate the MSDP data from the existing server to the new server. Could you please provide guidance on the recommended approach for migrating MSDP data? Please advise.
How can I find out the actual size of a backup after compression and deduplication ?
Hi everyone, I am using Veritas NetBackup version 11 to backup Oracle databases and all virtual machines in a quite big system. The using experience is nice and smooth, but my boss want me to show him the exact actual size of a backup after being backed up successfully. This means the actual size of a backup after being deduplicated. How can I find this statistics ? The Activity monitor in NetBackup Web UI shows the logical size and the deduplication ratio of each job ID, but it is suffering to manually sum them up =))) So, I really want to know that: Are there any faster ways to get the actual size of a backup after being deduplicated ? And if the only way to do that is manually calculating, what is the correct formula when I know the logical size and the deduplication ratio ?
NetBackup, client does not present in Cert Mgt, but shows connected in client properties
Despite the client being not present in Cert Mgt, it shows connected in client properties, and those clients backups have been operating lately. Only errors being the 196-backup window closed error. And most of the client backups ran just 3 days ago.
Backup of SAP HANA with multitenant database container with netbackup.
Hi, I have one query? We have netbackup 7.7.2 and SAP HANA with multitenant database container. For one instance we have to do following configurations on SAP HANA studio: Create hdbbackint soft link from /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint to /usr/openv/NetBackup/bin/hdbbackint_script for every database instance. The parameter file (initSAP.utl) must be specified for data in the SAP HANA database instance configuration. To specify the parameter file, go to Instance->Configuration-> global.ini > data_backup_parameter_file. The parameter file (initSAP.utl) must be specified for logs in the SAP HANA database instance configuration. To specify backup using the parameter file, go to Instance->Configuration->global.ini-> log_backup_parameter_file. To specify backup using the backint file, go to Instance->Configuration->global.ini-> log_backup_using_backint->SYSTEM = true. My problem is that how to configure backup for multitenant database container (For multiple Instance ) We have cluster "Dev" with multitenant database container having 3 instance "Dev" "Quality" and "SystemDB" The problem is that DBA is telling that create hdbbackint soft link from /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint to /usr/openv/NetBackup/bin/hdbbackint_script . DBA inform us that,It is not possible due to Database instances in SAP HANA database will be in hidden mode. So we cannot create the links. Requesting you to help me in this. Server Details: Master Server. Client/Master = Master NetBackup Client Platform = PC-x64, WindowsXP NetBackup Client Protocol Level = 7.7.2 Product = NetBackup Version Name = 7.7 Version Number = 770000 NetBackup Installation Path = D:\Program Files\Veritas\NetBackup\bin Client OS/Release = Windows2008 6 SAP HANA Client . Client/Master = Client of IRBIDCQCSER001.irb.local NetBackup Client Platform = Linux, SuSE3.0.76 NetBackup Client Protocol Level = 7.7.2 Product = NetBackup Version Name = 7.7 Version Number = 770000 NetBackup Installation Path = /usr/openv/netbackup/bin Client OS/Release = Linux 3.0.101-0.47.67-default
Import SLP is extending the retention with "Target retention"
Hi, so a quick question: When replicating from a legacy NBU Domain, the images that were created with 5 years retention and have only 1 year left are getting a retention refresh when being created with "target retention" For example: Copy 1 Created at 01/12/2020 Expires at 01/12/2025 Imported Target Retention Copy Created at 15/08/2025 Expires at 15/08/2030 Is this expected? Should 'Target Retention' reapply the original retention of the image basically resulting in a refresh?
Restoring Using a Different Media Server
Hello Everyone, I would like some assistance on how to perform a restoration using only one server that acts as both the master and media server. I currently have two master servers: one for PROD and one for DR. I plan to decommission the PROD master server along with all its connected media servers. I also plan to decommission the media servers connected to the DR master server and use the DR master as both the master and media server. My main concern is the restoration process. How can I redirect restorations from the old media servers (used for old backups) to the new combined master/media server, and use it for restoring both old and new backups? DR MASTER SERVER INFO: NBU Version: 10.3.0.1 OS: Microsoft Windows Server 2019 Standard Thank you.