asked on

Tapeware Backup with MS Exchange Server Objects Busy

Hi. I am running Yosemite Tape Backup on a SBS 2003, and after much hassle, I finally have it running my backup every night.

The problem is that the following files on my server are NOT being backed up, as it is saying the objects are busy. It looks like stuff from Exchange and SQL. I have everyone on the network not only log off their computers, but power them down at night (Can't trust people to actually CLOSE all programs.) and I stopped the SQL server. Any advice as to how to get them to backup? These files are pretty important.

One caviat: I am a programmer, not a network admin, so if my responses seem a bit basic I apologize. I was thrust into this position by default when our old Admin left.

The following is my log:

DVDSERVER\C:\Documents and Settings\All Users\Application Data\Microsoft\Network\Downloader
qmgr0.dat : Bkp : 209 - Object is busy
qmgr1.dat : Bkp : 209 - Object is busy

DVDSERVER\C:\Documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\ActivityLog
InboxLOG.txt : Bkp : 209 - Object is busy
OutboxLOG.txt : Bkp : 209 - Object is busy

DVDSERVER\C:\Inetpub\catalog.wci
00000002.ps1 : Bkp : 209 - Object is busy
00000002.ps2 : Bkp : 209 - Object is busy
00010001.ci : Bkp : 209 - Object is busy
cicat.fid : Bkp : 209 - Object is busy
cicat.hsh : Bkp : 209 - Object is busy
CiCL0001.000 : Bkp : 209 - Object is busy
CiP10000.000 : Bkp : 209 - Object is busy
CiP20000.000 : Bkp : 209 - Object is busy
CiPT0000.000 : Bkp : 209 - Object is busy
CiSL0001.000 : Bkp : 209 - Object is busy
CiSP0000.000 : Bkp : 209 - Object is busy
CiST0000.000 : Bkp : 209 - Object is busy
CiVP0000.000 : Bkp : 209 - Object is busy
INDEX.000 : Bkp : 209 - Object is busy
propstor.bk1 : Bkp : 209 - Object is busy
propstor.bk2 : Bkp : 209 - Object is busy

DVDSERVER\C:\Program Files\Exchsrvr\bin
store.fcl : Bkp : 209 - Object is busy

DVDSERVER\C:\Program Files\Exchsrvr\MDBDATA
E00.log : Bkp : 209 - Object is busy
E00tmp.log : Bkp : 209 - Object is busy
tmp.edb : Bkp : 209 - Object is busy

DVDSERVER\C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING\Data
master.mdf : Bkp : 209 - Object is busy
mastlog.ldf : Bkp : 209 - Object is busy
model.mdf : Bkp : 209 - Object is busy
modellog.ldf : Bkp : 209 - Object is busy
msdbdata.mdf : Bkp : 209 - Object is busy
msdblog.ldf : Bkp : 209 - Object is busy
tempdb.mdf : Bkp : 209 - Object is busy
templog.ldf : Bkp : 209 - Object is busy

DVDSERVER\C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING\LOG
ERRORLOG : Bkp : 209 - Object is busy
SQLAGENT.OUT : Bkp : 209 - Object is busy

DVDSERVER\C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data
master.mdf : Bkp : 209 - Object is busy
mastlog.ldf : Bkp : 209 - Object is busy
model.mdf : Bkp : 209 - Object is busy
modellog.ldf : Bkp : 209 - Object is busy
STS_Config.mdf : Bkp : 209 - Object is busy
STS_Config_log.LDF : Bkp : 209 - Object is busy
STS_DVDSERVER_1.mdf : Bkp : 209 - Object is busy
STS_DVDSERVER_1_log.LDF : Bkp : 209 - Object is busy
tempdb.mdf : Bkp : 209 - Object is busy
templog.ldf : Bkp : 209 - Object is busy

DVDSERVER\C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG
ERRORLOG : Bkp : 209 - Object is busy

DVDSERVER\C:\WINDOWS\security\logs
scepol.log : Bkp : 209 - Object is busy

DVDSERVER\C:\WINDOWS\system32\dhcp
dhcp.mdb : Bkp : 209 - Object is busy
DhcpSrvLog-Mon.log : Bkp : 209 - Object is busy
j50.log : Bkp : 209 - Object is busy
j50tmp.log : Bkp : 209 - Object is busy
tmp.edb : Bkp : 209 - Object is busy

DVDSERVER\C:\WINDOWS\system32\inetsrv\History
MBSchema_0000014762_0000000000.x : Bkp : 208 - Object not found
MBSchema_0000014763_0000000000.x : Bkp : 208 - Object not found
MetaBase_0000014762_0000000000.x : Bkp : 208 - Object not found
MetaBase_0000014763_0000000000.x : Bkp : 208 - Object not found

DVDSERVER\C:\WINDOWS\system32\LogFiles\HTTPERR
httperr1.log : Bkp : 209 - Object is busy

DVDSERVER\C:\WINDOWS\system32\msmq\storage
QMLog : Bkp : 209 - Object is busy

DVDSERVER\C:\WINDOWS\system32\wbem\Repository\FS
INDEX.BTR : Bkp : 209 - Object is busy
MAPPING.VER : Bkp : 209 - Object is busy
MAPPING1.MAP : Bkp : 209 - Object is busy
MAPPING2.MAP : Bkp : 209 - Object is busy
OBJECTS.DATA : Bkp : 209 - Object is busy

DVDSERVER\C:\WINDOWS\system32\wins
j50.log : Bkp : 209 - Object is busy
wins.mdb : Bkp : 209 - Object is busy
winstmp.mdb : Bkp : 209 - Object is busy

DVDSERVER\C:\WINDOWS\system32
h323log.txt : Bkp : 209 - Object is busy
hmdebug.log : Bkp : 209 - Object is busy

DVDSERVER\D:\Program Files\Exchsrvr\MDBDATA
priv1.edb : Bkp : 209 - Object is busy
priv1.stm : Bkp : 209 - Object is busy
pub1.edb : Bkp : 209 - Object is busy
pub1.stm : Bkp : 209 - Object is busy

DVDSERVER\F:\Program Files\Microsoft CRM\Help\catalog.wci
00000002.ps1 : Bkp : 209 - Object is busy
00000002.ps2 : Bkp : 209 - Object is busy
00010004.ci : Bkp : 209 - Object is busy
cicat.fid : Bkp : 209 - Object is busy
cicat.hsh : Bkp : 209 - Object is busy
CiCL0001.000 : Bkp : 209 - Object is busy
CiP10000.000 : Bkp : 209 - Object is busy
CiP20000.000 : Bkp : 209 - Object is busy
CiPT0000.000 : Bkp : 209 - Object is busy
CiSL0001.000 : Bkp : 209 - Object is busy
CiSP0000.000 : Bkp : 209 - Object is busy
CiST0000.000 : Bkp : 209 - Object is busy
CiVP0000.000 : Bkp : 209 - Object is busy
INDEX.000 : Bkp : 209 - Object is busy
propstor.bk1 : Bkp : 209 - Object is busy
propstor.bk2 : Bkp : 209 - Object is busy

DVDSERVER\F:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQL0000700005\Build\Indexer\CiFiles
00010008.ci : Bkp : 209 - Object is busy
CiCL0001.000 : Bkp : 209 - Object is busy
CiPT0000.000 : Bkp : 209 - Object is busy
CiSL0001.000 : Bkp : 209 - Object is busy
INDEX.000 : Bkp : 209 - Object is busy

DVDSERVER\F:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQL0000700005\Build\Indexer\NlFiles
00000001.ps1 : Bkp : 209 - Object is busy
00000001.ps2 : Bkp : 209 - Object is busy
CiP10000.000 : Bkp : 209 - Object is busy
CiP20000.000 : Bkp : 209 - Object is busy
CiST0000.000 : Bkp : 209 - Object is busy
DocId.Map : Bkp : 209 - Object is busy
propstor.bk1 : Bkp : 209 - Object is busy
propstor.bk2 : Bkp : 209 - Object is busy

DVDSERVER\F:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQL0000700005
SQL0000700005.Hash.gthr : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.Dir : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h0 : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h0.Dir : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h1 : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h1.Dir : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h3 : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h4A : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h4A.Dir : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h4B : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.h4B.Dir : Bkp : 209 - Object is busy
SQL0000700005.Hash.gthr.idx : Bkp : 209 - Object is busy
SQL0000700005.Idm.gthr : Bkp : 209 - Object is busy
SQL0000700005.Ntfy1.gthr : Bkp : 209 - Object is busy

DVDSERVER\F:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQLServer\GatherLogs
SQL0000700005.189.gthr : Bkp : 209 - Object is busy

ASKER CERTIFIED SOLUTION

Sembee

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

VeeVan

ASKER

I am using a REV drive from Iomega to do my backup on a Windows SBS 2003. Unfortunately, SBS recognizes the Rev as a CD drive, and won't let me use NTbackup. Any advice on how I could get that to work?

Thanks.
V

Sembee

Dump it to a file that happens to be located on the external drive. Simple.

Simon.

VeeVan

ASKER

Can I do that programmatically and automatically? Or do I have to do it manually?

And you're right about it not being Exchange aware. You have to buy ANOTHER program to enable that. Figures.

V

Sembee

The only backup program that I have seen that is Exchange aware "out of the box" is NTBACKUP. All others need to have a module, agent or extra purchased separately for native Exchange support.

For NTBACKUP you should be able to schedule it using the application. Make sure that there something in the drive so that it knows where to look, but once set it should run fine.

For SQL I would configure it to dump the file to a hard disk location first, then schedule the disk transfer for later.

Simon.