VSS Error
I produce backup windows 2008R2 ADDS role, Backup only SYSTEM STATE this virtual server (host hyper-V 2012).Backup Exec 2012 ver.14.0 rev. 1798. as a result of getting an error Job Completion Status Job ended: 14 apr 2014 г. at 16:58:28 Completed status: Failed Final error: 0x8004230e - 0x8004230e (2147754766) Final error category: Other Errors For additional information regarding this error refer to link V-79-32772-8974 Errors Click an error below to locate it in the job log Backup- alserpost-dc.alserpost.kz - Snapshot Technology: Initialization failure on: "\\dc.contoso.local\System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11225 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected does not support snap technology for this volume. Select another snapshot technology, and then run the job again.
What and How is NetBackup 7
Hello Guys, I hope you are started evaluating NetBackup 7.0. It have lot of new features. Here are some of them. New features: Integrated deduplication ■ Client deduplication ■ Media server deduplication ■ OpsCenter ■ Convergence of NOM and VBR ■ Improved ease-of-use ■ Additional base reporting functionality ■ Direct upgrade path ■ Expanded and simplified deployment ■ OpsCenter Analytics ■ Turnkey operation to enable advanced, business reporting ■ Improved reporting features ■ NetBackup for VMware ■ Fully integrated with VMware vStorage APIs ■ New VM and file recovery from incremental backups ■ New recovery wizard ■ Tighter vCenter integration ■ Guided Recovery ■ New database agents and enhancements to existing agents ■ Exchange 2010 support ■ Windows 7 and Windows 2008R2 client support ■ Enhancements to the NetBackup Enterprise Vault agent - Support all Enterprise Vault 8.0 databases using the Enterprise Vault Agent including the Fingerprint database, FSA Reporting database, and Auditing database - Enterprise Vault 8.0 support for granular quiescence - Enterprise Vault Migrator is now included with NetBackup ■ Enhancements to the NetBackup for Hyper-V agent - New file-level incremental backups - Two types of off-host backup - Hyper-V R2 and Cluster Shared Volumes (CSV) - Flexible VM identification ■ Improved SharePoint Granular Recovery ■ New platform proliferation ■ NetBackup 7.0 supported platforms ■ NetBackup 7.0 feature notifications Known Issues: Domain is OpsCenterusers@domain not NOMBuiltin@domain ; that is an error in the documentation. The userid and password are admin and password Master server version reports NetBackup 3.4 incorrectly After Windows Reboot, OpsCenter fails to start. Fix is to Restart the Authentication Service then start the OpsCenter Services. Pop-Up Blocker prevents the OpsCenter interface from initializing. Turn off Pop-Up blocker to run OpsCenter. On 64 bit windows systems, OpsCenter install or upgrade might fail. Install "VC2005 x86" from the DVD (<DVD Drive>\x86\Server\Prerequisites\vcredist_x86.exe) If OpsCenter installation failed due to any reason, the roolback and cleanup may not happen correctly in some scenarios. The fix is to execute the command “ SC DELETE OPSCENTERSERVER” The Windows/Solaris installation will fail if the OpsCenter host is not part of any domain name. (host is not qualified with a suffix such as “min.veritas.com”) Workaround: The solution is to add a domain suffix and then re-install Drive throughput and Drive utilization reports don’t work in some scenarios Creation of a custom report doesn’t work if user chooses Absolute timeframe option Deduplication reports (Size factor, Protected Size vs. Backed up Size, Size Savings reports) don’t work in a PDDE environment. They only work in a standalone PureDisk environment. I wanted all of guys to share new experience in working Netbackup 7.0. Share us the New Finding/Errors.
Backup failed with error code 71 (EXIT STATUS 71: none of the files in the file list exist). The server rebooted automatically on 28th march and after that the backups are failing.
Problem description : Backup failed with error code 71 (EXIT STATUS 71: none of the files in the file list exist). The server rebooted automatically on 28 th march and after that the backups are failing. The network drives are Netapp storage Shares and it is mapped to the client COLLECTIONSRV. The drives are accessible from OS using the user “USER1”. The netbackup client service is having the logon credentials of user “USER1”. In the policy the “ Backup Network drive” option is selected. The path is also specified properly. Also tried with the mapped drive letter “Y:\”. But the backups are failing with the same error code. The server has been rebooted manually but still the same issue. BPBRM: 03:02:59.482 [3339] <4> bpbrm handle_backup: from client COLLECTIONSRV: TRV - object not found for file system backup: \\10.10.5.138\evsqlbkp\SQLFULL\ BPBKAR: 10:58:04.857 AM: [1136.2856] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received 10:58:05.107 AM: [1136.2856] <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = \\10.10.5.138\evsqlbkp\SQLFULL\ 10:58:05.107 AM: [1136.5844] <4> tar_base::V_KeepaliveThread: INF - The Keepalive thread is active. Keepalive interval 60 Seconds 10 …. 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - ================================================================================ 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking estimate: start 10:58:07.794 AM: [1136.2856] <2> tar_base::V_vTarMsgW: TRV - object not found for file system backup: \\10.10.5.138\evsqlbkp\SQLFULL\ 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking estimate: stop 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking time: 0 secs 10:58:07.841 AM: [1136.5844] <4> tar_base::V_KeepaliveThread: INF - Keepalive Thread Terminating. Mutex:WAIT_OBJECT_0 10:58:07.841 AM: [1136.2856] <4> tar_base::V_StopKeepaliveThread: INF - The Keepalive Thread has Exited. Wait Reason:WAIT_OBJECT_0 10:58:07.841 AM: [1136.2856] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 71: none of the files in the file list exist 10:58:07.841 AM: [1136.2856] <4> tar_backup::backup_done_state: INF - ================================================================================ 10:58:09.856 AM: [1136.2856] <16> dtcp_read: TCP - failure: recv socket (460) (TCP 10053: Software caused connection abort) 10:58:09.856 AM: [1136.2856] <4> OVShutdown: INF - Finished process 10:58:09.872 AM: [1136.2856] <4> WinMain: INF - Exiting C:\Program Files\VERITAS\NetBackup\bin\bpbkar32.exe 10:58:11.872 AM: [1136.2856] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\VERITAS\NetBackup\logs\BPBKAR\040312.LOG
VxBSACreateObject: Failed with error
Hi all, I need your help, my manager Netbackup on a Windows 2008 operating system and Netbackup 7. We have an integration with RMAN but when I run the backup sguente send us the error. The owner forOracle engine is ORACLE and the NetBackup with another user named NetBackup, and integrate the same group of DBA but still sends me the same error. INF - Begin progress logging for process: (14464.15088) INF - Using policy BMB_SMCHFMPROD4_HFM_Ora_Onl_D to perform a user directed Oracle Stream Based backup. INF - Starting Oracle Recovery Manager. INF - Using: "f:\app\hfm\product\11.2.0\dbhome_1\bin\rman.exe" INF - Connection info: target 'netbackup/*****@HFM' rcvcat 'RMANHFM/*****@rmanbm' INF - Start of Recovery Manager input. INF - # ----------------------------------------------------------------- INF - # RMAN command section INF - # ----------------------------------------------------------------- INF - RUN { INF - ALLOCATE CHANNEL ch00 INF - TYPE 'SBT_TAPE'; INF - SEND 'NB_ORA_CLIENT=SMCHFMPROD4,NB_ORA_SID=HFM,NB_ORA_POLICY=BMB_SMCHFMPROD4_HFM_Ora_Onl_D,NB_ORA_SERV=mxqrsbur,NB_ORA_SCHED=Diario'; INF - BACKUP INF - INCREMENTAL LEVEL=0 INF - FORMAT 'bk_u%u_s%s_p%p_t%t' INF - TAG 'rl_t%t_s%s_p%p' INF - DATABASE; INF - RELEASE CHANNEL ch00; INF - # Backup Archived Logs INF - sql 'alter system archive log current'; INF - ALLOCATE CHANNEL ch00 INF - TYPE 'SBT_TAPE'; INF - SEND 'NB_ORA_CLIENT=SMCHFMPROD4,NB_ORA_SID=HFM,NB_ORA_POLICY=BMB_SMCHFMPROD4_HFM_Ora_Onl_D,NB_ORA_SERV=mxqrsbur,NB_ORA_SCHED=Diario'; INF - BACKUP INF - FORMAT 'arch_u%u_s%s_p%p_t%t' INF - ARCHIVELOG INF - ALL INF - DELETE INPUT; INF - RELEASE CHANNEL ch00; INF - # Control file backup INF - ALLOCATE CHANNEL ch00 INF - TYPE 'SBT_TAPE'; INF - SEND 'NB_ORA_CLIENT=SMCHFMPROD4,NB_ORA_SID=HFM,NB_ORA_POLICY=BMB_SMCHFMPROD4_HFM_Ora_Onl_D,NB_ORA_SERV=mxqrsbur,NB_ORA_SCHED=Diario'; INF - BACKUP INF - FORMAT 'ctrl_u%u_s%s_p%p_t%t' INF - CURRENT CONTROLFILE; INF - RELEASE CHANNEL ch00; INF - } INF - End of Recovery Manager input. INF - Start of Recovery Manager output. INF - Recovery Manager: Release 11.2.0.1.0 - Production on Fri Feb 3 23:27:50 2012 INF - connected to target database: HFM (DBID=1249472717) INF - connected to recovery catalog database INF - allocated channel: ch00 INF - channel ch00: SID=696 device type=SBT_TAPE INF - channel ch00: starting incremental level 0 datafile backup set INF - input datafile file number=00012 name=I:\HFM\DATAFILE\CISFM.DMP INF - input datafile file number=00014 name=H:\HFM\DATAFILE\CISODIWORK.DMP INF - input datafile file number=00015 name=I:\HFM\DATAFILE\CISFM01.DMP INF - input datafile file number=00016 name=I:\HFM\DATAFILE\CISFM02.DMP INF - input datafile file number=00017 name=I:\HFM\DATAFILE\CISFM03.DMP INF - input datafile file number=00019 name=G:\HFM\DATAFILE\CISEA01.ORA INF - input datafile file number=00020 name=G:\HFM\DATAFILE\CISEA02.ORA INF - input datafile file number=00021 name=G:\HFM\DATAFILE\CISEA03.ORA INF - input datafile file number=00022 name=G:\HFM\DATAFILE\CISEA04.ORA INF - Begin progress logging for process: (2436.13472) INF - Start backup of backup piece: (bk_u0vn2e6rs_s31_p1_t774314876) INF - Server status = 241 ERR - Server exited with status 241: the specified schedule is the wrong type for this request INF - input datafile file number=00007 name=H:\HFM\DATAFILE\CISEPMA.DMP INF - input datafile file number=00018 name=H:\HFM\DATAFILE\CISODIWORK2.DMP INF - input datafile file number=00003 name=E:\HFM\DATAFILE\O1_MF_UNDOTBS1_78OBHVV8_.DBF INF - input datafile file number=00013 name=H:\HFM\DATAFILE\CISODI.DMP INF - input datafile file number=00001 name=E:\HFM\DATAFILE\O1_MF_SYSTEM_78OBH3V0_.DBF INF - input datafile file number=00002 name=E:\HFM\DATAFILE\O1_MF_SYSAUX_78OBHK1G_.DBF INF - input datafile file number=00005 name=J:\HFM\DATAFILE\CISHSS.DMP INF - input datafile file number=00008 name=J:\HFM\DATAFILE\CISHBI.DMP INF - input datafile file number=00011 name=E:\HFM\DATAFILE\CISFDM.DMP INF - input datafile file number=00004 name=E:\HFM\DATAFILE\O1_MF_USERS_78OBJ9N7_.DBF INF - released channel: ch00 INF - RMAN-00571: =========================================================== INF - RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== INF - RMAN-00571: =========================================================== INF - RMAN-03009: failure of backup command on ch00 channel at 02/03/2012 23:28:12 INF - ORA-19506: failed to create sequential file, name="bk_u0vn2e6rs_s31_p1_t774314876", parms="" INF - ORA-27028: skgfqcre: sbtbackup returned error INF - ORA-19511: Error received from media manager layer, error text: INF - VxBSACreateObject: Failed with error: INF - Server Status: the specified schedule is the wrong type for this request INF - Recovery Manager complete. INF - End of Recovery Manager output. INF - End Oracle Recovery Manager.
Problème BMR client netbackup 7.1 avec Os AIX
Bonjour j'ai reçu le probleme BMR sur un cleint AIX 6.1 Plateforme: Master server : OS Solaris 10, Natbackup 7.1 Server à backup : agent client netbackup AIX 7.1, Os de AIX 6.1. etat de client connecté est existe sur un reseau de backup dedié( reseau dédié pour la palateforme de backup). Merci de me aider à resoudre cette probleme vue la criticité du plateforme. log de probleme: 09/21/2012 10:57:25 - Info nbjm (pid=17894) starting backup job (jobid=71653) for client KBPRORAC02D001, policy SOA_Prod_BMR, schedule Full-BMR 09/21/2012 10:57:25 - Info nbjm (pid=17894) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=71653, request id:{5D25FC38-03CA-11E2-BD02-00144FA05E06}) 09/21/2012 10:57:25 - requesting resource backup-hcart-robot-tld-0 09/21/2012 10:57:25 - requesting resource backup.NBU_CLIENT.MAXJOBS.KBPRORAC02D001 09/21/2012 10:57:25 - requesting resource backup.NBU_POLICY.MAXJOBS.SOA_Prod_BMR 09/21/2012 10:57:26 - granted resource backup.NBU_CLIENT.MAXJOBS.KBPRORAC02D001 09/21/2012 10:57:26 - granted resource backup.NBU_POLICY.MAXJOBS.SOA_Prod_BMR 09/21/2012 10:57:26 - granted resource 000227 09/21/2012 10:57:26 - granted resource HP.ULTRIUM4-SCSI.001 09/21/2012 10:57:26 - granted resource backup-hcart-robot-tld-0 09/21/2012 10:57:26 - estimated 15002642 kbytes needed 09/21/2012 10:57:26 - begin Parent Job 09/21/2012 10:57:26 - begin Bare Metal Restore: Start Notify Script 09/21/2012 10:57:26 - Info RUNCMD (pid=23519) started 09/21/2012 10:57:26 - Info RUNCMD (pid=23519) exiting with status: 0 Operation Status: 0 09/21/2012 10:57:26 - end Bare Metal Restore: Start Notify Script; elapsed time 0:00:00 09/21/2012 10:57:26 - begin Bare Metal Restore: Bare Metal Restore Save 09/21/2012 10:57:27 - Info bpbrm (pid=23526) KBPRORAC02D001 is the host to backup data from 09/21/2012 10:57:27 - started process bpbrm (pid=23526) 09/21/2012 10:57:29 - collecting BMR information 09/21/2012 10:57:29 - connecting 09/21/2012 10:57:29 - connected; connect time: 0:00:00 09/21/2012 10:57:29 - transfering BMR information to the master server 09/21/2012 10:57:29 - connecting 09/21/2012 10:57:29 - connected; connect time: 0:00:00 09/21/2012 10:57:59 - Error bpbrm (pid=23526) BMRERR: Received BMR error: Failed to import Config file. (1) 09/21/2012 10:57:59 - Error bpbrm (pid=23526) BMRERR: Received BMR error: Failed sending the discovery. (1) 09/21/2012 10:57:59 - Error bpbrm (pid=23526) BMRERR: Received BMR error: BMR information discovery failed. (1) 09/21/2012 10:57:59 - Info bmrsavecfg (pid=0) done. status: 1: the requested operation was partially successful 09/21/2012 10:57:59 - end writing Operation Status: 1 09/21/2012 10:57:59 - end Bare Metal Restore: Bare Metal Restore Save; elapsed time 0:00:33 09/21/2012 10:57:59 - begin Bare Metal Restore: Policy Execution Manager Preprocessed Operation Status: 0 09/21/2012 11:07:27 - end Bare Metal Restore: Policy Execution Manager Preprocessed; elapsed time 0:09:28 09/21/2012 11:07:27 - begin Bare Metal Restore: End Notify Script 09/21/2012 11:07:27 - Info RUNCMD (pid=23829) started 09/21/2012 11:07:27 - Info RUNCMD (pid=23829) exiting with status: 0 Operation Status: 0 09/21/2012 11:07:27 - end Bare Metal Restore: End Notify Script; elapsed time 0:00:00 Operation Status: 1 09/21/2012 11:07:27 - end Parent Job; elapsed time 0:10:01 the requested operation was partially successful (1) Merci d'avance.
Downloading the trail version of veritas netbackup 7
In 2010, in which address Icould downloadthe trail versionof veritas netbackup 7? I've been using veritas netbackup 6.5.4 + vmware vshpere, using the vdr tobackup vms. Backuping vms with Netbackup 6.5.4 require too much disk space. VDR can not back up other content in windows, resulting in I had two data backup centers. Depressed. To find a lot of addresses, and not now.