BERemote failed logins using odd credentials
New install of Backup Exec 2014, have installed the Windows Agent on a VMware virtual server. Last 3 nights we have been receiving the following error in the Security Event log: Event 4625 An account failed to log on. Subject: Security ID: SYSTEM Account Name: <LOCAL SERVER> Account Domain: <OUR DOMAIN> Logon ID: 0x3e7 Logon Type: 4 Account For Which Logon Failed: Security ID: NULL SID Account Name: <ESX Admin account> Account Domain: Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x140 Caller Process Name: C:\Program Files\Symantec\Backup Exec\RAWS\beremote.exe Network Information: Workstation Name: <LOCAL SERVER> Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Transited Services: - Package Name (NTLM only): - Key Length: 0 Here's what I don't get. The <ESX Admin Account> that is being used is setup properly in the Backup Exec Media Server under logon accounts, but it is used for accessing the ESX hosts themselves, not the guest servers. That account exists only on the ESX servers, not as a user account in the local domain. The guest server should be using a domain account setup specially just for the Backup Exec system and that is also setup as the default logon account. This server, <LOCAL SERVER>, is actually backed up at 7PM and displays no errors and is successful. The above error occurs about 4 hours later and no active jobs involving this server are running. I have seen this same issue on 3 other servers, doing the exact same thing. Any ideas on what is going on? Note that this issue is not preventing jobs from being ran, but it is showing up in our security logs as a failed attempt for a "special access account" and our auditors see this and are questioning why it is happening. This is the reason I need this resolved. Thanks.
Windows system state backup duplicate from disk to tape error
Environment Windows 2008 Standard SP2 64bit Backup Exec 15 ver 14.2 rev 1180, tape drive IBM HH LTO Gen 4 1. I have noticed that the windows server system state backup full to disk then duplicate to tape => backup is successful. But when I run backup windows server system state backup differential to disk then duplicate to tape => backup is unsucessful (job rate is 0MB/Min) (of course, system state backup to disk is sucessful). 2. Weird System State backup size: it's mention at issue : https://www-secure.symantec.com/connect/forums/weird-system-state-backup-size . it's still happen in backup exec 15. Please help me solve it. Many thanks!
Backup Exec 2014 remote agent crashing on Server 2003
Hello, My company has a Windows 2008 Standard SP2 server running Backup Exec 2014 with multiple servers running the remote agent on Windows Server 2003 Standard SP2 (as well as other OS's). We have been having an issue the past 2 weeks with our 2003 VM's specifically. One by one the remote agent has started crashing and will keep crashing every time BE tries to communicate with it until we reboot. The servers give the following error when the crash occurs: Event ID 259 A process crash has been detected. Faulting application: beremote.exe 14.1.1786.1059 Faulting module: beclass.dll 14.1.1786.1059 Fault offset 0x9a3c1 Exception code 0xc0000005. For now it looks like the issue goes away after a reboot, however we are not really interested in systematically rebooting every 2003 server that eventually has this issue. The jobs were functioning perfectly fine before, and there were no changes made in the past month or so that we could see as having caused this change. I have a case open with Symantec but they are generally not interested and not sure what is happening. Has anyone seen this before, and if so do you know the cause?Backup Exec 15: The operation failed because the vCenter or ESX server reported a problem creating or accessing more files needed.
Hello, I need some help I'm tryin to Backup a Virtual Server using a Virtual Based backup but I'm not being succesful. There images below display the errors I am getting. Job Log shows this... I tested the credencials and everything seems fine. The Credencial Ststus is succesful and the State shows Online as you can see below I also have the correct version of Backup Exec Remore Agent Utility Installed, Under Security tab, I can see that the truct was established between the server where Backup Exec 15 is installed and the Remote server I am trying to backup. What can I do here? Thank you.
Backup Exec 15 Service crashes when trying to add vcenter server
Having an issue trying to add vcenter 6.0 server to Backup Exec 15. When tring to add the server, an error pops up about communication failer and the Backup Exec Remote Agent for Windows on BE 15 server stops. If the Application logs I get 2 errors Event ID 1000 and 259. Google searching, I found a post simular where it was suggested to replace libcurl.dll file from BE 15 with the file from BE 2014. How ever I am still not able to add vcenter server to BE15. Currently all backups a runninng via the local agent installed in all VM's Vcenter server has the latest BE agent installed and vmtools installed. Event ID 259 A process crash has been detected. Faulting application: beremote.exe 14.2.1180.1162 Faulting module: vmwaretools.dll 6.1.15.511 Fault offset 0x4150fe Exception code 0xc0000005. Event ID 1000 Faulting application name: beremote.exe, version: 14.2.1180.1162, time stamp: 0x55943f99 Faulting module name: vmwaretools.dll, version: 6.1.15.511, time stamp: 0x5551a550 Exception code: 0xc0000005 Fault offset: 0x00000000004150fe Faulting process id: 0xc3c Faulting application start time: 0x01d0db55522320a7 Faulting application path: C:\Program Files\Symantec\Backup Exec\beremote.exe Faulting module path: C:\Program Files\Symantec\Backup Exec\vmwaretools.dll Report Id: c83570f6-4771-11e5-80fa-0cc47a0b6176 Faulting package full name: Faulting package-relative application ID: I created a test server with BE2014 and was able to add vcenter server to it and was success in runnin a backup.exchange 2010 hyper v 2012 R2
Hallo Zusammen, ich habe ein Problem mit Backup Exe 2014 SP2: Bei der Sicherung der virtuellen Maschine mit dem OS Win 2008 R2 auf dieser der Exchange 2010 installiert ist kommt folgende Fehlermeldung: Auf diesem virtuellen Computer wurde ein vollständiges Backup durchgeführt, da die Option zum Zurückgreifen auf ein vollständiges Backup gewählt wurde. Für diesen virtuellen Computer werden die Backup-Methoden 'Inkrementell' und 'Differentiell' nicht unterstützt. V-79-57344-38769 - Der virtuelle Computer 'Buehn-Exch-Hub' wurde offline gesichert, daher sind die VHD- und VHDX-Dateien nur absturzkonsistent. Wiederherstellung auf Dateiebene kann durchgeführt werden, die Ergebnisse sind jedoch unvorhersehbar. Für diesen virtuellen Computer kann keine Wiederherstellung auf Anwendungsebene ausgeführt werden. V-79-57344-38727 - Backup Exec konnte nicht die zur Wiederherstellung individueller Anwendungsobjekte erforderlichen Metadaten für den virtuellen Computer 'Buehn-Exch-Mail' abrufen. Sie können keine GRT-Wiederherstellung von Applikationsdaten von diesem Backup erstellen.Large Hyper-V incremental backups
I'm currently running backup exec 2014 and backup up (amongst other things) a hyper-v host with 6 VMs. I have a full backup every other weekend and incrementals every weekday. I changed around our backup scheme recently to make it a bit more fault tolerant, most notably redirecting each backup to it's own storage. When I did this, I noticed that the backup sizes for my incremental backups reported by backup exec for my hyper-v host did not match the actual backup sizes being used on disk, not even close to. When backup exec finishes it's incremental backup of my hyper-v host, it reports backup sizes that are anywhere from about 1.5 GB to 5 GB depending on what was done that day. If I look at the log for the job, the sizes for each hyper-V host are consistent with that number, showing backup sizes for each host that are typically well under 1 GB before compression, and compression rations between 2:1 and 3:1. However, when I actually go and look at the NAS and the files that BE has created, the size of the vhdx files it creates are all in excess of a 1 GB, commonly 2-3 GB, resulting in the actual size of the hyper-V host incremental backups being about between 10-20 gigs a day. Knowing what's on most of those servers, typically things like a windows 2012 install running nothing but a DHCP server, the backup sizes reported by backup exec are accurate to what the size of the backups should be... so then why are the actual an order of magnitude larger than that? I'm currently experimenting with using the "Microsoft Incremental Backup" method to reduce the backup sizes, but even if it works to reduce the backup sizes this is unadvised as it requires all of my VMs to permanently run in checkpoint mode and checkpoint mode isn't even supported for some types of servers per microsoft documentation (you're not supposed to run a DC in checkpoint mode, or at least you're not supposed to use checkpoints to rollback a domain controller). If I can't find a good method of dealing with this, I may ultimately have to treat all of my virtual servers as physical servers for the purposes of hyper-V and just back them all up individually to get thse backup sizes down to an appropriate size. Btw, the reason the size is an issue is because of copying the backups offsite. We have plenty of storage space and network bandwidth onsite, but our internet bandwidth is limited and we're already pushing closer to this limit than I'm really comfortable with. Is this an issue that only I'm seeing, in which case I may have a configuration error somewhere, or is this normal behavior for hyper-v backups? Is there a method that I can get these backups down to the correct size? There's really no reason for most of these backups to be even 1 GB, let alone multiple GBs.