# Locked exchange files after image

I imaged my server to a new hard drive last night (acronis true image server 9), everything went fine.  Shortly after I verified email was again running, data was there, etc I started the backup process (backup exec 10)
I looked in the logs this morning and normally a few files are skipped because in use but I got a lot and they are not the normal files that get locked.
The ones that concern me are the exchange files locked
Here is the log

item C:\Program Files\Exchsrvr\bin\store.fcl in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000003.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000008.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000009.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00000a.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00000b.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00000c.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00000d.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00000e.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00000f.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000010.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000011.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000012.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000013.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000014.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000015.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000016.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000017.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000018.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000019.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00001a.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00001b.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00001c.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00001d.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00001e.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db00001f.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000021.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db000022.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\DB000027.DAT in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\DBREFS in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\{CFF455BD-748A-4052-8BEE-39DDDFDD0268}_4.img in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_MESASBS_01586.xml in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_MESASBS_01587.xml in use - skipped.
The item C:\WINDOWS\system32\h323log.txt in use - skipped.
The item C:\WINDOWS\system32\wins\winstmp.mdb in use - skipped.
The .DR file required for Intelligent Disaster Recovery is created/updated.

I assume exchange was running some processes after the image and locked these files.  What are these files and should they unlock themselves after a period of time?
I need to make sure that they will backup tonight in case anything happens.  Thakns for any input
LVL 24
###### Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Commented:
The files such as db000003.dat  are the MS Exchange database files.  They will lock if the database is being altered to ensure data integrity in the database otherwise you can have file corruption.
Commented:
Do you have the exchange agent?

Here's some links discussing the info in my previous post http://support.veritas.com/docs/277230
http://support.veritas.com/docs/276229
http://support.veritas.com/docs/259152
Author Commented:
The exchange agent is there and is in the running status.
The service may not have started after the image?
Basically after the image I booted the machine all looked well so I ran an immediate backup.  Its possible at that point that service wasnt started?
Commented:
It basically boils down to if you are running the agent, then you shouldn't need to do a file level replication on the Exchange data, which is what I see when I look at your output log.

You should be covered.
Author Commented:
OK cool.  I guess i'll wait to see what happens tonight.
Author Commented:
These files are still locked...
I guess I try a reboot before the backup process tonight and see if that clears them.
Commented:
Do you have the AOFO option installed?
Commented:
Still on the first note it appears that you are backing up the exchange through the file system instead of through the agent.

For these backups select the resource called "Microsoft Information Store".

This will backup both the database and the logs.
Author Commented:
Still on the first note it appears that you are backing up the exchange through the file system instead of through the agent.

I'm not sure what you mean by this but we use backup exec 10 for backups.
I assume it uses the agent?
Commented:
No, there is a specific Exchange Agent which is an upgrade to Backup Exec.  you want to run this to backup Information Stores.

Experts Exchange Solution brought to you by