ContributionsMost RecentMost LikesSolutionsRe: RMAN Backup Failure Bpbrm sending junk characters and failing Are those DB instance names seen in the error.jpg? If so, it does resemble the FORMAT string that specify in RMAN backup script. Re: Sharepoint backup end with status 1 partially sucessful Try running a FULL backup and see if you get the Status 1, if not, then it will be down to the INCR shedules Re: Sharepoint backup end with status 1 partially sucessful Just be aware of the backup selection when using Sharepoint & combining Incrementals. Policy ucust-gst-sharepoint-int Schedule daily_diffinc You are most likely running into the following: http://www.symantec.com/docs/TECH160884 You may need to exclude the Index Files from incremental backups in this policy. Its in Page 68 (Symantec NetBackup for Microsoft SharePoint Server Administrator's Guide) Re: NBU 7.5 policy for Exchange DAG's on VMWare Ravi, I did some digging on this and you are correct in your assumption, You can configure the Vmware based policy to protect Exchange 2013 - you simply do not have the GRT functionality, (thats until 7.6.0.3). So you should be able (as you said) recover from Storage Group level back into the Exchnage environment on that setup. Re: NBU 7.5 policy for Exchange DAG's on VMWare If not mistaken, ticking the Exchange Option within The Vmware policy is invoking GRT, so for your combination Exchange 2013 v GRT v 7.5x - is still not supported. If you are not ready to upgrade, to support your Exchange environment you need to install the NBU Agent on the client host directly create a policy using the Exchange Client Type. (not Vmware) Re: NBU 7.5 policy for Exchange DAG's on VMWare Ravi, How is this different to your post here: https://www-secure.symantec.com/connect/forums/application-state-capture-fails-status-47 You cannot mix 7.5.x with Exchange 2013 GRT. Are you now at 7.6.x? Re: Two restore jobs are ever created ! - Restore sharepoint Also note down what object are you trying to restore, ie Content DB, GRT object, Site Collection etc. Re: SQL database backup is getting failed running through SQL agent The only failure you had past 6pm was one of the database failed for <Policy_SQL_Daily>, still looks in low verbosity. dbclient.log 18:08:22.499 [7228.8760] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.> 18:08:22.511 [7228.8760] <2> vnet_pbxConnect: pbxConnectEx Succeeded 18:08:22.511 [7228.8760] <2> logconnections: BPRD CONNECT FROM X.X.X.X.64258 TO X.X.X.X.1556 fd = 1028 18:08:22.575 [7228.8760] <16> Dbbackrec::PerformNBOperation: ERR - Error found executing <backup database "Database1" to VIRTUAL_DEVICE='VNBU0-7228-8760-1431986485', VIRTUAL_DEVICE='VNBU1-7228-8760-1431986485' with stats = 10, blocksize = 65536, maxtransfersize = 65536, buffercount = 4, differential>. 18:08:22.586 [7228.8760] <2> vnet_pbxConnect: pbxConnectEx Succeeded You have "Database1" setup in the bch script? That logical database doesn't exist in your environment. So look to remove it. Re: ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Failed to process backup file <c-2057956423-20150516-0c> If you are doing alternative client restore Try create a folder <Install path>\NetBackup\db\altnames \usr\openv\netbackup\db\altnames Create a file named "No.Restrictions" Also, Check that NB_ORA_SERV=abcbkp02 Reflects the first entry in bp.conf SERVER=abcbkp02 Re: Application State Capture Fails Status 47 We do support non-granular support for Exchange 2013 at 7.5.0.7 - but you will need to install the NBU agent on the guest host directly and use the Netbackup Exchange option (not VMware)