11-14-2012 08:51 AM
I have the following setup in my organisation:
Backup Exec 2012 installed on Win 2008 R2 virtual server
Servers being backed up successfully:
Physical Win 2008 R2 Domain Controller (System State)
Virtual Exchange 2010 server (win 2008 R2)
We use XenCenter for Virtualization.
The (Virtual) Win 2008 R2 file server backup fails within 2 minutes of the start with "the job failed with the following error: a communications failure has occurred"
The target for all of these backups is a physical server running freeNAS with 1.5Tb available. As I say the PDC and exchange backups to the freeNAS server are successful.
Please advise how to proceed. This has been going on for sometime (months) and we've failed to find a solution. We've been using a non BE method for backup as a fail-safe but this is no longer acceptable.
Thanks
Solved! Go to Solution.
11-14-2012 09:02 AM
It is not recommended that you use a VM as a media server. Furthermore, Xenserver is not a supported VM host.
11-14-2012 09:02 AM
It is not recommended that you use a VM as a media server. Furthermore, Xenserver is not a supported VM host.
11-14-2012 09:05 AM
even though the other two server backups run successfully?
11-14-2012 09:08 AM
When you run an unsupported configuration, if it works you are lucky. Otherwise, you are on your own. You cannot open a support case with Symantec when you have an unsupported configuration.
11-15-2012 01:44 AM
Ok, thanks for the clear response. So now we are going to build a physical 2008 R2 server to be our media server. How do we go about migrating the configuration and backup schedules and history from what we are using now?
Do the agents need re-installing or changing in any way?
Thanks
01-31-2013 12:55 AM
Using Backup Exec 2012 on Windows Server 2011, using external drives for backup but recently begin getting Ready;No idle devices are available and failed backups
Backup Exec is up to date...looking for any suggestions
Thanks in advance