How to start/stop Net Backup services on master/media servers?
Hi all, This sounds silly! But still it will be great if somebody can tell me "how to start/stop netbackup services on master/media servers from commandline" master/media servers - AIX 5.3 Net Backup 6.5.2 Thank you. DDSSolved97KViews2likes14Comments
ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Failed to process backup file <c-2057956423-20150516-0c>
Hi All, I'm trying to restore Oracle 12c database backup, but unable to restore it, script using for restoring controlfile :- run { set until time "to_date('2015/05/15 18:40:00','YYYY/MM/DD HH24:MI:SS')"; allocate channel ch1 type 'sbt_tape' parms="ENV=(NB_ORA_CLASS=AIR_ABCDB12_DB_DSTGEDV_ONLINE, NB_ORA_SERV=abcbkp02, NB_ORA_CLIENT=abcdb12)"; restore controlfile; alter database mount; } Error : - channel ch1: ORA-19870: error while restoring backup piece c-2057956423-20150516-0d ORA-19507: failed to retrieve sequential file, handle="c-2057956423-20150516-0d", parms="" ORA-27029: skgfrtrv: sbtrestore returned error ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Failed to process backup file <c-2057956423-20150516-0d> Detailed log :- abcbkp02:> rman target / catalog rman/xxx@rmancat Recovery Manager: Release 12.1.0.2.0 - Production on Fri May 15 20:10:23 2015 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. connected to target database: DSTGEDV (not mounted) connected to recovery catalog database run { set until time "to_date('2015/05/15 18:40:00','YYYY/MM/DD HH24:MI:SS')"; allocate channel ch1 type 'sbt_tape' parms="ENV=(NB_ORA_CLASS=AIR_ABCDB12_DB_DSTGEDV_ONLINE, NB_ORA_SERV=abcbkp02, NB_ORA_CLIENT=abcdb12)"; restore controlfile; alter database mount; } executing command: SET until clause allocated channel: ch1 channel ch1: SID=122 device type=SBT_TAPE channel ch1: Veritas NetBackup for Oracle - Release 7.6 (2015021210) Starting restore at 15-MAY-15 new media label is "@aaaah" for piece "c-2057956423-20150515-2b" channel ch1: starting datafile backup set restore channel ch1: restoring control file channel ch1: reading from backup piece c-2057956423-20150515-2b channel ch1: ORA-19870: error while restoring backup piece c-2057956423-20150515-2b ORA-19507: failed to retrieve sequential file, handle="c-2057956423-20150515-2b", parms="" ORA-27029: skgfrtrv: sbtrestore returned error ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Failed to process backup file <c-2057956423-20150515-2b> failover to previous backup new media label is "@aaaah" for piece "c-2057956423-20150515-2a" channel ch1: starting datafile backup set restore channel ch1: restoring control file channel ch1: reading from backup piece c-2057956423-20150515-2a channel ch1: ORA-19870: error while restoring backup piece c-2057956423-20150515-2a ORA-19507: failed to retrieve sequential file, handle="c-2057956423-20150515-2a", parms="" ORA-27029: skgfrtrv: sbtrestore returned error ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Failed to process backup file <c-2057956423-20150515-2a> failover to previous backup ^C user interrupt received PSDRPC returns significant error 1013. released channel: ch1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 05/15/2015 20:10:33 RMAN-03099: job cancelled at user request ************************** Please let me know incase if any other info needed for this. Thanks in advance for your suggestions/recommendations/solution.!Solved66KViews1like12CommentsOracle RMAN restore is failing with error "ORA-19507: failed to retrieve sequential file, ...."
Hi All, We are running netbackup for oracle agent. The oracle clients has four instance and each instance has its own backup policy. The backup is successful for all instances. But when it comes to restore, only one instance restore succeeds and 3 fails. below is the rman output: RMAN> run { 2> allocate channel ch1 type 'sbt_tape'; 3> SEND'NB_ORA_SERV=backup-server,NB_ORA_CLIENT=banner,NB_ORA_POLICY=banner-oracle-seed-policy,NB_ORA_SCHED=Default-Application-Backup'; 4> restore controlfile to '/tmp/my_controlfile_seed.ctl'; 5> release channel ch1; 6> } using target database control file instead of recovery catalog allocated channel: ch1 channel ch1: sid=155 devtype=SBT_TAPE channel ch1: Veritas NetBackup for Oracle - Release 7.5 (2012060520) sent command to channel: ch1 Starting restore at 22-MAR-13 channel ch1: starting datafile backupset restore channel ch1: restoring control file output filename=/tmp/my_controlfile_seed.ctl channel ch1: reading from backup piece cntrl_18_1_810725846 ORA-19870: error reading backup piece cntrl_18_1_810725846 ORA-19507: failed to retrieve sequential file, handle="cntrl_18_1_810725846", parms="" ORA-27029: skgfrtrv: sbtrestore returned error ORA-19511: Error received from media manager layer, error text: Backup file <cntrl_18_1_810725846> not found in NetBackup catalog failover to previous backup channel ch1: starting datafile backupset restore channel ch1: restoring control file output filename=/tmp/my_controlfile_seed.ctl channel ch1: reading from backup piece bk_14_1_810725788 ORA-19870: error reading backup piece bk_14_1_810725788 ORA-19507: failed to retrieve sequential file, handle="bk_14_1_810725788", parms="" ORA-27029: skgfrtrv: sbtrestore returned error ORA-19511: Error received from media manager layer, error text: Backup file <bk_14_1_810725788> not found in NetBackup catalog failover to previous backup . . . . released channel: ch1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 03/22/2013 11:35:44 RMAN-06026: some targets not found - aborting restore RMAN-06024: no backup or copy of the control file found to restore I appreciate if somebody can assist in finding a solution for this problem. Many Thanks, HadiSolved36KViews1like8CommentsInstall a linux client - step by step
Ineed help to install a linux client. I am not familiar with Unix/Linux "Language". Can anybody help me with a step by step guide? The Master NBU is a Windows 2003 and I have 3 Linux (suse 32/64bit))clients and I must to install the NBUclient. Usually this installation makes the linux administrator, but now is in vacation. We have a network path where the setup kit's are "\\servername.shared.com\setup" and I can on the client logging. What must i do next. ...? Thanks for your help" Regards Marius DemeterSolved34KViews1like17Comments
Windows 10? New software update for Symantec System Recovery 2013 Desktop Edition?
I am currently using Symantec System Recovery 2013 R2 with my Windows 8.1 based desktop PC. I am planning on upgrading to Windows 10 on July 29, 2015 when Windows 10 is released. I've been relying on Norton Ghost and SSR 2013 to do full system images for years. Is Symantec currently working on software for Symantec System Recovery 2013 so that it will be compatible with Windows 10? Will Symantec be offering a FREE update patch to Symantec System Recovery 2013 that will make it compatible with Windows 10? Will it be called Symantec System Recovery 2013 R3 or something else like Symantec System Recovery 2015? I would like to see SSR 2013 tested and certified as compatible with Windows 10 as soon as possible. I would prefer not to have switch to another vendor's system image backup software like Acronis. Their website is saying that you can get a free software update for Windows 10 compatibility for Acronis True Image 2015.34KViews12likes385Comments
Expired backup sets not deleted
Anybody solved that problem with Expired backup sets? I can see them expired, Allow Backup Exec to delete all expired backup sets is enabled, but BE does not delete them even when there is no disk space on storage. I saw some other posts but are few month old... Besides with no solutionSolved34KViews1like10Comments
VSS timeout issues, restart not suitable solution
Hello I have had continual issues with vss writers time outs on one of our machines we are backing up. Running Windows Server 2008R2 SP1, using BE2010 R3 SP1 The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job. The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points. I have selected "Process logical volumes for backup one at a time" too see if this helps. Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues. Thanks for the help vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {bcedc94e-0c21-4212-8bbf-b65083123138} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177} State: [9] Failed Last error: Timed outSolved30KViews2likes9Comments
NBU status: 2074, EMM status: Disk volume is down
Environment: Master Server: Windows Server 2008 R2 Media Server: Windows Server 2008 R2 EMC DataDomain All the backup jobs including catalog backup jobs are running successfully. I tried to cleanup all expired images with bpimage -cleanup –allclients due to increase in size of image catalog and got error. The media server mentioned in the below job details has two storage units, one local drive as basic disk storage unit stu-03 and other one is data domain network drive \\dd670\backup Both storage units are accessible and backup jobs are running fine on them. What could be the cause and possible solutions of this error? Ran bpimage -cleanup –allclients and got the following error from the job details: 1/24/2014 12:49:40 AM - Info nbdelete(pid=7024) deleting expired images. Media Server: enp-en01.xxx.com Media: @aaaaJ 1/24/2014 12:49:40 AM - Error nbdelete(pid=7024) Cannot obtain resources for this job : error [2074] the requested operation was partially successful(1) The job was successfully completed, but some files may have been busy or unaccessible. See the problems report or the client's logs for more details. 1/24/2014 12:49:40 AM - requesting resource @aaaaJ 1/24/2014 12:49:40 AM - Error nbjm(pid=5692) NBU status: 2074, EMM status: Disk volume is down 1/24/2014 12:49:40 AM - Error nbjm(pid=5692) NBU status: 2074, EMM status: Disk volume is downSolved30KViews1like4Comments
Windows 10? New software update for Symantec System Recovery 2013 Desktop Edition?
I am currently using Symantec System Recovery 2013 R2 with my Windows 8.1 based desktop PC. I am planning on upgrading to Windows 10 on July 29, 2015 when Windows 10 is released. I've been relying on Norton Ghost and SSR 2013 to do full system images for years. Is Symantec currently working on software for Symantec System Recovery 2013 so that it will be compatible with Windows 10? Will Symantec be offering a FREE update patch to Symantec System Recovery 2013 that will make it compatible with Windows 10? Will it be called Symantec System Recovery 2013 R3 or something else like Symantec System Recovery 2015? I would like to see SSR 2013 tested and certified as compatible with Windows 10 as soon as possible. I would prefer not to have switch to another vendor's system image backup software like Acronis. Their website is saying that you can get a free software update for Windows 10 compatibility for Acronis True Image 2015.