Set up Backup Exec Properly i.e. the correct settings to use

The Exchange backup job is really quite simple.  Install the remote agent on the exchange server.  once that is complete, when you setup your backup job, you will have the exchange section of the backup job available to you.  when you click on this it will give you all the options for Exchange backup.

My recommendation is to perform a full backup on exchange everytime you back it up.  the reason for this is so that you have a 100% good backup rather than an incremental or differential.  it also makes certain that the exchange logs are committed to the database and cleaned off the server so that you do not run into space issues.

As for the media set.  Configure it to allow append infinitely.  Overwrite after 6 days.  this will make sure that whatever B2D files are created, are not overwritten until you are ready to do the full backup again.

The backup jobs that will be created will be based off of a selection list.  you must use the same selection list for the full backup and the differential backup jobs.  The reason for this is so that the correct files are backed up at the same time and the corrent method (Full or Differential) is used.  

Create the first job and call it the full backup.  Once this job is in place schedule it for Friday night.  Incase things atake a while utilizing a full backup scenario this will give it the weekend to complete correctly assuming that you do not need 7 day backups.  Makes ure under the general section for this job you make sure that the backup method is "Full - using archive bit."

Now create the second job and label it as Differential.  Make sure that you select the same selection list as the full backup.  In the backup method select "Differential - using archive bit".  This will make sure that your two jobs are using the same method.  Schedule this job to run everyday except for Friday as the full is set to run then.

I did a full backup yesterday but it failed giving an error in the job log stating that some files are corrupt.

This has never happened before. Could you take a look at the job log please & give any advise?

Thank you
Job-Log-BEX-BMSSTORAGE-00060-xml.mht

I will exclude these files but i am a little worried about the Exchange Server files. I have backed up the exchange server files in the past & the backup completed.

Could something else be causing this?

So i'm still setting up backup jobs...

"My recommendation is to perform a full backup on exchange everytime you back it up.  the reason for this is so that you have a 100% good backup rather than an incremental or differential.  it also makes certain that the exchange logs are committed to the database and cleaned off the server so that you do not run into space issues."

I plan on making full backups every time & i was wondering how to set the backup to clean the exchange logs off the server?

I am still worried about the corrupt files & was wondering if i exclude them from the backup selection list it will fix the issue. Some are Exchange files - do you know by looking at the log attached if the exchange files are critical ones?

The files that are tied to exchange in this log are ones that are either temporary files, or are in use by the transport service and will never be backed up.  excluding them in the only way to get a successful backup.  Also in a normal Exchange backup, you do not try to backup the .edb files directly.  these are the exchange databases and are taken care of with the exchange agent when you select the exchange datastore.  

As for the exchange logs, when you choose the exchange datastore, the logs are set to comit automatically as long as you perform a full backup under the exchange section of the backup job.

Ok Excellent its now working so im happy.

One more thing, i would like to back up another server to this server. they are on 2 seperate subnets & domains. I have created a network drive on the one which i would like to backup & tried to create a B2D Folder using the Drive letter & that did not work stating cannot find the path specified.

I then used the URL \\servername\folder name & this did not work saying Access Denied i have created a script to log on to the machine which will back up & it connects to the server with the Domain Administrator Account so should have full rights.

Any help both Servers have Backup Exec 12.5 on them.

Cheers

I have the settings applied in BE Exchange Agent to run full backup & Flush the commited logs.

When i run Exchnage Performance Analyzer i get an error saying Echange has never been backed up.
I thought if the logs were flushed Exchange would notice that it had been backed up??

on the remote server, instead of typing in \\servername\folder name, manually install the remote agent on the server.  it can be found on the backup server in the following folder assuming you selected the defaults.  C:\Program Files\Symantec\Backup Exec\Agents\ and then either the RAWS32 or RAWS 64 based upon whether your server is 32 bit or 64 bit.  You will run either setupaa.cmd or setup aofo.cmd in the RAWS32 folder or setupaax64.cmd or setupaofox64.cmd in the RAWS64 folder.  When the agent installs, you will get an open to publish the server information to a media server.  Make sure you specify the server that has backup exec installed.  At this point that server should show up under the favorite servers when you setup a backup job.


I can't say on the Exchange Performance Analyzer.  I do not use this to verify whether or not backups are performing correctly.  I base my assumption on the backup of the server itself in Backup Exec.

Just looked in that location & the Agent folder was not there.

Do you have to pay extra for the remote agent add on?

We just got the Server Licence & Exchange Agent???

no.  It should be there regardless of whether you purchased the remote agent.

is there a way to get it from installation files or anywhere else?

Cheers

Thank You & Sorry for the Delay