No drives available.
Hi, I have 3 media servers sharing 2 drives in an Quantum i500. We have a Storage lifcycle policy which eventually write to these 2 drives. There are 2 active jobs however they will only write to one drive at a time. One job will be writing and the other active job states "No drives avaiable" and doesn't use the second drive. Both drives are working ok as the jobs flip between the 2 drives. Storage Unit has maximum write drives set to 2.Netbackup admin console backup error
Dear, I perform daily backup on tape from monday to Saturday. Since last week, everytime i start the backup i get the following error: a pending action is associated with the resource request. User intervention may be required. I move to device monitor and i find pending request from another tape (very old tapes). I tried to deny request, assign.... It won't work because everytime i assign or deny i get another request from another tape. I appreciate your help. Sincerely. Jad.
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?
Problemas al restaurar archivos desde LTO3
Estimados, Estoy tratando de realizar la restauración de mis cintas antiguas LTO3 por temas de auditoria, sin embargo me esta saliendo el siguiente error: He realizado un inventario antes y todo esta conforme a nivel de libreria, asi mismo de la consola de netbackup puede realizar inventario y todo sale OK. El problema sale cuando hago una restauración. 11:38:04 07/10/2019: Restore Started 11:38:05 (223418.xxx) Restore job id 223418 will require 1 image. 11:38:05 (223418.xxx) Media id 0109L2 is needed for the restore. 11:38:08 (223418.001) Restoring from copy 1 of image created 30/06/2014 06:54:50 a.m. 11:38:10 (223418.001) INF - If Media id 0109L2 is not in a robotic library administrative interaction may be required to satisfy this mount request. 11:38:14 (223418.001) INF - EXIT STATUS 103: error occurred during initialization, check configuration file 11:38:21 (223418.001) Status of restore from copy 1 of image created 30/06/2014 06:54:50 a.m. = error occurred during initialization, check configuration file 11:38:21 INF - Server status = 2826 11:38:21 (223418.xxx) INF - Status = invalid error number. Saludos CordialesOracle: status 25
*** Moved to new post from https://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
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 help
