Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Console of Backup Exec, Best Practices

Created: 30 Jun 2011 • Updated: 06 Sep 2013 | 2 comments
This issue has been solved. See solution.

Somebody Knows about this ?

1.- The Best Practice of Backup Exec is have the console  physical or virtual ? i know what the console works in virtual enviroment  but is the best practice????   i will have issues in the future?  somebody have a whitepapper?

 

Discussion Filed Under:

Comments 2 CommentsJump to latest comment

CraigV's picture

Well, your media server should be physical for better connectivity to storage hardware, as having a media server as a VM requires very strict conditions (like an Adaptec SCSI card for instance).

For the BE Remote COnsole, it doesn't matter if it is on a VM or a physical server/workstation. It's simply a way to log onto the BE server without logging onto the server.

Whichever suits your environment, go with it. But from a user-side, I created a user account with normal domain user rights, and made that a member of each backup server's Backup Operators group. This locked the account down a bit.

 

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

SOLUTION
sazz.'s picture

Remote Administration Console will be available only if the server does not already have Backup Exec for Windows Server installed. Also, it should be noted that the Remote Administration Console has limited functionality when compared to a full installation of Backup Exec. Admin Console is only to have the managebility over your Backup Exec environment and works fine on both PHYSICAL and VIRTUAL without any issues. I been using it on Virtual machine without having any issues for past 2 years