ryansoto
asked on
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.f cl in use - skipped.
The item C:\Program Files\Exchsrvr\MESASBS.log \20070725. log in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\AP0 .LOG in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\BF0 .LOG in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00003.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00008.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00009.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0000a.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0000b.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0000c.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0000d.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0000e.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0000f.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00010.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00011.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00012.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00013.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00014.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00015.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00016.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00017.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00018.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00019.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0001a.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0001b.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0001c.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0001d.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0001e.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 0001f.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00021.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\db0 00022.dat in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\DB0 00027.DAT in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\DBR EFS in use - skipped.
The item C:\Program Files\Exchsrvr\mtadata\EV0 .LOG in use - skipped.
The item C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC\LOG\ ERRORLOG in use - skipped.
The item C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING \LOG\ERROR LOG in use - skipped.
The item C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LO G\ERRORLOG in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\{CFF455BD -748A-4052 -8BEE-39DD DFDD0268}_ 4.img in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\{F220ADA5 -2DFC-4D67 -BA75-BA9A DD2931A2}_ 4.img in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_MESASBS_0 1586.xml in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_MESASBS_0 1587.xml in use - skipped.
The item C:\Program Files\VERITAS\Backup Exec\NT\Logs\adamm.log in use - skipped.
The item C:\WINDOWS\WindowsUpdate.l og in use - skipped.
The item C:\WINDOWS\system32\h323lo g.txt in use - skipped.
The item C:\WINDOWS\system32\hmdebu g.log in use - skipped.
The item C:\WINDOWS\system32\LogFil es\HTTPERR \httperr3. log in use - skipped.
The item C:\WINDOWS\system32\msmq\s torage\QML og in use - skipped.
The item C:\WINDOWS\system32\wins\w instmp.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
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.f
The item C:\Program Files\Exchsrvr\MESASBS.log
The item C:\Program Files\Exchsrvr\mtadata\AP0
The item C:\Program Files\Exchsrvr\mtadata\BF0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\db0
The item C:\Program Files\Exchsrvr\mtadata\DB0
The item C:\Program Files\Exchsrvr\mtadata\DBR
The item C:\Program Files\Exchsrvr\mtadata\EV0
The item C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC\LOG\
The item C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING
The item C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LO
The item C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\{CFF455BD
The item C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\{F220ADA5
The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_MESASBS_0
The item C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX_MESASBS_0
The item C:\Program Files\VERITAS\Backup Exec\NT\Logs\adamm.log in use - skipped.
The item C:\WINDOWS\WindowsUpdate.l
The item C:\WINDOWS\system32\h323lo
The item C:\WINDOWS\system32\hmdebu
The item C:\WINDOWS\system32\LogFil
The item C:\WINDOWS\system32\msmq\s
The item C:\WINDOWS\system32\wins\w
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
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.
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
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
ASKER
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?
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?
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.
You should be covered.
ASKER
OK cool. I guess i'll wait to see what happens tonight.
ASKER
These files are still locked...
I guess I try a reboot before the backup process tonight and see if that clears them.
I guess I try a reboot before the backup process tonight and see if that clears them.
Do you have the AOFO option installed?
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.
For these backups select the resource called "Microsoft Information Store".
This will backup both the database and the logs.
ASKER
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?
I'm not sure what you mean by this but we use backup exec 10 for backups.
I assume it uses the agent?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.