After Installing Sophos Ent Console backups to a NAS are failing. I have disabled On-Access scanning, and still having no luck. Exceptions for Backup Exec folder and file locations are listed too. A server without SEC is backing up to the same location with out issue. Any help is appreciated.
Hello Kris Poskitt,
what exactly is failing?
A server without SEC is backing up
SAV (the endpoint component which you suspect to interfere) is independent of SEC (RMS is "shared" and under control of SEC/SUM but not involved in scanning). Backup did work before installing SEC and the Endpoint components?
Christian
what exactly is failing?
The VM Servers are failing to backup to the NAS, Backup Exec error code E00084F4. There are 3 jobs, one for each VM. The start times for each job are an hour apart. When the jobs fail they all fail the same time. We can have them running for 4 hours before the all fail, or even longer. Now the backup that is successful is the host server of the VMs. The Host server has 6 NICs all teamed to the same switch. This switch also has 4 NIC ports for the NAS teamed. Because the host can backup which has no SAV installed, we can rule out connectivity. Its just SAV and the VM's
A server without SEC is backing up
SAV (the endpoint component which you suspect to interfere) is independent of SEC (RMS is "shared" and under control of SEC/SUM but not involved in scanning). Backup did work before installing SEC and the Endpoint components?
Yes all the VMs on the host backed up every day fine. Just coincidental ever since i installed SEC they failed.
I could be completely wrong with SEC, it could be coincidental. Also something to note too is; i also tried to backup to a local hard disk on the Host server to take NAS out of the equation, but this fails the same way too. Disk space availability is not an issue. backing up 1.03TB and have 15TB available.
Hope this helps picture things better.
Apologies, i mean ever since SAV installed on all Server VMs, the backups have failed.
SEC is installed on one VM for management.
Hello Kris Poskitt,
they all fail the same time
hm, the VMs shouldn't be "aware of each other", even less the SAV component on them. I'm not familiar (actually have no idea of) Backup Exec.
This is far beyond my meager knowledge and I'd like to shift it on to Support ... [^o)] ... and I'm probably missing something obvious. That the (guest) backups apparently fail at the same time is somewhat perplexing. Are these your only virtual servers (i.e. is this issue limited to this host)? Do the backups always overlap (as you've mentioned 4 hours they seem to take a long time) and in addition are always all three active when the error occurs? How frequent to you run the backups and how often do they fail? Personally I'd try - if feasible, and depends on the answers to the preceding questions - one of the following: 1) - add another server which also runs a backup job (of sufficient duration) but without SAV; 2) - uninstall Sophos from one of the servers.
Christian
Thanks for your response.
Yes they are only VM Servers that fail backup, not Host Server as Host Server has no SAV installed.
Yes Backups do over lap, and they have never been a problem before! Reason for multiple backup jobs is to backup a vm for each job rather than one job and all vm's. Experience of one job and all vm's is that is if one VM fails, the rest fail too. I get more success when i set individual jobs.
Backups run daily and fail daily since SAV.
I have ran one job only on each server, without over lap and get the same issue.
I will uninstall SAV off one VM and test backup again.
.
Hello Kris Poskitt,
only VM Servers
my wording was perhaps not as clear as intended, to rephrase: You have only one host with three VMs, you have more than one host with server VMs but backup fails only on one the VMs of one host, or you have more than one host and the VMs' backup fails on several hosts? BTW: Which hypervisor?
Backups run daily and fail daily
but as far as I understand at different points. What means more success vs. without over lap and get the same issue in this context? The backups fail but progress farther before failing?
Anyway, even if it's SAV that causes or triggers the error this does not explain the other jobs failing simultaneously. Can you identify which fails first, can it be any of the three? If so it'd not be a cinch to see that uninstalling SAV made a difference.
Christian
only VM Servers
my wording was perhaps not as clear as intended, to rephrase: You have only one host with three VMs, you have more than one host with server VMs but backup fails only on one the VMs of one host, or you have more than one host and the VMs' backup fails on several hosts? BTW: Which hypervisor?
One Host and 3 VMs only. Host is running Hyper-V Hypervisor, Windows Server 2012r2
Backups run daily and fail daily
but as far as I understand at different points. What means more success vs. without over lap and get the same issue in this context? The backups fail but progress farther before failing?
They run sequentially i.e Dc job starts 1600, sql job starts 1700, Exchange jpb starts 1800, host server job start 1900. They will fail at 21:20 one day and the next 01:40. It's random. No schedule task or other jobs run at these times. When the jobs fail they all fail at the same time apart from the host job. The host stays active and completes. All backing up to the same location NAS.
Anyway, even if it's SAV that causes or triggers the error this does not explain the other jobs failing simultaneously. Can you identify which fails first, can it be any of the three? If so it'd not be a cinch to see that uninstalling SAV made a difference. Its to the exact second they all fail.
only VM Servers
my wording was perhaps not as clear as intended, to rephrase: You have only one host with three VMs, you have more than one host with server VMs but backup fails only on one the VMs of one host, or you have more than one host and the VMs' backup fails on several hosts? BTW: Which hypervisor?
One Host and 3 VMs only. Host is running Hyper-V Hypervisor, Windows Server 2012r2
Backups run daily and fail daily
but as far as I understand at different points. What means more success vs. without over lap and get the same issue in this context? The backups fail but progress farther before failing?
They run sequentially i.e Dc job starts 1600, sql job starts 1700, Exchange jpb starts 1800, host server job start 1900. They will fail at 21:20 one day and the next 01:40. It's random. No schedule task or other jobs run at these times. When the jobs fail they all fail at the same time apart from the host job. The host stays active and completes. All backing up to the same location NAS.
Anyway, even if it's SAV that causes or triggers the error this does not explain the other jobs failing simultaneously. Can you identify which fails first, can it be any of the three? If so it'd not be a cinch to see that uninstalling SAV made a difference. Its to the exact second they all fail.
