Do I need Remote Server Agent?

[CathodeRay]

Just looking for a little real-world advice... we've got 4 servers: a Primary Domain Controller, a Backup Domain Controller, a SQL Server, and an Exchange Server.

We're planning on installing Symantec Backup Exec with Exchange Agent... but do we need the remote server agent?

We *would* like to make sure we backup Active Directory, but other than that, there's not much on the two domain controllers that we really need.

Can someone help us evaluate the risks of not deploying the server agent(s)?

(Incidentally, we plan on using SQL's flat file backup tools, and backing up those files, rather than using SQL Agent.)

Thanks...

 

[marflo500]

Hi CathodeRay,

The Remote agent is needed if you want to back-up machines other than the Backup server machine (the machine with Backup exec installed on it). I would advise that you get it in case you get more servers in the future.

Liam

 

[CathodeRay]

So if we use it, will it backup the operating system and Active Directoty? What does it backup, other than mapped drives?

 

[marflo500]

The Remote Server Agent is just an extension that allows your backup server to gain access to your networked machines so that they can be backed-up. You will need to back up the System State so that AD gets backed up.

Check out this thread:

http://www.tek-tips.com/viewthread.cfm?qid=1432708

Hope this helps
Liam

 

[Davetoo]

If you put the Backup software on one of your DC's for instance, then you will need three remote agents, one for the Exchange Server, one for the SQL server, and one for the other DC. You need to be sure you purchase the Exchange and SQL remote agents.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[LawnBoy]

Any server that you want to remotely pull from has to have the remote agent. You will then be able to backup any file that resides on that remote machine. You can backup a workstation without buying a remote agent for it.

You don't have to have the SQL agent. Your plans for the SQL server are fine, I handle my backups the same way.

You can avoid buying the remote agent for your SQL server though. When you setup the database backup job, have the file it creates saved to a different server that has the remote agent installed. That way BE never actually touches the SQL server.

Have you considered whether any files will be open when you try to back them up? You may need the Advanced Open File Option (AOFO). Be sitting down when you see the price of that module...

The stagehand's axiom: "Never lift what you can drag, never drag what you can roll, never roll what you can leave.