This is 1 of the reasons for not running BE on a VM. If you're able to move it to physical hardware, do so.
That said, put in an exclusion for the BE media server in your selection list, or deselect it manually.
Thanks for the quick answer.
I tried to express that in both scenarios the BE media server _is_ on physical hardware.
In the vmware environment it's a totally separate physical computer while in the hyper-v environment it is the host, but still on physical hardware.
In other words. BE is not installed in virtual machines, and that's why I'm confused about the error message.
And also the virtualdisk- and normal windows agent-backup jobs are separated.
That is pretty strange then...any selections for the media server in your selection list itself? IF so, remove them and run the backup job again to see if this goes through successfully. Change to the Text View in your selection list.
Had recently encountered same issue...i.e. BE was on a physical server, however receiving error about the media server cannot back itself up...here the reason was IP conflict...one of the VMs had the same IP address as that of the BE media server & hence the error...worth a try..
No selections for anything but the virtual machines in the vmware environment job.
In the hyper-v environment I have to select the hyper-v branch from under the media server but there are no other components selected from the media server itself.
In the Text View there is only a selection for:
And similar for the hyper-v environment.
I've also made a whole new selection list and job but that didn't help either.
I read something about it in a forum.
Checked this, no luck.
All VMs are servers so there would be other problems also with an IP conflict.
Also saw this in a forum somewhere.
Thank you for the answer though.
Are you backing up any non-windows VMs in the same job ? If yes, separate them into two jobs...one for windows VMs with GRT enabled & the other one for non-windows VMs with GRT disabled & retry..
In the vmware environment all VMs are Windows computers, with GRT enabled. So nothing new to try here.
In the hyper-v backup I can remove the one VM that's a Linux machine.
Hello again. About the Hyper-V environment.
After removing the linux VM from the backup job it does not give me the error.
The new separate job for the linux VM does not work at all, naturally. Gives me the error.
Does this have to do with BE2010 not being fully compatible with Linux?
I've modified the job to backup only the vdisks using the Windows Agent, this would do the trick as I'm not using a linux agent.
Still having this problem with the vmware backup jobb, will try to separate some of the VM:s to see if one of them is causing the problem.
Thank you for the tip!
The strangest thing about the Linux VM backup is that it's on a different Hyper-V host, not the one that BE is installed on.
When I try to run the job selecting only the Linux VM from the Hyper-V agent of the second Hyper-V host I get the normal (topic) error after 2 seconds. So it does not even try to do anything, just stops.
The Linux version is Red Hat Enterprise 6.2, not found in the compatibility list, can this be the problem? Still, I'm only trying to backup the vdisks.
Tried the backup from another physical server, now with BE 2012.
Same result, can't back up the Linux machine at all. BE 2012 is compatible with Red Hat 6.0 but no mention of 6.2. Is this still the problem?
The backup runs for 5 seconds tops. Same error.
I'm probably going to have to use another software to back that computer up for now....