Backup Exec 2010 - Missing mdbdata folder when backing up Exchange 2003 folder

[AyazHoda]

Hi


We have just installed Backup Exec 2010 on windows 2003 server SBS. we tried to back up every thing on different drives (C;E;F;J;H;K)

Drive C: contain Windows folders and other Programs files
Drive E: contains Exchanges 2003 folders and files mdb


Back went fine last night with few execptions

Unable to open following items
C:\Programs Files\Mailtraq\mailtraq.lck-skipped
C:\Programs Files\SAV\SAVRT\0203Nac~.tmp-skipped
C:\windows\Security\tmp.edb.log, dhcp temp, wins temp file


We also notice it didn't back up following files in E: Drive exchange folder
\mdbdata\priv1.edb
\mdbdata\priv1.stm

And when backup storage folder it creates new files ends up with mq extension.

Questions

Why Backup Exec  did not back up files on C drive and skipped

Why Backup Exec did not back up files in exchange 2003 folder

Regards

Ayaz Hoda

[AyazHoda]

Just to add up further to my topic

we didn't select Microsoft Information Store ( First Storage Group), we did select all drives only

[Colin_Weaver]

Certain items in the file system are excluded automatically from a flat file backup of the file system if they should be backed up using a specific mechanism - for instance items in the System State, Items protected by the Exchange Agent and items protcted by the SQL Agent (there are others too)

This is known as "Active File Exclusion" and will exclude the files in question without making any reference to it in the job logs. - this will explain your Exchange 2003 missing files which should be backed up using the Exchange agent (via the Information Store icons in your Backup Selection lists)

The files you mention on the C: drive are active at the time of the backup and Backup Exec therefore skips them. - the one under SAVRT (Symantec Anti-Virus Real Time) is probably not critical as it appears to be a temp file. The others may well be temp files and not critical either but as they are part of components from other vendors you may need to check with them.

[Colin_Weaver]

You can add to the exclusions lists if you are sure a file (or folder) does not need protecting by a backup which will remove the skipped files warnings.

Each of the entities you list is a different backup set - although multiple sets can usually be selected for backup in a single job. (note in this context a backup set is a drive letter or a database etc - so C: D: System State, Shadow Copy Components and an Exchange Information Store counts as 5 backup sets)

Also  you can't get the server back in one pass with Backup Exec - you will have to recover the operating system (so drives, System State and Shadow Copy), then recover the sets for Exchange, SQL, Sharepoint and EV data (in separate jobs) - which could be a fair amount of 'hassle'

As the SBS license for Backup Exec will not cover protecting EV - it is likely you will need to use an EV Agent license - and you may need to confirm when you arrange for this whether or not it can be installed on the SBS license for Backup Exec or whether you will have to use a standard core license for Backup Exec and therefore also need the Sharepoint, SQL and Exchange agent licenses.

[AyazHoda]

What must be done to include Exchange and SQL file.

Is there any way on Backup Exec 2010 to disable Active File Exclusions.

Regards

Ayaz

[AyazHoda]

Hi Colin

I just amend my question ...

Is there any way on Backup Exec 2010 to disable Active File Exclusions.

Regards

Ayaz

[Colin_Weaver]

well there is a way (a registry modification) - but you would have to Shutdown the Exchange and SQL Services before running your backup job (every day) as
a) The files will be held open so you will just see more skipped files errors - and this time they WILL BE IMPORTANT files.
b) You can get inconsistent databases when it comes to the restore which would almost certainly require assistence from Microsoft to get them running again in the event of a disaster.

[Colin_Weaver]

For completeness How to disable Active File Exclusion = http://entsupport.synmantec.com/docs/259152

However I strongly recommend that you understand the importance of maintaining database consistency and the effect of skipping an open  file relating to a critical database before you continue down this route as Symantec may be unable to help you if you backup using this method and are then unable to access your data after a restore.

[AyazHoda]

Thanks Colin for your assitance!

[CraigV]

Hi there,

Why not look into using the Exchange and SQL agents? All you would need to do is to select the Information Store and SQL instances...much easier when backing up and restoring. THat means you can backup Exchange and clear your logs, and do the same with SQL.

Laters!

[Colin_Weaver]

Nice one Craig - I forgot to mention that clearing transaction logs happens with an agent driven backup - so a useful extra point that is important.