Backup Exec Alert: Job Warning (Server: "DC-XXXXXXXX") An unknown application is deleting files from the following folder:
I am using Backup Exec 2014 on my sever. I recieve the following error in event viewer. Event ID: 33919 Backup Exec Alert: Job Warning (Server: "XXXXXXXX") An unknown application is deleting files from the following folder: C:\ProgramData\Symantec\CRF Files contained in this folder are used by Backup Exec, and deleting them may cause Backup Exec processes to crash. Determine which application is accessing the folder and add the folder to the application's exclusion list. For more information, click the following link: http://entced.symantec.com/entt?product=BE&module=eng-event&error=V-379-33919&build=retail&version=14.1.1786.1093&language=EN&os=Windows_V-6.1.7601_SP-1.0_PL-0x2_SU-0x110_PT-0x2 HOW TO SOLVE THIS ISSUE?3KViews1like2CommentsBackup Job Fail "This operation returned because the time period expired"
Dear All, I am running Symantec Backup Exec 2010 SP1 I am running daily backup to tape and the attached tape device is HP 1/8 G2 autoloader. Everything was working fine and suddenly the job started to fail with the error in the attached printscreen. After the failure I found that the Device bacaem "Offline" I made sure that the cabling are ok. Device is ok, i can not find any errors. Kindly advice562Views0likes3Commentsjob status - complete with exceptions
there are some backup jobs run in Backup Exec 2012 , only two full backup jobs complete with exceptions in the lastest backup task. The credential of this backup job test result was failed. we haven't change any password or credential of this job. Exceptions Details: can't open this item \\posdb1\[ROOT]/oracle/app/grid/product/11.2.0/log/posdb1/srvm/eonsd_0.log.lck - skiped. can't open this item \\posdb1\[ROOT]/var/run/iscsid.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/multipathd.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/atd.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/sm-client.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/sendmail.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/iscsiuio.pid - skiped.Solved2.4KViews1like8CommentsBE2012 backup VM failed
we are using BE2012 backup the VMhost, the backup media server is a very old IBM server(X236) ,VMverison is Esxi 5.1.0. VM host is IBM x3650M4,have 3 virtual machines.2 on server internal disk, 1 on a DAS. we have a scheduleto backup whole host(3 virtual machines), Mon to Thu differential backup, Fri is full backup,when the job backup 1 virtual machines on internal disk, always have problem. below are some error event from backup media server during job running: ---------------------------------------------------------------------- Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34113 Date: 2/27/2015 Time: 8:47:12 AM User: N/A Computer: XXX Description: Backup Exec Alert: Job Failed (Server: "CNSRVERP") (Job: "XXX-Daily-Diff-Diff-D04-Thu") cnsrvict01-Daily-Diff-Diff-D04-Thu -- The job failed with the following error: A communications failure has occurred with a Virtual Machine resource. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml ------------------------------------------------------------------------------------------------------------ Event Type: Error Event Source: Ntfs Event Category: (2) Event ID: 55 Date: 2/27/2015 Time: 10:41:10 AM User: N/A Computer: CNSRVERP Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\vstor2-mntapi10-shared-CCF91436000050060.... For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 04 00 02 00 52 00 ......R. 0008: 02 00 00 00 37 00 04 c0 ....7..À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 93 04 19 00 ... -------------------------------------------------------------------------------------------------------------------------------------------------- Event Type: Warning Event Source: vstor2-mntapi10-share Event Category: (2) Event ID: 57 Date: 2/27/2015 Time: 10:41:10 AM User: N/A Computer: CNSRVERP Description: The description for Event ID ( 57 ) in Source ( vstor2-mntapi10-share ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: . Data: 0000: 00 00 00 00 01 00 dc 00 ......Ü. 0008: 02 00 00 00 39 00 04 80 ....9.. 0010: 00 00 00 00 01 00 00 c0 .......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ --------------------------------------------------------------------------------- Event Type: Warning Event Source: vstor2-mntapi10-share Event Category: (2) Event ID: 57 Date: 2/27/2015 Time: 10:41:09 AM User: N/A Computer: CNSRVERP Description: The description for Event ID ( 57 ) in Source ( vstor2-mntapi10-share ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: . Data: 0000: 00 00 00 00 01 00 dc 00 ......Ü. 0008: 02 00 00 00 39 00 04 80 ....9.. 0010: 00 00 00 00 01 00 00 c0 .......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ ------------------------------------------------------------------------ Event Type: Warning Event Source: Ntfs Event Category: None Event ID: 50 Date: 2/27/2015 Time: 10:41:11 AM User: N/A Computer: CNSRVERP Description: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 04 00 04 00 02 00 52 00 ......R. 0008: 00 00 00 00 32 00 04 80 ....2.. 0010: 00 00 00 00 01 00 00 c0 .......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 01 00 00 c0 ...À ------------------------------------------------------------ Event Type: Warning Event Source: Ntfs Event Category: None Event ID: 50 Date: 2/27/2015 Time: 10:41:11 AM User: N/A Computer: CNSRVERP Description: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 04 00 04 00 02 00 52 00 ......R. 0008: 00 00 00 00 32 00 04 80 ....2.. 0010: 00 00 00 00 01 00 00 c0 .......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 01 00 00 c0 ...À -------------------------------------------------------------------------- Event Type: Warning Event Source: vstor2-mntapi10-share Event Category: (2) Event ID: 57 Date: 2/27/2015 Time: 10:41:15 AM User: N/A Computer: CNSRVERP Description: The description for Event ID ( 57 ) in Source ( vstor2-mntapi10-share ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: . Data: 0000: 00 00 00 00 01 00 dc 00 ......Ü. 0008: 02 00 00 00 39 00 04 80 ....9.. 0010: 00 00 00 00 01 00 00 c0 .......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ -------------------------------------------------------------------------------------------- what't the problem? thank you1.1KViews0likes5CommentsServices Backup Exec VSS provider cannot start
dear, i have some problem services backup exec vss provider cannot start after installing agent for windows. i install RAWSx64 in windows server 2008 R2. i use syamntec backup exec 2012 Version 14.0 Rev.1798 (64-bit). if i start services occur error "error 1053: the services did not respond to the start or control request in a timely fashion." what's wrong i do? do you have solution?1.7KViews0likes2CommentsBackup Exec 2014
I have a strange problem, I have contacted Symantec support and they told me that there are known issues with the new version of Symantec Backup Exec 2014 and my best bet was to post it on the forums or keep an eye out for updates.. which I don’t understand… but anyway.. so im hoping someone can help me... my setup, OS is windows 2012 R2 and Exchange 2013 Symantec exec 2014 ver. 14.1 rev 1786 (64bit) - Trial LTO4 tape. the backups keep failing with an access denied error, I have tried deselecting the file paths in question but it still fails. I cant find the option to disable this virtual conversion or sdr…. I don’t even need these components… Backup- \\FH.local\C:V-79-57344-41488 - Due to one or more errors in \\FH.local\C:, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore. V-79-57344-33928 - Access is denied. Access denied to directory DFSRoots\Shared Folders\Company\. V-79-57344-33928 - Access is denied. Access denied to directory DFSRoots\Shared Folders\Users\.1.2KViews1like8CommentsExchange inkrementell Sicherung
Guten Tag, nach dem Update von Backup 2010 R3 auf 2014 Sp1 versuche ich unsere Exchange Datenbank 2010 zusätzlich zur täglichen Sicherung auch stündlich inkrementell zu sichern. Die Sicherung scheint auch zu funktionieren, allerdings wird der Auftrag immer mit Fehlermeldungen beendet. Auftrag beendet am Dienstag, 14. Oktober 2014 um 09:03:46 Abschlussstatus: Fehlgeschlagen Endgültiger Fehler: 0xe000fed1 - Beim Abfragen des Writer-Status ist ein Fehler aufgetreten. Details finden Sie im Auftragsprotokoll. Endgültige Fehlerkategorie: Ressourcenfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-65233 Sichern V-79-57344-65233 - Snapshot: Initialisierungsfehler auf: "Microsoft Information Store". Snapshot: Microsoft Volume Shadow Copy Service (VSS).Verfassername: Exchange Server, Verfasserkennung: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Letzter Fehler: Der VSS Writer ist fehlgeschlagen, der Vorgang kann jedoch wiederholt werden (0x800423f3), Status: Stabil (1). Ich habe gesehen das bei prüfen auf dem Exchange Server vssadmin list writers folgender Fehler auftritt: Verfassername: "Microsoft Exchange Writer" Verfasserkennung: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7} Verfasserinstanzkennung: {50964531-c2d2-4f85-9c81-e8b690de95a3} Status: [7] Fehler Letzter Fehler: Wiederholbarer Fehler Nach einem Neustart des System ist der Fehler weg, allerdings taucht er unmittelbar nach starten der inkrementellen Sicherung wieder auf. AOF ist deaktiviert in den Jobeinstellungen. Vielleicht hat jemand den passenden Tip für mich? Grüße StefanSolved1.5KViews0likes7CommentsWeekly Full Duplicate backup wont complete untill TS Weekly Full Duplicate Jobs Complete
Hi Guys, I have a bit of a strange issues. To give you an idea as how we are configured I will detail our policies and then detail the issue. Backup Setup Backup Server Windows Server 2008 R2, Backup Exec 2010 R3 with SP4 on a Physical Server connected to a Robotic Library. Policies Default Policy – This contains a Weekly Full Backup which backups to a folder call BackupToDisk. This backup is then duplicated by a backup called Weekly Full Duplicate. The Weekly Full Backup runs on a Friday between 22:01 and 21:59 on the Saturday. The duplicate backup is then set to run once the Weekly Full backup completes Terminal Servers Policy – This contains a Weekly Full backup to Disk which again save backups to the BackUpToDisk Folder and then has a second linked job to Duplicate the backups to Tape. These jobs run on a Saturday starting at 22:01 till 21:59 on the Sunday. Both duplicate jobs are linked to their respective Weekly Full Jobs and the use the Media Sets. Issue Currently the Weekly Full backup for our Default Policy for our main servers runs perfectly fine on a Friday and into the Saturday, but the duplicate job always fail with the following error message The job failed with the following error: The device cannot be found. If I then try and run the Jobs again by resubmitting on the Saturday then the Jobs again fail with the same error message. If I wait until after the Terminal Server jobs have completed on the Sunday and then resubmit the jobs for the rest of the servers the jobs complete successfully. The Terminal Server Jobs both Weekly Full and Duplicate complete successfully. I have checked that all the previous Weekly Full backups have completed which have all completed successfully, so there is no reason why the backup shouldn’t be working. Does anyone have an idea as to why this happening and what I can do to stop this from happening. Kind Regards1.3KViews0likes9Comments