We Have MSSQL 2005 - Should We Upgrade to NetBackup 8.0 or 7.7.3 ?
We Have MSSQL 2005 - Should We Upgrade to NetBackup 8.0 or 7.7.3 ? I'm preparing to upgrade our NetBackup servers as our current version (v7.6.1.2) is EOSL. However, I have a problem. We are still gradually migrating our databases from an MSSQL Server 2005 cluster to a new MSSQL 2014 cluster. This process will take months and the NetBackup upgrade cannot wait. I'm aware that MSSQLServer 2005 is not supported in NetBackup beyond v7.6.1.2. Worse still is it's running on Win2003SP2, which is, of course, also not supported. I am proposing to go ahead and upgrade our NetBackup servers to v8.0 in the meantime, and keep the NetBackup Client on our SQL Server 2005 cluster at v7.6.1.2. Alternatively, I could upgrade the NetBackup servers to v7.7.3 and keep the NetBackup Client on our SQL Server 2005 cluster at 7.6.1.2. So my questions are: 1. Would this work ? Would our existing database and transaction log backup policies still work? 2. If it would work, which NetBackup version would you recommend, v7.7.3 or v8.0 ? I'm leaning towards v8.0 myself and a Symantec / Veritas support engineer told me yesterday it is the generally more stable of the two. Please note that the fact that we still use Win2003 and MSSQL2005 is a matter which is largely beyond my control, so please don't post replies telling me about the risks this poses to our organisation - I already know and we're working on it. Tags:Windows 2003 End of Support, SQL Server, NetBackup 7.6, NetBackup 8.0,Netbackup 7.7 and Windows 2003 Compatibility
Moved to new post fromhttps://vox.veritas.com/t5/NetBackup/Netbackup-7-7-and-Windows-2003-Support/m-p/754626 It seems from your responses that nobody really knows the answer (to Relboy's question either). It's better just to say those three little words that are so hard for some to utter: "I don't know." Better still, don't post at all, and leave the preaching about Win2003 being a risk to an audience who wouldn't already know this. I suspect no-one in this forum is in a position to kill off business critical legacy systems as they wouldn't have the authority or budget control. Let's look at the question of operating a newer NetBackup server with older clients for legacy platforms another way. Is anyone out there already doing this ? E.g., have you tried running NetBackup Server 7.7.3 or 8.0 and, on the legacy Win2003 client, NB Client 7.6.1.2 ? How did this work out for you ? Did you experiment with different NB versions ? Which was the optimal combination ?
Backing up Oracle ZFS 7120 to Tape using NetBackUp
Hi Everyone, Earlier today my Oracle DBA asked if I am able to backup his Oracle ZFS 7120 appliance with Netbackup, today was the first time I've heard of ZFS. He wants to perform a weekly full of the whole ZFS drive, which is about 10 TB and back it up to tape and send it offsite for DR purposes, So I have the following questions: Thank you in advance for all your assistance. 1. is it possible to use netbackup 7.6 to perform a backup from the zfs appliance straight to tape? how does that work if the databases are constantly being written to? 2. after doing research, I found an Oracle ZFS plugin for NetBackup, would installing thi software cause MBU to crash? 3. If I am wrong about the Oracle ZFS plugin for netbackup, how would I go about getting netbackup to talk to the ZFS appliance, and then schedule the weekly full straight to tape? Thank you for your time.
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)