Dear all,
has anyone come across the following eventlog error message while backing
up a W2K3 client?
Volume Shadow Copy Service error: Unexpected error calling routine
MoveFileExW
TSM backups work, nothing in the TSM error log or schedlog. No change,
client has been working happily for quite a
So, are you saying that I always need to delete and redefine all
connections to the drive being replaced?
I have just tried this and will see if it works.
From:
Bob Levad ble...@winnebagoind.com
To:
ADSM-L@VM.MARIST.EDU
Date:
07/10/2009 04:56 PM
Subject:
Re: [ADSM-L] Replacing tape drives (or
Windows 2008 64-bit
Exchange 2007
TSM client 5.5.2.0
TDP Exchange 5.5.1.0
Never seen this one before. I am able to install and customize the TDP agent
and run commands like QUERY TSM, QUERY TDP, but when I try QUERY EXCHANGE
all I get is:
C:\Program Files\Tivoli\TSM\TDPExchangetdpexcc
Zoltan,
You don't need to delete and redefine all connections to the drive being
replaced. All you need to do before a drive change is to make sure that
the drive is not used and that you take the path to the drive offline.
Once IBM replaces the drive (using the same S/N as the replaced drive),
Hey Bill,
The reason you can't query exchange is because the Microsoft Exchange
Information Store service is not running. That service needs to be
started for TDP for Exchange to run; start that service and everything
will be smth.
BERTAUT TCHUISE
Storage Support Administrator
Legg Mason
Are you running this on a cluster? Try adding the following to the
command:
/EXCSERVER=exc-server-name
where exc-server-name is the name of your Exchange Server.
Thanks,
Del
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on
Well, that didn't do it.
Completely deleted and redefined the paths to this drive and the drive
itself. None of the library-client TSM servers can access the
replacement drive eventhough its serial-number is now the same as the
original. The server that owns the drive (and was rebooted) can
That is right, of course, you don't NEED to work with anything except the
problem drive.
The only reason we drop the whole library and re-define it is that it is
easy once the script is written and you don't need to be concerned with what
was changed. Everything will re-detect just fine if all
Well then I must have some other problem or am missing something.
Even deleting and redefining did not make it work on the non-libraryowning
servers. All of the paths are defined with autodetect.
I tested with my 6.1 test server. Even stopping and restarting both
lin_taped and the TSM server
