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 ?
Windows - Netback 7.0 Reboot issues
Currently have a server which is Windows Server 2003 running Netbackup 7.0. I have a robot with two drives - Dell PowerVault 132T. I have been having a problem readding the Robot to Netbackup, when i am running the scan it is only picking up the two drives. I have had the robot on the netbackup before but i had to readd the drives which i had accidently removed the robot as well. It is on a NDMP set up but i dont have the full info to manually add it in. The medium changer can be seen in Device Manger. and the device can be accessed through its webGUI. I know this is out of support officially but any help would be much appreciated?
Lost my tape library
I have 3 backup servers, my master and one media server is Windows 2008 R2 and running Netbackup 8.0. The other is running 2003 and NBU 7.5.0.7. This older server is only used for offsiting with the tape library. Last week, I had issues with this unit and network. After a few reboots, the server was back up on the network, but the library and tape drives were no longer recognized. I am at a loss as to why. They don't show up in device manager and not really sure where to go from here. I was in the process of bringing up a newer library and decommissioning the old library and server, but was not ready for that. Can anyone give me some guidance?(24) socket write failed
Hello, I would like some assistance in figuring this one out, it have been bugging me for weeks. My environment. Master and two media serversWindows 2012R2 running NBU 7.7.3 Client is Server 2000 running NBU client 6.5.4 What I have tried. disabling TCP offload and upping the client timeout. I also tried creating a new policy and backing up just two folders and not the ALL_Local_Drives. Attached is the bpbkar log from the client using logging 5. Anything else needed to diagnose this let me know. Thanks, Scott
network read failed(42)
Hi All, Full catalog backup(f:\catalog drive assigned from VMAX storage array) completed fine on last sunday. then on monday we assigned E drive from Pure and did robocopy for F drive to E drive. All catalog data moved to E drive on Monday. Then i chanded drive lettrs F drive into G drive. And, E drive to F drive(now my F:\catalog drive is from Pure storage). When diff catalog backup started on Monday it failed with 42. I am now running Full catalog backup and dont know if it will complete complete. it will take another 6 hours to confirm. May i know what caused the failure and what i need to do? Thank you in advance.Netbackup Migrator for Enterprise Vault
Hi, I am hoping someone can help me, please. I have some enterprise vault collections that have been migrated to tape via netbackup. Everything is working fine when retrieving a stubbed file but the loading and reading of the tape is way to slow. Is there a way to make a duplicate of the tape to disk and just use that duplicate on disk as the primary? If so, can someone provide steps for duplication and setting as primary. Running Netbackup 6.5 (I know, I know - Dinosaur) but company had no budget to upgrade. Thanks so much for any helpWe 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,Oracle: status 25
*** Moved to new post fromhttps://vox.veritas.com/t5/NetBackup/ORA-19511-Error-received-from-media-manager-layer-error-text/m-p/839557 *** Oracle backups are getting failed with 25 whereas windows backups are failing with 25 .Please find the below the logs for reference. Recovery Manager: Release 10.1.0.4.0 - Production Copyright (c) 1995, 2004, Oracle. All rights reserved. connected to target database: DMSP (DBID=1485656476) using target database controlfile instead of recovery catalog RMAN> RUN { 2> ALLOCATE CHANNEL MYL_RMAN1 TYPE SBT_TAPE parms="ENV=(NB_ORA_POLICY=IRG_ora_gerpasx01_dmsp,nb_ora_client=GERPASX01, nb_ora_serv=w2zbu001,nb_ora_sched=weekly)"; 3> ALLOCATE CHANNEL MYL_RMAN2 TYPE SBT_TAPE parms="ENV=(NB_ORA_POLICY=IRG_ora_gerpasx01_dmsp,nb_ora_client=GERPASX01, nb_ora_serv=w2zbu001,nb_ora_sched=weekly)"; 4> CONFIGURE RETENTION POLICY TO NONE; 5> CONFIGURE CONTROLFILE AUTOBACKUP ON; 6> BACKUP INCREMENTAL LEVEL 0 FORMAT 'db_bkup_%d_%U_%t' DATABASE; 7> BACKUP FORMAT 'archive_%d_%U' ARCHIVELOG ALL DELETE INPUT ; 8> } 9> list backup summary; 10> exit; allocated channel: MYL_RMAN1 channel MYL_RMAN1: sid=146 devtype=SBT_TAPE channel MYL_RMAN1: Veritas NetBackup for Oracle - Release 7.5 (20130610) allocated channel: MYL_RMAN2 channel MYL_RMAN2: sid=121 devtype=SBT_TAPE channel MYL_RMAN2: Veritas NetBackup for Oracle - Release 7.5 (20130610) old RMAN configuration parameters: CONFIGURE RETENTION POLICY TO NONE; new RMAN configuration parameters: CONFIGURE RETENTION POLICY TO NONE; new RMAN configuration parameters are successfully stored old RMAN configuration parameters: CONFIGURE CONTROLFILE AUTOBACKUP ON; new RMAN configuration parameters: CONFIGURE CONTROLFILE AUTOBACKUP ON; new RMAN configuration parameters are successfully stored Starting backup at 25-AUG-19 channel MYL_RMAN1: starting incremental level 0 datafile backupset channel MYL_RMAN1: specifying datafile(s) in backupset input datafile fno=00008 name=G:\ORACLE\ORADATA\DMSP\USERS02.DBF input datafile fno=00009 name=H:\ORACLE\ORADATA\DMSP\USERS03.DBF input datafile fno=00005 name=H:\ORACLE\ORADATA\DMSP\USRINDEX01.DBF input datafile fno=00006 name=H:\ORACLE\ORADATA\DMSP\TOOLS01.DBF channel MYL_RMAN1: starting piece 1 at 25-AUG-19 channel MYL_RMAN2: starting incremental level 0 datafile backupset channel MYL_RMAN2: specifying datafile(s) in backupset input datafile fno=00004 name=G:\ORACLE\ORADATA\DMSP\USERS01.DBF input datafile fno=00001 name=G:\ORACLE\ORADATA\DMSP\SYSTEM01.DBF input datafile fno=00003 name=G:\ORACLE\ORADATA\DMSP\SYSAUX01.DBF input datafile fno=00002 name=G:\ORACLE\ORADATA\DMSP\UNDOTBS01.DBF input datafile fno=00007 name=G:\ORACLE\ORADATA\DMSP\STATSPACK01.DBF channel MYL_RMAN2: starting piece 1 at 25-AUG-19 RMAN-03009: failure of backup command on MYL_RMAN1 channel at 08/31/2019 18:47:21 ORA-19506: failed to create sequential file, name="db_bkup_DMSP_3vua46us_1_1_1017256924", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSACreateObject: Failed with error: Server Status: cannot connect on socket channel MYL_RMAN1 disabled, job failed on it will be run on another channel RMAN-03009: failure of backup command on MYL_RMAN2 channel at 09/01/2019 18:15:51 ORA-19506: failed to create sequential file, name="db_bkup_DMSP_40ua46us_1_1_1017256924", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSACreateObject: Failed with error: Server Status: cannot connect on socket channel MYL_RMAN2 disabled, job failed on it will be run on another channel released channel: MYL_RMAN1 released channel: MYL_RMAN2 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on MYL_RMAN2 channel at 09/01/2019 18:15:51 ORA-19506: failed to create sequential file, name="db_bkup_DMSP_40ua46us_1_1_1017256924", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSACreateObject: Failed with error: Server Status: cannot connect on socket Recovery Manager complete. Recovery Manager: Release 10.1.0.4.0 - Production Copyright (c) 1995, 2004, Oracle. All rights reserved. connected to target database: DMSP (DBID=1485656476) using target database controlfile instead of recovery catalog RMAN> RUN { 2> ALLOCATE CHANNEL MYL_RMAN1 TYPE SBT_TAPE parms="ENV=(NB_ORA_POLICY=IRG_ora_gerpasx01_dmsp,nb_ora_client=GERPASX01, nb_ora_serv=w2zbu001,nb_ora_sched=weekly)"; 3> ALLOCATE CHANNEL MYL_RMAN2 TYPE SBT_TAPE parms="ENV=(NB_ORA_POLICY=IRG_ora_gerpasx01_dmsp,nb_ora_client=GERPASX01, nb_ora_serv=w2zbu001,nb_ora_sched=weekly)"; 4> CONFIGURE CONTROLFILE AUTOBACKUP ON; 5> BACKUP FORMAT 'archive_%d_%U' ARCHIVELOG ALL DELETE INPUT ; 6> SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT'; 7> SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT'; 8> BACKUP FORMAT 'archive_%d_%U' ARCHIVELOG ALL DELETE INPUT ; 9> RELEASE CHANNEL MYL_RMAN1; 10> RELEASE CHANNEL MYL_RMAN2; 11> } 12> list backup summary; 13> exit; allocated channel: MYL_RMAN1 channel MYL_RMAN1: sid=109 devtype=SBT_TAPE channel MYL_RMAN1: Veritas NetBackup for Oracle - Release 7.5 (20130610) allocated channel: MYL_RMAN2 channel MYL_RMAN2: sid=82 devtype=SBT_TAPE channel MYL_RMAN2: Veritas NetBackup for Oracle - Release 7.5 (20130610) old RMAN configuration parameters: CONFIGURE CONTROLFILE AUTOBACKUP ON; new RMAN configuration parameters: CONFIGURE CONTROLFILE AUTOBACKUP ON; new RMAN configuration parameters are successfully stored Starting backup at 28-AUG-19 current log archived channel MYL_RMAN1: starting archive log backupset channel MYL_RMAN1: specifying archive log(s) in backup set input archive log thread=1 sequence=148427 recid=147678 stamp=1017356444 input archive log thread=1 sequence=148428 recid=147679 stamp=1017357945 input archive log thread=1 sequence=148429 recid=147680 stamp=1017368154 input archive log thread=1 sequence=148430 recid=147681 stamp=1017399647 input archive log thread=1 sequence=148431 recid=147682 stamp=1017417645 input archive log thread=1 sequence=148432 recid=147683 stamp=1017442849 input archive log thread=1 sequence=148433 recid=147684 stamp=1017446150 input archive log thread=1 sequence=148434 recid=147685 stamp=1017477052 input archive log thread=1 sequence=148435 recid=147686 stamp=1017513770 channel MYL_RMAN1: starting piece 1 at 28-AUG-19 channel MYL_RMAN2: starting archive log backupset channel MYL_RMAN2: specifying archive log(s) in backup set input archive log thread=1 sequence=148416 recid=147667 stamp=1017152022 input archive log thread=1 sequence=148417 recid=147668 stamp=1017152022 input archive log thread=1 sequence=148418 recid=147669 stamp=1017152690 input archive log thread=1 sequence=148419 recid=147670 stamp=1017169927 input archive log thread=1 sequence=148420 recid=147671 stamp=1017197758 input archive log thread=1 sequence=148421 recid=147672 stamp=1017237658 input archive log thread=1 sequence=148422 recid=147673 stamp=1017256328 input archive log thread=1 sequence=148423 recid=147674 stamp=1017291706 input archive log thread=1 sequence=148424 recid=147675 stamp=1017310546 input archive log thread=1 sequence=148425 recid=147676 stamp=1017320206 input archive log thread=1 sequence=148426 recid=147677 stamp=1017342640 channel MYL_RMAN2: starting piece 1 at 28-AUG-19 RMAN-03009: failure of backup command on MYL_RMAN1 channel at 09/03/2019 19:12:08 ORA-19506: failed to create sequential file, name="archive_DMSP_41uac3gc_1_1", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSACreateObject: Failed with error: Server Status: cannot connect on socket channel MYL_RMAN1 disabled, job failed on it will be run on another channel