Data replication to Cloud
Hi all, my customer is willing to setup a Disaster Recovery solution. The source environment is based on Netbackup + DataDomain using DDBoost. Customer would like to replicate to cloud without using DELL DDVE, but he'd rather prefer to use standard blob storage in Azure. Can this be achieved using native NetBackup replication features, or do we need to stop using DDBoost on the source environment and start using a different deduplication tool? I've been given the attached high level architecture, but colleagues state that DDBoost must be disabled in order to use MSDP-C for replication.
Backup policy recovering speed slowly (disk)
Dear NetBackupers, We have a NetBackup version 8.1.1 server and mostly Solaris clients for backup, server is connected with clients via LAN fibre optics and backup storage Dell EMC Data Domain 2500 is mounted via NFS to our NetBackup server also fiber optics. Our issue manifests as two specific policies interleave and the first that is run looses its backup speed and doesn't achieve max potential speed thus backup time of policy that usually finishes in 20 hours lasts around 30 hours. How could we configure client or server settings that when one of the affected policies finishes other regains max potential speed? We have done server tuning as recommended by backup storage vendor as this: ----------------------------------------------------------------------------------------------------- ✔Include the following lines in /etc/system for TCP: set ndd:tcp_wscale_always=1 set ndd:tcp_tstamp_if_wscale=1 set ndd:tcp_max_buf=16777216 set ndd:tcp_cwnd_max=8388608 set ndd:tcp_xmit_hiwat=2097152 set ndd:tcp_recv_hiwat=2097152 for NFS: set nfs:nfs3_nra=16 set nfs:nfs3_max_transfer_size=1048576 set nfs:nfs3_bsize=1048576 set nfs:nfs3_max_threads=256 set rpcmod:clnt_max_conns=64 ✔Add the NFS client mount options "rsize=1048576,wsize=1048576" ✔NFS patch 147268-01 or kernel patch 147440-05 (or later) is installed for Solaris. ---------------------------------------------------------------------------------------------------------------- Changes were done on the media server of NetBackup as we had some troubles with policies speed after that speeds were better but we are still observing before mentioned problems with those two policies when they interleave and the backup speeds in my opinion are not recovering quicky enough when one of those backup policies finishes. Should we make reccomended changes on NetBackup clients also so backup speeds would recover more quickly? TLDR: We can reschedule policies with little effort but how to configure them to achieve maximum speed in less time.
Can't fix error 2106 Disk Storage Server is down
Hello, Tried calling Veritas support on this matter but alas 7.6 is EOSL... We are backing up to Data Domains using SLPs. In an effort to access the Data Domains, an admin tried to login using the boost account and locked it. I have since re-enabled the account which I thought was the cause of the 2106 errors, but I am still getting them. nbdevquery -liststs -stype DataDomain -U shows the storage servers are down I've tried to change the state using nbdevconfig -changestate, but they still show "down" status. I've also deleted/recreated the boost account on the DDs, and did a tpconfig -update , but I can't get the storage server to come up. Not sure which logs I need to look at to resolve this issue. Thanks
Oracle Restore Jobs are failing with 2850 (TpErrno = Robot/LTI protocol error )
Environment Details : Master 7.6.0.1 ( Windows 2008) SAN Media Server : us*****5 We are using EMC DataDomain as VTL (Tape and tape drives are Virtual) /28/2016 3:06:56 PM - Info bpbrm(pid=22605) telling media manager to start restore on client 7/28/2016 3:06:57 PM - Info bpbrm(pid=22605) spawning a brm child process 7/28/2016 3:06:57 PM - Info bpbrm(pid=22605) listening for client connection 7/28/2016 3:06:57 PM - Info bpbrm(pid=22605) child pid: 22626 7/28/2016 3:06:58 PM - Info bpbrm(pid=22605) accepted connection from client 7/28/2016 3:06:58 PM - mounted 7/28/2016 3:06:58 PM - Info tar(pid=2942) Restore started. 7/28/2016 3:06:58 PM - connected 7/28/2016 3:06:58 PM - Info bptm(pid=22613) D07594 7/28/2016 3:06:59 PM - Info bptm(pid=22613) INF - Waiting for positioning of media id D07594 on server us*****5 for reading. 7/28/2016 3:06:59 PM - positioning D07594 to file 3 7/28/2016 3:06:59 PM - positioned D07594; position time: 0:00:00 7/28/2016 3:06:59 PM - begin reading 7/28/2016 3:07:00 PM - Info bpbrm(pid=22605) sending media manager msg: CONTINUE RESTORE 7/28/2016 3:11:55 PM - begin Restore 7/28/2016 3:11:58 PM - 1 images required 7/28/2016 3:11:58 PM - media D07594 required 7/28/2016 3:11:58 PM - media D07673 required 7/28/2016 3:11:59 PM - restoring image us*****5_1469609943 7/28/2016 3:12:03 PM - requesting resource D07594 7/28/2016 3:12:03 PM - granted resource D07594 7/28/2016 3:12:03 PM - granted resource ULTRIUM-TD1.3000590023 7/28/2016 3:37:29 PM - Info bptm(pid=22613) Waiting for mount of media id D07673 (copy 1) on server us*****5. 7/28/2016 3:37:29 PM - started process bptm (22613) 7/28/2016 3:37:29 PM - mounting D07673 7/28/2016 3:37:30 PM - Info bptm(pid=22613) INF - Waiting for mount of media id D07673 on server us*****5 for reading. 7/28/2016 3:37:43 PM - Error bptm(pid=22613) error requesting media, TpErrno = Robot/LTI protocol error 7/28/2016 3:37:49 PM - Error bptm(pid=22625) The following files/folders were not restored: 7/28/2016 3:37:50 PM - Error bptm(pid=22625) UTF - /8vrbnin4_1_1 7/28/2016 3:37:50 PM - Info tar(pid=2942) done. status: 5: the restore failed to recover the requested files 7/28/2016 3:37:50 PM - Info bpbrm(pid=22605) got ERROR 98 from media manager 7/28/2016 3:37:50 PM - Info bpbrm(pid=22605) killing bpbrm child 22626. 7/28/2016 3:42:33 PM - current media D07594 complete, requesting next resource ULTRIUM-TD1.3000590023:D07673 7/28/2016 3:42:34 PM - granted resource D07673 7/28/2016 3:42:34 PM - granted resource ULTRIUM-TD1.3000590015 7/28/2016 3:42:49 PM - current media D07673 complete, requesting next resource ULTRIUM-TD1.3000590015:Oracle:D07673 7/28/2016 3:42:54 PM - Error nbjm(pid=3084) NBU status: 98, EMM status: The media server reported a system error 7/28/2016 3:42:55 PM - restored image us*****5_1469609943 - (error requesting media (tpreq)(98)); restore time 0:30:56 7/28/2016 3:43:01 PM - end Restore; elapsed time: 0:31:06 Restore error(2850)