Want to restore backup reside in Data Domain STU via FC network
We have AIR setup and SLP backups been replicated to target data domain STU From target data domain STU, where our SLP replicated backups resides and want to perform the restore via FC network. Taken call with EMC data domain vendor and configured FC traffic between SAN Media server(ABC) and Data Domain. After the configuration I can see in NB console new storage server DFC-DD01 has been added, before that we had IP based storage server(DD01) for AIR SLP replication and also in that we have added the SAN Media server(ABC). At present in NB console, when I open the disk pools I can see storage server as DD01. Now my queries are Can I add same SAN media server (ABC) in the new storage server DFC-DD01. Once I add, will NB get visibility on the existing disk pool for DD01 & DFC-DD01. If I do so, the configuration is like, same SAN media server(ABC) will be in both IP & FC based storage server. Then If I initiate the restore, which traffic will it use, either IP or FC?.NB Logs with file and it's size restored
Where I can find the detailed information of files and its size which I had restored. In User_ops logs I can see the files restored but not size of it. In a scenario we faving size mismatch of the backup and restored data whereas no error in the restore jobs detailed status.
Error message in sap oracle detail log.
Error message occurs in the detail log during sap backup. What should I check? 2019. 12. 27 오후 3:42:03 - Info nbjm (pid=13885) starting backup job (jobid=23683) for client bxddev, policy bxddev_SAP, schedule Default-Application-Backup 2019. 12. 27 오후 3:42:03 - Info nbjm (pid=13885) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=23683, request id:{FE1420F4-2873-11EA-87DC-C738CC064B28}) 2019. 12. 27 오후 3:42:03 - requesting resource stu_adv_hkpbma2 2019. 12. 27 오후 3:42:03 - requesting resource hkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019. 12. 27 오후 3:42:03 - requesting resource hkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019. 12. 27 오후 3:42:04 - granted resource hkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019. 12. 27 오후 3:42:04 - granted resource hkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019. 12. 27 오후 3:42:04 - granted resource MediaID=@aaaab;DiskVolume=/advanceddisk/dp1/advol;DiskPool=dp_adv_hkpbma2;Path=/advanceddisk/dp1/advol;StorageServer=hkpbma2;MediaServer=hkpbma2 2019. 12. 27 오후 3:42:04 - granted resource stu_adv_hkpbma2 2019. 12. 27 오후 3:42:04 - granted resource TRANSPORT 2019. 12. 27 오후 3:42:04 - estimated 0 kbytes needed 2019. 12. 27 오후 3:42:04 - Info nbjm (pid=13885) started backup (backupid=bxddev_1577428924) job for client bxddev, policy bxddev_SAP, schedule Default-Application-Backup on storage unit stu_adv_hkpbma2 2019. 12. 27 오후 3:42:04 - started process bpbrm (pid=301944) 2019. 12. 27 오후 3:42:05 - connecting 2019. 12. 27 오후 3:42:08 - connected; connect time: 0:00:00 2019. 12. 27 오후 3:42:09 - Info bpbrm (pid=301944) bxddev is the host to backup data from 2019. 12. 27 오후 3:42:09 - Info bpbrm (pid=301944) reading file list for client 2019. 12. 27 오후 3:42:10 - Info bpbrm (pid=301944) listening for client connection 2019. 12. 27 오후 3:42:11 - Opening Fibre Transport connection, Backup Id: bxddev_1577428924 2019. 12. 27 오후 3:42:12 - Info bpbrm (pid=301944) INF - Client read timeout = 3600 2019. 12. 27 오후 3:42:12 - Info bpbrm (pid=301944) accepted connection from client 2019. 12. 27 오후 3:42:12 - Info bpbrm (pid=301944) start bpbkar on client 2019. 12. 27 오후 3:42:12 - begin writing 2019. 12. 27 오후 3:42:13 - Info dbclient (pid=20932) Backup started 2019. 12. 27 오후 3:42:13 - Info dbclient (pid=20884) Backup started 2019. 12. 27 오후 3:42:13 - Info bpbrm (pid=301944) bptm pid: 301952 2019. 12. 27 오후 3:42:13 - Info bptm (pid=301952) start 2019. 12. 27 오후 3:42:14 - Info bptm (pid=301952) using 262144 data buffer size 2019. 12. 27 오후 3:42:14 - Info bptm (pid=301952) using 16 data buffers 2019. 12. 27 오후 3:42:14 - Info bptm (pid=301952) USING 262144 data buffer size for FT 2019. 12. 27 오후 3:42:15 - Info bptm (pid=301952) start backup 2019. 12. 27 오후 3:42:18 - Error bpbrm (pid=301944) from client bxddev: ERROR: V-3-20003: Cannot open /dev/sapvg01/lvol6: Permission denied 2019. 12. 27 오후 3:42:28 - end writing; write time: 0:00:16 2019. 12. 27 오후 3:42:30 - Info dbclient (pid=20884) bpbkar waited 133 times for empty buffer, delayed 149 times 2019. 12. 27 오후 3:42:30 - Info dbclient (pid=20884) done. status: 0 2019. 12. 27 오후 3:42:30 - Info bptm (pid=301952) waited for full buffer 1445 times, delayed 11337 times 2019. 12. 27 오후 3:42:32 - Info bptm (pid=301952) EXITING with status 0 <---------- 2019. 12. 27 오후 3:42:32 - Info bpbrm (pid=301944) validating image for client bxddev 2019. 12. 27 오후 3:42:32 - Info dbclient (pid=20884) done. status: 0: the requested operation was successfully completed the requested operation was successfully completed (0)NETBACKUP 8.1 certificate renewal
We are using NBU 8.1 with 800-900 linux clients and 500 Windows clients When I look at the certificates, A few hundreds will expire in 170-180 days. To be able to continue the backup, to extend the life of a certicicate, we generate a reissue token from the GUI, copy the authiorization code (manually, copy/paste doesn't work), connect on the client and execute "nbcertcmd -getCertificate -token -force". It works, but if we have a few hundreds systems to update, we need something that could be scripted and executed from one point. Is there a solution in 8.1 for this problem ? For technical reasons, we cannot upgrade to 8.2 (We backup OpenVMS systems with NBU and 8.1 is the latest version with a support for this OS).
Netbackup 5 or lower client binary
Hi, I am looking for NetBackup Version 5(or lower) client software for HP-UX 10.20 PA-RISC HP9000. Last supported Veritas Netbackup client version for HP-UX 10.20 operating system, was version 3.4 (3.4.1). But it appears that NBU client version 4.5 as well as 5.x are operational on HP-UX 10.20 clients. (But not supported from Veritas ) If anybody can share any of these version, it will we very helpful for me. Thanks in advance.
