Restore files from backupid on other client's filesystem
Hi all, i would try a restore files from a client to another, but i presume to have only backup-id information for client's backup. The files on backup-id should be restored togheter on a dedicated filesystem on another client. I thought with bpflist -backupid "name" to obtain the files name and then insert on file's list and restore with bprestore command, but i receive "no entity was found" output and if i try bpimagelist with same backu-id, it's present. There is an option to restore from backup-id directly? for redirect many files on a filesystem, should i compile a rename file to redirect? Any idea? Thanks and RegardsSolved1.4KViews0likes2CommentsWant 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?.800Views0likes1CommentChange expiration date to all backups image in catalog to infinite
Hi All, I have a requirement to change expiration date for all backup image in catalog to infinite. I aware by backup ID, Media ID or client name we can do the changes but i want to have a single command that change exp date to infinite of all backup images in the catalog. Before I used bpexpdate -recalculate -client clientname -d infinity -force, here i want to know this command could have changed the expiration date to infinite for all backup images of the client specified or not ?. Most of images we have in disk storage i.e on DD. If there a command to change all images to infinite in DD by specifiying the storage unit name or diskpool ..etc also would be helpful. Also want to know the different between image and media expiration.Solved4.3KViews0likes10CommentsSAN Media server redirected Restore
We have a HP UX client where we installed SAN media server on it. Our intention is to perform restore via SAN network to the clientwhere we installed and configured as SAN media server. But backup which we going to restore was taken by different media server and the backup images are reside in our Data Domain storage unit. We have done the zoning between Data Domain and SAN Media server as well. Since the backup was taken by another media server If I initiate the restore, from which media server will the restore happens. What I suppose to do if i want my SAN media server to perform the restore, so that data will get transfereed via SAN.Solved736Views0likes1CommentNB 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.804Views0likes1CommentError 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)995Views0likes1CommentNETBACKUP 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).5.1KViews0likes3CommentsNetbackup 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.1.7KViews0likes5CommentsRestore from tape fails with 'TAR Read Error' in Backup Exec 6.5
I am not able to restore from the tape.I was searching for solutionand checked most of the settings andthats seemsfine here are the failed log details. 15:28:26 10/1/2010: Restore Started 15:28:28 (62.xxx) Restore job id 62 will require 1 image. 15:28:28 (62.xxx) Media id B00500 is needed for the restore. 15:28:41 (62.001) Restoring from image created 7/2/2010 1:36:06 PM 15:28:43 (62.001) INF - If Media id B00500 is not in a robotic library administrative interaction may be required to satisfy this mount request. 15:28:46 (62.001) INF - Waiting for mount of media id B00500 on server miracle-main for reading. 15:28:47 (62.001) INF - TAR STARTED 15:28:48 (62.001) INF - Waiting for positioning of media id B00500 on server miracle-main for reading. 15:30:52 (62.001) INF - Beginning restore from server miracle-main to client miracle-main. 15:30:53 (62.001) FTL - tar file read error 15:30:53 (62.001) INF - TAR EXITING WITH STATUS = 13 15:30:53 (62.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY 15:30:53 (62.001) INF - TAR KEPT 0 EXISTING FILES 15:30:53 (62.001) INF - TAR PARTIALLY RESTORED 0 FILES 15:30:53 (62.001) Status of restore from image created 7/2/2010 1:36:06 PM = file read failed 15:30:54 (62.xxx) INF - Status = the restore failed to recover the requested files.2.1KViews0likes6Comments