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-Infonbjm(pid=13885)startingbackupjob(jobid=23683)forclientbxddev,policybxddev_SAP,scheduleDefault-Application-Backup 2019.12.27오후3:42:03-Infonbjm(pid=13885)requestingSTANDARD_RESOURCEresourcesfromRBforbackupjob(jobid=23683,requestid:{FE1420F4-2873-11EA-87DC-C738CC064B28}) 2019.12.27오후3:42:03-requestingresourcestu_adv_hkpbma2 2019.12.27오후3:42:03-requestingresourcehkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019.12.27오후3:42:03-requestingresourcehkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019.12.27오후3:42:04-grantedresourcehkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019.12.27오후3:42:04-grantedresourcehkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019.12.27오후3:42:04-grantedresourceMediaID=@aaaab;DiskVolume=/advanceddisk/dp1/advol;DiskPool=dp_adv_hkpbma2;Path=/advanceddisk/dp1/advol;StorageServer=hkpbma2;MediaServer=hkpbma2 2019.12.27오후3:42:04-grantedresourcestu_adv_hkpbma2 2019.12.27오후3:42:04-grantedresourceTRANSPORT 2019.12.27오후3:42:04-estimated0kbytesneeded 2019.12.27오후3:42:04-Infonbjm(pid=13885)startedbackup(backupid=bxddev_1577428924)jobforclientbxddev,policybxddev_SAP,scheduleDefault-Application-Backuponstorageunitstu_adv_hkpbma2 2019.12.27오후3:42:04-startedprocessbpbrm(pid=301944) 2019.12.27오후3:42:05-connecting 2019.12.27오후3:42:08-connected;connecttime:0:00:00 2019.12.27오후3:42:09-Infobpbrm(pid=301944)bxddevisthehosttobackupdatafrom 2019.12.27오후3:42:09-Infobpbrm(pid=301944)readingfilelistforclient 2019.12.27오후3:42:10-Infobpbrm(pid=301944)listeningforclientconnection 2019.12.27오후3:42:11-OpeningFibreTransportconnection,BackupId:bxddev_1577428924 2019.12.27오후3:42:12-Infobpbrm(pid=301944)INF-Clientreadtimeout=3600 2019.12.27오후3:42:12-Infobpbrm(pid=301944)acceptedconnectionfromclient 2019.12.27오후3:42:12-Infobpbrm(pid=301944)startbpbkaronclient 2019.12.27오후3:42:12-beginwriting 2019.12.27오후3:42:13-Infodbclient(pid=20932)Backupstarted 2019.12.27오후3:42:13-Infodbclient(pid=20884)Backupstarted 2019.12.27오후3:42:13-Infobpbrm(pid=301944)bptmpid:301952 2019.12.27오후3:42:13-Infobptm(pid=301952)start 2019.12.27오후3:42:14-Infobptm(pid=301952)using262144databuffersize 2019.12.27오후3:42:14-Infobptm(pid=301952)using16databuffers 2019.12.27오후3:42:14-Infobptm(pid=301952)USING262144databuffersizeforFT 2019.12.27오후3:42:15-Infobptm(pid=301952)startbackup 2019.12.27오후3:42:18-Errorbpbrm(pid=301944)fromclientbxddev:ERROR:V-3-20003:Cannotopen/dev/sapvg01/lvol6:Permissiondenied 2019.12.27오후3:42:28-endwriting;writetime:0:00:16 2019.12.27오후3:42:30-Infodbclient(pid=20884)bpbkarwaited133timesforemptybuffer,delayed149times 2019.12.27오후3:42:30-Infodbclient(pid=20884)done.status:0 2019.12.27오후3:42:30-Infobptm(pid=301952)waitedforfullbuffer1445times,delayed11337times 2019.12.27오후3:42:32-Infobptm(pid=301952)EXITINGwithstatus0<---------- 2019.12.27오후3:42:32-Infobpbrm(pid=301944)validatingimageforclientbxddev 2019.12.27오후3:42:32-Infodbclient(pid=20884)done.status:0:therequestedoperationwassuccessfullycompleted therequestedoperationwassuccessfullycompleted (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.
