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.!Solved66KViews1like12CommentsHow to check VCS version and update ?
Dear all, I've been asked to manage few asymmetric failover win 2003 systems with Veritas Cluster Server installed: how can i check the current verision and if there was some hot-fix, and services pach installed ? Thanks in advance and Best Regards, /fabrizio32KViews2likes10CommentsBackups don't complete - hangs on Active: Running - Backup
Just upgraded from a working install of Backup Exec 2012 to BE2014 14.1 with all update installed. Since upgrading, I have not had a single successful backup. I have deployed the 2014 backup agent to my servers and rebooted them after the install. They now validate as having the latest version of theagentinstalled. The backups will run and appear to backup all of the selections as expected. The issue is the backup job never ends. It just hangs up on "Backing up". Job status indicates "Active: Running - Backup". If I view the job activity, it doesn't seem to be working on any current file or directory. Judging by bytes and file count, I'm pretty sure everything has been backed up, but the job doesn't stop. The job log xml file shows the following: Job server: BACKUPSRV Job name: SRV23.DOMAIN.LOCAL Backup 00014-Full - End of Week Job started: Monday, March 30, 2015 at 4:40:37 PM Job type: Backup Job Log: BEX_BACKUPSRV_04279.xml Job Backup Method: Full Drive and media mount requested: 3/30/2015 4:40:39 PM Drive and media information from media mount: 3/30/2015 4:40:42 PM Drive Name: Synology DS512+ Media Label: B2D014498 Media GUID: {6326d716-216c-493b-a5d8-4eeac38bbb6f} Job Operation - Backup Backup Set Retention Period: 3 Weeks. Compression Type: None Encryption Type: None SRV23.DOMAIN.LOCAL Backup Exec server is running Backup Exec version 14.1.1786.1103 with SP-2,HF-227745. Agent for Windows(SRV23.DOMAIN.LOCAL) is running Backup Exec version 14.1.1786.1103 with SP-2,HF-227745. Snapshot Technology: Started for resource: "\\SRV23.DOMAIN.LOCAL\C:". Snapshot technology used: Symantec Volume Snapshot Provider (VSP) for Windows Server 2000 only. Snapshot Technology: Symantec Volume Snapshot Provider (VSP) snapshot cache file settings for volume "C:" : Initial: 12376 MB. Maximum: 12376 MB. File: "\\?\Volume{dd143455-36c9-11dc-a162-806d6172696f}\Backup Exec AOFO Store\_BEVspCacheFile_1.VSP". Snapshot Technology: Symantec Volume Snapshot Provider (VSP) snapshot settings used: Quiet Time: 5 seconds. Time Out: 2000 seconds. Network control connection is established between 172.22.1.62:62236 <--> 172.22.1.53:10000 Network data connection is established between 172.22.1.62:62331 <--> 172.22.1.53:3450 \\SRV23.DOMAIN.LOCAL\C: Family Name: "Media created 3/30/2015 4:40:39 PM" Backup of "\\SRV23.DOMAIN.LOCAL\C:" Backup set #1 on storage media #1 Backup set description: "" Backup Method: Full - Back up files (using modified time) Backup started on 3/30/2015 at 5:06:53 PM. Backup completed on 3/30/2015 at 5:11:08 PM. Backed up 11495 files in 1321 directories. Processed 1,137,817,834 bytes in 4 minutes and 15 seconds. Throughput rate: 255 MB/min Additionally, cancelling the backup manually (which requires killing the job engine process) results in the Job Status being "Cancelled". It also means the filesfrom the backupdo not show up in the restore list when attempting to restore. I can provide additional logs as needed.Solved14KViews0likes10CommentsHow to update Backup Exec Remote Agent For Windows System_
Hi all! I'm excperiencing connecting problems during night becakup to random clients - V-79-57344-65072 "the connection to target system has been lost". I've checked Backup Exec RAWS version at media server as well as on all remote systems - it's 13.0.5204.109. The Backup Exec RAWS version on the media serverin newer than enywhere else - it's 13.0.5204.114. In order to try to resolve this issue I want to update agents first. Is it possible to do it automaticly? The uninstallation process and push install doesn't help - the older version is installed.14KViews1like18CommentsError 239
hi, some backups failed with error code 239. these client are correct on the NBU Policy, and, the DNS resolution is OK. the resolution with bpclntcmd -hn and with -ip are correct. the communication is OK too. when i lanch the backup from command line with a lowercase of the client name that give the error : EXIT STATUS 239: the specified client does not exist in the specified policy. when i changed the client name to the uppercase, and lanched again, it's pass. when launching from GUI, it's OK. when launching with all fqdn name it's pass, same if launching from command line with IP adress. the issue appear just when launching with lowercase... the backups are launched from a scheduler (that run the command bpbackup...). the Issue appear aleatory, after we upgraded the Master; media servers from 7.5.0.6 to 7.7.1 (Netbackup Enterprise). master is windows 2008 R2 Standard Edition. please helpSolved13KViews0likes17CommentsNorton Ghost users - Welcome to Symantec System Recovery!
As announced today (15 March 2013), Norton Ghost 15 is being discontinued, and will be replaced with Symantec System Recovery (SSR) 2013 Desktop edition. Click here for details. We'd like to welcome those customer who already have made the transition, or are thinking about it! Please use this thread to discuss any non-technical issues, such as functionality, upgrade information, etc. If you encounter a technical issue and require technical epertise, you are in good hands. This board is monitored by several SSR specialists, ready to assist. Simply start your own thread with your question. On the surface, Ghost 15 and SSR 2013 are very similar in the look and feel. The console hasn't changed much, so using the product itself should not be much of a learning curve. However, the engine itself has gone through several improvements. Here are a few of the changes in SSR 2013 from Ghost 15: Support for Windows Server 2012 and Windows 8 UEFI Support:Symantec System Recoverynow enables boot from UEFI (Unified Extensible Firmware Interface) in addition to BIOS. 64 bit Support: 32-bit and 64-bit recovery disks are now included. USB Recovery Disk: Create a custom Symantec SystemRecovery Disk on a USB device.Add 32- or 64-bit drivers. Advanced Monitoring and Reporting:Symantec SystemRecoveryMonitor is a new monitoring solution that's extremely simple to use andis FREE of charge to all Symantec System Recovery 2013 customers. It's a standalone andlightweightsolution for managing up to 100 nodes.It’s simplicity and no extra dependency eliminates the learning curve for users. Intuitive GUI along with essential action controls provide crisp status along with ability to take desired actions seamlessly through the same view. Improved support for virtual environments: Greater support for ESX, VMWare, HyperV, and Citrix. Smart Reconciliation:Now Backups and reconciliation are efficiently done by smartly tracking changed blocks.The reconcile time is drastically reduced to seconds by eliminating the need to do a complete reconcile in cases of crashes or abrupt shutdowns. In addition,incrementalbackups are now up to 750% faster. (Incremental Backup without reconcile at least 35%,Full Backup 15% faster,Incremental Backup with reconcile – At least 750% faster thanNorton Ghost 15) For more information on SSR 2013, visit http://www.symantecsystemrecovery.com. Again, welcome Norton Ghost users! Please let us help make the transition to SSR 2013 as seamless as possible.9.2KViews4likes97CommentsUpgrade Backup Exec 2010 R3 SP4 To BE 16
Are you currently using Backup Exec 2010 R3 SP4 and planning to upgrade to Backup Exec 16 ? If so, then Veritas recommend you to read this blog and follow the steps before installing Backup Exec 16. Backup Exec supports a direct upgrade from Backup Exec 2010 R3 SP4 to Backup Exec 16. However, specific to 2010 R3 SP4, you need to ensure that your current SQL version is compatible with Backup Exec 16. The Backup Exec 16 Environment Check will block an upgrade , if your implementation is using a local SQL Express instance created by Backup Exec with the name ‘BKUPEXEC’, which is installed with SQL 2005 SP3. Refer to the following screenshot. To avoid this error you must have SQL 2005 SP4 installed, which is compatible with Backup Exec 16. SQL 2005 SP4 version can be installed with Windows updates (if it is enabled on your setup). Make sure your systems are fully patched with Windows updates. You can also download SQL 2005 SP4 from Microsoft: http://www.catalog.update.microsoft.com/Search.aspx?q=KB2463332 To verify that the correct version of SQL is installed on your setup, go to the SQL Server Configuration Manger and select SQL server 2005 services > SQL Server > SQL server (BKUPEXEC) > Properties. The Service Pack Level now displays 4. Note: If you select an existing instance of SQL Server that is not installed by Backup Exec, you must upgrade the SQL Server to SQL 2008 R2 SP2. When you upgrade from previous versions, Backup Exec automatically converts your existing definitions, configurations, and jobs to the current version. Some of your jobs may be combined or moved. After the migration completes, Backup Exec displays the Migration Report that you must review and acknowledge before Backup Exec continues the upgrade process. In this report, you can see how your jobs were migrated. Veritas recommends that you review the Migration Report thoroughly to determine how your existing jobs have changed and how you may need to adjust your jobs manually. The Migration Report is available for viewing from the Backup Exec Administration Console or the Home tab at any time after the migration completes. The Migration Report is stored in the following path: \Program Files\Veritas\Backup Exec\Data\MigrationReportFiles\Data-Migration-Report.html. References Upgrade Bacup Exec 2010 R3 to BE 15 Veritas Backup Exec 16 Version Upgrade Process Upgrading Backup Exec 15 to 168.8KViews3likes0CommentsEnterprise Vault Tab Missing in Outlook 2010
After installing Enterprise Vault addin 11.1.3474 on client win 8.1 desktop,I dont see Enterprise vault tab in outlook. I dont know why this is happening ? Allthough in add and remove programs it shows as installed, below is the screenshot: Even in outlook it shows as enabled, below is the screen shot: EV log gives below information in %temp%\ev_client_log_20150528154030: 28/05/2015 10:10:30.926[4052][H]: Log file created (level 1). 28/05/2015 10:10:30.930[4052][H]: LoadSettingsFromHiddenMessage com_error: 0x80004005 28/05/2015 10:10:30.931[4052][H]: User has never been enabled. 28/05/2015 10:10:31.463[4052][H]: FUI: Not loading UI as action map is empty. Is the user enabled? Please let me know what Im supposed to do so that I can get Enterprise Vault tab in outlook client. I dont have any access to Enterprise Vault server so I dont know if anything needs to be done from server side... Expecting your answer for this issue.Solved8.6KViews0likes4Commentsinternal error 8027
Hi, I encountered "internal error 8027",before I restore my image to DL380pGen8server. My platform is linux Debian with 3 partitions.Only -IR can resolve the issue but it takes too long to afford in manufactory. Let me know if anyone can advie it. I am using WinPE4, Ghost 12.0.0.6284, but I would like to upgrade to version 12.0.0.8003 above. Hopefully it can resolve my issue. Can anyone advie how to upgrade it? Thanks. Regards. EmilySolved8KViews0likes1Comment