Backup exec 12.5 windows 7 agent

This is my favored method for backing up domain controllers - I'd much prefer to snap up a single ntbackup systemstate file than a bunch of redundant windows system files Add a comment. Active Oldest Votes. Improve this answer. Kara Marfia Kara Marfia 7, 5 5 gold badges 31 31 silver badges 56 56 bronze badges. You posted the same answer while I was typing my response! Have an upvote Under the Windows Systems, the workstations' shares are still checked, however.

Do I need to remove those selections first? Well, you'll always get an error for the backups it tries in the Windows Systems item on machines without an agent, so you probably want to remove those though it won't keep the user-defined job from running. I'll edit above with the step I skipped.

Sam Cogan Sam Cogan GregD GregD 8, 1 1 gold badge 22 22 silver badges 35 35 bronze badges. You are supposed to need an agent for this with Backup Exec Note that I've tried this on a Sign up or log in Sign up using Google.

Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. I already knew the part about Windows Backup, but I cannot use that because the source volume is greater than 2 TB - 4 GB stupid error , which makes a lot of sense.

This HP Data Protector seems to be fully functioning for 60 days, and is Exchange Aware, so I am downloading that to trial it and use it for this purpose. Hopefully it will not be necessary though. I am hoping the exchange database repair goes well and I can move on. We shall see. Like Martin said, what you want to do depends a lot on the version of Exchange you are running. The good news is, sounds like management doesn't doesn't value e-mail backups and restores so you could always erase everything and start a new datastore.

I know what you mean. Oh, they would value it if they didn't have it One of those "why didn't you tell me" type of things. And then I could just produce the emails of my explanation and their refusal to pay for it!

Yeah, we are running Exchange I am liking this HP Data Protector - it actually looks pretty good and since our license is about to expire with Backup Exec this may be a good opportunity. Just for reference r2 and exchange windows backup works again.

You have to backup all the system but it is exchange aware, resets the logs and you only have to restore exchange if that's all you want. You can restore to a recovery DB and then do a single mailbox restore if you need to. Just as a follow up, I will be looking into getting the exchange agent; however, in this case that I didn't have it, Datascope by Lucid8 was a lifesaver.

It helped me recover all of our old database with a process that is so extremely simply it really is almost hard to believe there is not some black-magic going on here! Thanks for all the responses.

Select 'Allow Backup Exec to establish a trust with the servers. Note: 'Restart the remote computer automatically after installing the Veritas Backup Exec Agent for Windows when a restart is required' should only be selected if down time has been planned or is not problematic for the target server s.

Click Install to begin setup. Click Finish to complete the installation.. Click on the round Backup Exec button which is located to the left of the Home tab. Note: The box Save the server list for future remote install sessions enables the names of all of the remote computers and their credentials to be added automatically the next time Backup Exec or any of its options need to be installed to these remote computers.

Enter the Remote computer credentials type the user name and password of an account that has administrative rights on the server. Click Next. Enter the Remote Install Credentials type the user name and password of the account that has administrative rights on the servers.

The destination location for Remote Agent install files can be changed under the Destination Folder section if required. On the Remote Agent Publishing screen: Check the box which says 'Enable remote agent to publish the IP address and name of the remote computer and the version of the Remote Agent to media server'. Click Next when the screen shows Ready to install the Agent for Windows beside the server name s. Click Install to begin the installation.

Wait for the installation to complete and click Finish. An SSL trust relationship will need to be established after a manual installation of the Agent for Windows. This is explained in the following article: How to establish trust for remote servers in Backup Exec 15 and above Click here to go back to the top of this article. Local manual installation using the GUI method When automated push installation of the AWS fails it may be necessary to perform a local installation.

Double-click on Setup. It is also recommended to right-click on the Setup. Click Next on the Welcome screen.