The Data Protection client interacts closely with the backup-archive client (DSMAGENT). The client completes all of the Virtual Shadow Copy Service (VSS) operations. The first step is to determine whether the problem is with the Microsoft VSS service or with the Tivoli® Storage Manager.
Volume Shadow Copy Service (VSS) Information
--------------------------------------------
Writer Name : Microsoft Exchange Writer
Local DSMAgent Node : SERVERA
Writer Status : Online
Selectable Components : 4
If the TDPEXCC QUERY
EXCHANGE command does not return all of this information,
you might have a proxy configuration problem. Contact the Tivoli Storage
Manager server administrator
to have the correct server GRANT PROXY commands
that are issued to enable proxy authority for nodes. If all of the
information returned to you seems correct, proceed to the next step. VSSADMIN LIST WRITERS
VSSADMIN LIST PROVIDERS
VSSADMIN LIST SHADOWS
The VSSADMIN LIST SHADOWS command does not list shadow copies of SAN-attached volumes.
The vssadmin tool uses Microsoft Software Shadow Copy provider to list the shadow copies that are created.
diskshadow>set verbose on
diskshadow>begin backup
diskshadow>add volume f: (database volume)
diskshadow>add volume g: (log volume)
diskshadow>create
diskshadow>end backup
diskshadow>list shadows all
diskshadow>delete shadows all
diskshadow>list shadows all
Volumes f: and g: represent the Exchange database and log volumes. Repeat theDISKSHADOW commands four times and verify that the Windows event log file contains no errors.
diskshadow>set context persistent
diskshadow>set verbose on
diskshadow>begin backup
diskshadow>add volume f: (database volume)
diskshadow>add volume g: (log volume)
diskshadow>create
diskshadow>end backup
diskshadow>list shadows all (this might take a few minutes)
diskshadow>delete shadows all
diskshadow>list shadows all
Volumes f: and g: represent the Exchange database and log volumes. Repeat the diskshadow commands four times and verify that the Windows event log file contains no errors.
diskshadow>set context persistent
diskshadow>set option transportable
diskshadow>add volume f: (database volume)
diskshadow>add volume g: (log volume)
diskshadow>set metadata c:\metadata\exchangemeta.cab
(the path where you want the metadata stored)
diskshadow>create
You must copy the exchangemeta.cab file
from the source server to the offload server. After you copy the file,
issue the following commands:diskshadow>load metadata newpath/exchangemeta.cab
diskshadow>import
diskshadow>list shadows all (this might take a few minutes)
diskshadow>delete shadows all
Volumes f: and g: represent the Exchange database and log volumes. Repeat the diskshadow commands four times and verify that the Windows event log file contains no errors.
If all tests pass, continue to Step 3.
See the diskshadow documentation for the specific commands for performing backups.
If you can re-create the problem, it most likely is a general VSS issue. See the Microsoft Knowledge Database for information. If your operation passes successfully with diskshadow, it most likely is a Tivoli Storage Manager or Data Protection for Exchange client problem.