Just an FYI for those of you moving to Symantec BackupExec 11d from Version10d: There is a documented problem that...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
may occur when you upgrade and import your old settings.
Although your backups may run and verify, on the job log you may find the error message "Cannot connect to media server."
If you do get this message, check your Selection List. If you have included the "System State" in any of your backup jobs that were imported from 10d, you may find that you have two identical entries for the media server and the System State.
If this is the case, take the following steps:
- Uncheck the System State selection in each Selection List.
- Go to Credentials.
- Run Check Credentials.
- Go back and reselect System State for each backup job.
- Run the credentials again.
- You should now have only one entry.
After performing the above procedure, our backups now run cleanly without any errors.
Related item: If you have a firewall installed, you must open port 10,000 on the firewall. (I'm not sure why, but support engineering says that this too is a known issue). We have a SonicWall appliance, and I was able to add and create two new groups -- Backup Exec Services and Backup Exec Remote Agent and a new service -- to open port 10000.
One final note: If the system clock is changed (unfortunately, I can't tell you by how much), Backup Exec will fail.
Rating this tip below will let us know how useful it was to you. And if you have a Windows tip, timesaver or workaround to share, submit it to our tip contest. You could win the monthly prize.