How 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.14KViews1like18CommentsExchange lässt sich nicht mehr sichern
Hallo! Wir haben BackupExec 2010 R3 im Einsatz mit "Agent for MS Exchange Server", "Active Directory Recovery Agent" und "Remote Agent for Windows and Netware Servers". Backup Exec läuft auf einem Server 2003 R2 mit allen Servicepacks und Updates Exchange läuft auf einem Server 2003 R2 64bit mit allen Servicepacks und Updates. Der Remote Agent wurde auf dem Server aktualisiert. Das Problem: Bis letzte Woche wurde der Exchange-Server problemlos gesichert - auch eine Wiederherstellung war kein Problem. Leider habe ich dann das SP2 von BackupExec eingespielt und die 5 angebotenen Hotfixes. Seither lässt sich Exchange nicht mehr sichern und wir bekommen folgende Fehlermeldung: V-79-57344-34070 - AOFO: Initialisierung fehlgeschlagen: "Microsoft Information Store". Advanced Open File Option verwendet: Microsoft Volume Shadow Copy Service (VSS). Fehler im Snapshot-Provider (0xE0008516): Die für einen Snapshot angegebenen Ressourcen verfügen über keine gültigen Daten. Überprüfen Sie, ob Dateien gelöscht oder umbenannt wurden. Ausführliche Angaben finden Sie in der Windows-Ereignisanzeige. Der Link zur entsprechenden Supportseite erzählt irgendwas von Advanced Open File Option - welche nicht verwendet wird. Dies habe ich vorhin überprüft. In der Auswahlliste der Sicherungsjobs wird der Microsoft Information Store seit den Updates nicht mehr angezeigt. Lediglich im Registerreiter "Auswahldetails anzeigen" stehen die Einträge nach wie vor drinnen: \\servername.domäne.inhouse\Microsoft Information Store\First Storage Group|*.* /SUBDIR \\servername.domäne.inhouse\Microsoft Information Store\Second Storage Group|*.* /SUBDIR Kennt dieses Problem jemand und hat vielleicht eine Lösung dafür? Ansonsten müsste ich BackupExec komplett de- und wieder installieren (OHNE irgendwelchen Updates) und hoffen, dass das Programm danach wieder so läuft wie es soll. Das wäre die letzte Option, denn alle Versuche die Exchange-Sicherung seit einigen Tagen wieder zum laufen zu bringen, sind fehlgeschlagen. Vielen Dank10KViews0likes12CommentsSystem State backups slow all of a sudden
All of a sudden all my System State backups appear to be running dreadfully slow, to the point of being unable to complete the backup within a 24hour timeframe. Throughput seems stalled, and BEremote.exe is running at 100% CPU on the affected servers. All servers are running 2008 R2. Checking the sgmon logs I notice that files are still being added to the VSS snapshot. I've tried reinstalling the agents with no change, NTbackup seems to run just fine. Anyone else with this problem? It's happened all at the same time pretty much, I suspect windows update to have pushed some update out that screws things up.Solved9.9KViews0likes13CommentsBE 2014 won't backup VMs on Hyper-V 2012 R2
Hi all. The Backup Server is running Server 2008 R2 Standard with Backup Exec 2014 installed. All updates have been applied from live update. I'm trying to backup VMs on a server running Hyper-V 2012 R2, but I continue to receive a "Final error: 0xa0009679 - A failure occurred querying the Writer status for a Hyper-V virtual machine" error. Running VSS Admin List results in a "Retryable Error" for the Microsoft Hyper-V VSS Writer. I have tried restarting the server already and that didn't help. Any tips? Event Viewer also gives me this at the time of the backup failure: 1) Application and Service Logs > Microsoft > Windows > Hyper_V-VMMS > Admin: Failed to fix-up absolute VHD paths in configuration of virtual machine 'VM Name': Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. (0x8007052F). (Virtual machine ID AEB2B426-05DD-4C4F-AC8F-330B0D57B8D4) 2) Windows Logs > Application: A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried, the error may not reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Other details: The Hyper-V 2012 R2 OS has been separated from the VMs on the HD. OS is on C and the VMs are on D. VM backups continue to run perfectly fine from a Hyper-V 2008 R2 server. All servers mentioned are using the same storage device. Any help will be much appreciated. Thanks everyone.5.7KViews1like20CommentsBackup of SQL fails - wrong user access
Hi, Trying to figure out an issue with backup an sql server 2008 databases on a remote server. Below is the erros I am getting. Now I have looked at TECH144230 and TECH69132 which basically says to check to make sure that the logon account has the sysadmin role on the DB which it does. So I am not sure what the next step is. Backup- PBCA-DOC1V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'guest' does not have permission to run DBCC checkdb for database 'master'. V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'guest' does not have permission to run DBCC checkdb for database 'msdb'. Backup- PBCA-DOC1\CCHDM_SQLEXP2008V-79-57344-37951 - Database master has failed to freeze for the snapshot backup. V-79-57344-37951 - Database msdb has failed to freeze for the snapshot backup.Solved5.7KViews0likes2CommentsFailed Final error: 0xe00084bd - The system cannot find the path specified - unable to restore file or directory.
Hello I can't backup only this Vm with Backup Exec 2014 since a very long time. They are no snapshot existed in snapshot Manager. When i select manually only one VM using snapshot technology .. Could you help me ? it says always .. And after the message appears.... ANd, Why it talk about restore ? I giev a backup not arestore. Error : e00084bd - The system cannot find the path specified - unable to restore file or directory. See the job log for details. Agent used : Yes Advanced Open File Option used : No5.5KViews1like16CommentsRestart required after agent update?
Hi I just upgraded to Backupexec 2014 service pack 1 As after each upgrade, it's adviced to upgrade remote agents. As after each upgrade, it's required to restart servers... Is this really mandatory? No way to just restart remote agent service on remote server? Restarting a server is nothing, but restarting up to 50 or 60 servers take some time. And this should most of times be done during night. It really becomes time consuming to take a few hours each time a hotfix is released No way to solve this Symantec guys? Would be really happy ;)Solved5.5KViews1like3CommentsLogon account that was provided does not have the appropriate privileges to back up the SQL database
Recently I upgrade BackExec 2010 to 2012, updated remote agents etc... and I created all "new" jobs and started from scratch. I have 3 servers running Win2008 with MSSQL and two of them are backing up fine,but I am having problems with one particular server (Win2008 with MSSQL). Testing creditionals work fine, I use the System Logon Account. I have changed the creditionals to domain admins, I even used the SA logon account for access the MSSQL server and it always fails with the below errors. I have done the following: In SQL Server Management Server I made sure that the logon account used for backing up SQL database exists there. Made sure theLogon account was in the Sysadmin Role. Test Run Errors (only a partial list of the errors): Device : 3f4c28a6-a36c-4622-980c-f541f10538d3, DICOMSERVER\MSSQLSERVER Check status : Error: e0009b84, The job failed with the following error: The logon account that was provided does not have the appropriate privileges to back up the SQL database . Either assign the appropriate privileges to this logon account, or use another logon account. Device : 3F4C28A6-A36C-4622-980C-F541F10538D3, \\DICOMSERVER\C: Check status : Error: e0009b84, The job failed with the following error: The logon account that was provided does not have the appropriate privileges to back up the SQL database . Either assign the appropriate privileges to this logon account, or use another logon account. Job Alert Errors(only a partial list of the errors): Job ended: Friday, May 09, 2014 at 12:36:32 AM Completed status: Failed Final error: 0xe0008443 - One or more SQL Database consistency checks have failed. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-33859 V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'guest' does not have permission to run DBCC checkdb for database 'msdb'. V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'public' does not have permission to run DBCC checkdb for database 'PRA_DICOM'. V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'public' does not have permission to run DBCC checkdb for database 'PSC_DICOM'. etc.....etc... Backup- DICOMSERVER\MSSQLSERVER Database \model was not found, or could not be accessed. Click an exception below to locate it in the job log Backup- DICOMSERVER\MSSQLSERVER V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).The item DICOMSERVER\MSSQLSERVER\model in use - skipped.Solved5.2KViews1like13CommentsPre Job - The system cannot find the path specified.
Hello, OS: Windows Server 2008 R2 Standard, Backup Exec: 2010 R3 (up to date) Simple Backup Job, which one is saving just remote files. Pre <d:\scripte\server_down.bat> Post <d:\scripte\server_up.bat> Both scripts running, if I start them manually. All I found was: TECH90733 - "A backup configured to use a batch file in a Pre/Post command does not execute the batch file" but the service is still running as Local System Account Anyone some idea? Greetings! TobiasSolved5KViews0likes18Comments