|
Configure TSM for Mail Data Protection for
Exchange 6.1.3.1 |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This document will take
you through a basic setup for Data Protection for Exchange 6.1.3.1. For more
configuration options please refer to the Admin guide provided by IBM. Table of Contents 1. Installing TSM for Mail
6.1.3.1 2.1.1. Register
TDP for Exchange Node 2.1.2. Register
TDP for Exchange Proxy Node 2.1.3. Grant
Proxy Authority to NODE_A 2.1.4. Build
TSM for Mail option file 2.1.5. Build
TSM BA Client option file 2.1.6. Build
TSM for Mail Configuration 2.2. Configuration Using Function Manager 3. Configuring TSM for Mail
6.1.3.1 on the Client Machine 3.1.1. Remove
"TSM Client Acceptor Daemon" and "TSM Remote Agent"
services if exist 3.1.2. Install
"TSM Client Acceptor Daemon" service 3.1.3. Install
"TSM Remote Agent" service 3.1.4. Check
the TSM CAD and TSM AGENT services 3.2. Configuration Using Function Manager 5.1. Software and Operating system requirements 5.1.1. Available features listed by Exchange Server
version 6.1. Known Issues and Limitations 1.1.
Silent Install
To
perform a silent install run the following command replacing the INSTALLDIR,
and ouput file with the your
own values. Setup.exe /s /v"INSTALLDIR=\"C:\Program
Files\Tivoli\DPforMail\"
ADDLOCAL=\"Client\" TRANSFORMS=\"1033.mst\" /qn /l*v \"C:\Program Files\Tivoli\DPforMail\Install.log\" 1.2.
Manual Install
Run Setup.exe and follow the prompts. Below are the
screens that would appear.
The TSM
Administrator needs to register the nodes and grant access to the Proxy nodes.
They also have to create the option files for both the TSM for Mail and TSM
BA client and update the TdpExc.cfg file with the
appropriate LOCALDSMAgentnode. 2.1.
Manual Configuration
2.1.1.
Register TDP for Exchange Node
Register Node NODE_A xxxxxxxx Domain=STANDARD Contact='' Cloptset='OptionSetName' BackDelete=Yes
MAXNUMMP=2 KeepMP=Yes EXAMPLE: Register Node SERVER1_TDPEXC xxxxxxxx Domain=STANDARD Contact=''Cloptset='OptionSetName' BackDelete=Yes
MAXNUMMP=2 KeepMP=Yes 2.1.2.
Register TDP for Exchange Proxy Node
Register Node NODE_A xxxxxxxx Domain=STANDARD Contact='' Cloptset='OptionSetName' BackDelete=Yes
MAXNUMMP=2 USERID=NONE KeepMP=Yes EXAMPLE: Register Node SERVER1_TEST xxxxxxxx Domain=STANDARD Contact='' Cloptset='OptionSetName' BackDelete=Yes
MAXNUMMP=2 USERID=NONE KeepMP=Yes 2.1.3.
Grant Proxy Authority to NODE_A
Grant Proxynode
target=SERVER1_TDPEXC agent=SERVER1_TEST 2.1.4.
Build TSM for Mail option file
NodeName
SERVER1_TDPEXC TCPServerAddress x.x.x.x TCPPort
1500 PasswordAccess Generate 2.1.5.
Build TSM BA Client option file
NodeName
SERVER1_TEST TCPServerAddress x.x.x.x TCPPort
1500 PasswordAccess Generate 2.1.6.
Build TSM for Mail Configuration
Edit
the TdpExc.cfg file TDPExc.cfg LASTPRUNEDate
04/07/2011 11:16:57 MOUNTWait
Yes BACKUPMETHod
VSS TEMPLOGRestorepath
TEMPDBRestorepath
CLIENTACcessserver
LOGFile tdpexc.log LOGPrune 60 LANGuage
ENU BACKUPDESTination TSM LOCALDSMAgentnode
SERVER1_TEST REMOTEDSMAgentnode
STOREMAILBOXInfo NO
2.2.
Configuration Using Function Manager
Function
Manager can be used to automate most of the steps found in section 2.1 above.
It will perform all these tasks including building the option and
configuration files. ·
Select
TDP from Category ·
Select
Configure TDP for Exchange 6.1.2 from available functions ·
Enter
your TSM Admin ID and Password ·
Select
the TSM server to be used ·
Enter
the Exchange server name ·
Enter
the AppCode. Usually PR00 ·
Enter
a password for the TSM nodes ·
Click
on GO Example:
The following
steps needs to be performed on the client machine. 3.1.
Manual Configuration
3.1.1.
Remove "TSM Client Acceptor Daemon" and
"TSM Remote Agent" services if exist
Dsmcutil remove /name:"TSM
CAD" Dsmcutil remove /name:"TSM
AGENT" 3.1.2.
Install "TSM Client Acceptor Daemon" service
Dsmcutil install CAD /name:"TSM CAD" /node:NODE_A_PROXYAGENT /password:xxxxxxxx
/optfile:dsm.opt /autostart:yes /startnow:yes 3.1.3.
Install "TSM Remote Agent" service
Dsmcutil install remoteagent /name:"TSM
AGENT" /node:NODE_A_PROXYAGENT /password:xxxxxxxx /optfile:dsm.opt
/partnername:"TSM CAD" 3.1.4.
Check the TSM CAD and TSM AGENT services
3.2.
Configuration Using Function Manager
Function
Manager can be used to automate most of the steps found in section 2.1 above.
It will perform all these tasks including installing the TSM services. Run
Function Manager from the client machine. ·
Select
TDP from Category ·
Select
“Configure TDP for Exchange 6.1.2 on the Client Server” from available
functions ·
Select
the path to the configuration files ·
Click
on GO Example:
3.3.
Schedule the backups
Schedule Task: Replace
the Time and Mailbox Database names with the appropriate values. Exchange 2010: Schtasks /Create /SC DAILY /ST 21:00:00 /TN Exchange_Backup
/TR "C:\program file\tivoli\tsm\TDPExchange\DPExcBack.bat
EXC_BACKUP """MailboxDatabaseXX1,MailboxDatabaseXX2"""
FULL """C:\program file\tivoli\tsm\TDPExchange\DSM.opt"""" OR Schtasks /Create /SC DAILY /ST 21:00:00 /TN Exchange_Backup
/TR "C:\program file\tivoli\tsm\TDPExchange\DPExcBack.bat
EXC_BACKUP """MailboxDatabaseXX1,MailboxDatabaseXX2"""
FULL Dsm.opt Exchange 2003: Schtasks /Create /SC DAILY /ST 21:00:00 /TN Exchange_Backup
/TR "C:\program file\tivoli\tsm\TDPExchange\DPExcBack.bat
EXC_BACKUP “””First Storage Group””” FULL Dsm.opt OR Schtasks /Create /SC DAILY /ST 21:00:00 /TN Exchange_Backup
/TR "C:\program file\tivoli\tsm\TDPExchange\DPExcBack.bat
EXC_BACKUP * FULL Dsm.opt 4.
Samples Output
4.1.
Sample Backup Output
========================================================================= Request : QUERY
TSM TSM
Options File :
C:\program file\tivoli\tsm\TDPExchange\dsm.opt TSM
Nodename Override : ========================================================================= Request : QUERY
EXCHANGE Exchange
Server : (default) ============================================================ Request : VSS
BACKUP Component
List : 'MailboxDatabaseXX001', 'PublicFolderDB', 'MailboxDatabaseXX001' Backup
Type : full Backup
Destination : TSM Local
DSMAGENT Node
: SERVER1_ TEST Offload
to Remote DSMAGENT Node : ------------------------------------------------------------ Server
: x.x.x.x ------------------------------------------------------------ VSS Backup operation completed with rc = 0 Files Examined : 4290 Files Completed : 4290 Files Failed : 0 Total Bytes : 63927853523 ========================================================================= Request : QUERY EXCHANGE Exchange
Server Override : EXCSERVER1 ========================================================================= 5.1.
Software and Operating system requirements
5.1.1.
Available features listed by Exchange Server version
6.1.
Known Issues and Limitations
Known Issues and Limitations: Version 2.2.x FlashCopy® Manager for Microsoft Exchange & V6.1.x Data Protection for Microsoft Exchange Server https://www-304.ibm.com/support/docview.wss?uid=swg21319956&wv=1 6.2.
Troubleshooting
Error: ACN0501E
Invalid Proxy Configuration Detected: Target
Node 'NODE_A' is not listed as a valid node to proxy to for Node Name
'NODE_A_PROXYAGENT'. ***
Request being sent to cancel the current command. ACN0004E
An unknown error has been detected. Solution: Ensure
that the LOCALDSMAgentnode option specified in the config file is a valid Proxy Node. It should be set in
the dsm.opt file in the TSM BAClient
and exist on the TSM server. Error: ANS1532E
(RC5722) Proxy Rejected: Proxy authority has not been granted to this node. ACN5060E
A Tivoli Storage Manager API error has occurred. Solution: Issue
the following command to grant access… Grant
Proxynode target=NODE_A agent=NODE_A_PROXYAGENT Error: ACN0515E
Invalid DSMAGENT Node configuration found for node 'NODE_A_PROXYAGENT'. ACN0004E
An unknown error has been detected. Or
ACN0520E
Failed to connect to Local DSMAGENT Node 'SERVER1_ PROXYAGENT' at address:port '10.x.x.x:9761'.
Verify that the TSM Client Acceptor Daemon (CAD) is installed, configured,
and running properly. Or ANS5252E
TSM attempted to execute a system command which failed. command :
"C:\Program Files\TSM\baclient\excvssic.exe"
C:\adsm.sys\vss_staging\SERVER1_TDPEXC_TEST\TSMSERVER1.x.x.x\20110518120724\382adebd-0265-44d0-a687-d6bc124b666f_Audit.txt
rc :
-1073741502 ANS1327W
The snapshot operation for '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\'
failed with error code: -1073741502. ACN0262E
Errors occurred while processing the VSS operation. Examine the Windows Event
Logs and DSMERROR.LOG for additional details. VSS
Backup operation completed with rc = 450 Files
Examined : 0 Files
Completed : 0 Files
Failed : 2 Total
Bytes : 0 ACN0519E
The VSS operation failed with rc = 450. ACN5815E
The VSS operation failed with rc = 450. Solution: Install
the “TSM Client Acceptor Daemon” service and ensure it is started. Example: dsmcutil remove /name:"TSM
CAD" dsmcutil install CAD /name:"TSM
CAD" /node:NODE_A_PROXYAGENT /password:xxxxxxxx /optfile:dsm.opt
/autostart:yes /startnow:yes Result: …\tsm\baclient>dsmcutil remove
/name:"TSM CAD" TSM
Windows NT Client Service Configuration Utility Command
Line Interface - Version 6, Release 2, Level 2.0 (C)
Copyright IBM Corporation, 1990, 2010, All Rights Reserved. Last
Updated Dec 2 2010 TSM
Api Version 6.2.2 Command:
Remove TSM Client Service Machine:
SERVER1(Local Machine) Registry
key 'SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Scheduler
Service' not found. Removing
TSM Client Service 'TSM CAD' ... The
specified service doesn't exist . The
service was not removed. C:\Program
Files\tsm\baclient>dsmcutil
install CAD /name:"TSM CAD" /node:
SERVER1_PROXYAGENT /password:xxxxxxxx /optfile:dsm.opt TSM
Windows NT Client Service Configuration Utility Command
Line Interface - Version 6, Release 2, Level 2.0 (C)
Copyright IBM Corporation, 1990, 2010, All Rights Reserved. Last
Updated Dec 2 2010 TSM
Api Version 6.2.2 Command:
Install TSM Client Service Machine:
SERVER1(Local Machine) Installing
TSM Client Service: Machine : SERVER1 Service Name : TSM CAD Client Directory : C:\Program Files\tsm\baclient Automatic Start : no Logon Account : LocalSystem The
service was successfully installed. Creating
Registry Keys ... Updated
registry value 'ImagePath' . Updated
registry value 'EventMessageFile'
. Updated
registry value 'TypesSupported' . Updated
registry value 'TSM CAD' . Updated
registry value 'ADSMClientKey' . Updated
registry value 'OptionsFile' . Updated
registry value 'ClientNodeName' . Generating
registry password ... Authenticating
TSM password for node SERVER1_PROXYAGENT ... Connecting
to TSM Server via client options file 'dsm.opt' ... Password
authentication successful. The
registry password for TSM node SERVER1_PROXYAGENT has been updated. Error: ANS2619S
(RC3026) The Client Acceptor Daemon was unable to start the Remote Client
Agent. ***
Request being sent to cancel the current command. ***
Request being sent to cancel the current command.
Solution: Install
the “TSM Remote Agent” service. Example: dsmcutil remove /name:"TSM
AGENT" dsmcutil install remoteagent /name:"TSM AGENT" /node:NODE_A_PROXYAGENT
/password:xxxxxxxx /optfile:dsm.opt
/partnername:"TSM CAD" TIP: Make sure that the /OptFile option is set to DSM.OPT as seen above. Result: C:\Program
Files\tsm\baclient>dsmcutil
install remoteagent /name:"TSM
AGENT" /node: SERVER1_PROXYAGENT /password:xxxxxxxx
/optfile:dsm.opt /partnername:"TSM
CAD" TSM
Windows NT Client Service Configuration Utility Command
Line Interface - Version 6, Release 2, Level 2.0 (C)
Copyright IBM Corporation, 1990, 2010, All Rights Reserved. Last
Updated Dec 2 2010 TSM
Api Version 6.2.2 Command:
Install TSM Client Service Machine:
SERVER1(Local Machine) Locating
partner client acceptor service 'TSM CAD' ... Installing
TSM Client Service: Machine : SERVER1 Service Name : TSM AGENT Client Directory : C:\Program Files\tsm\baclient Automatic Start : no Logon Account : LocalSystem Partner Name : TSM CAD The
service was successfully installed. Creating
Registry Keys ... Updated
registry value 'ImagePath' . Updated
registry value 'EventMessageFile'
. Updated
registry value 'TypesSupported' . Updated
registry value 'TSM AGENT' . Updated
registry value 'ADSMClientKey' . Updated
registry value 'OptionsFile' . Updated
registry value 'ClientNodeName' . Updated
registry value 'PartnerName' . Updated
Partner Client Acceptor registry value 'PartnerName'
. Generating
registry password ... Authenticating
TSM password for node SERVER1_PROXYAGENT ... Connecting
to TSM Server via client options file 'dsm.opt' ... Password
authentication successful. The
registry password for TSM node SERVER1_PROXYAGENT has been updated. The
remote agent can be started by the client acceptor only. /startnow:yes is ignored. Error: ANS1353E
(RC53) Session rejected: Unknown or
incorrect ID entered ***
Request being sent to cancel the current command. ACN5060E
A Tivoli Storage Manager API error has occurred. OR
ACN0515E
Invalid DSMAGENT Node configuration found for node 'NODE_A_PROXYAGENT' Solution: Ensure
you do not specify “USERID=NONE” when registering the TDP node. Example: Incorrect: Register
Node NODE_A xxxxxxxx Domain=STANDARD Contact='' Cloptset='OptionSetName' BackDelete=Yes MAXNUMMP=2 USERID=NONE
KeepMP=Yes Correct: Register
Node NODE_A xxxxxxxx Domain=STANDARD Contact='' Cloptset='OptionSetName ' BackDelete=Yes MAXNUMMP=2 KeepMP=Yes Error:
ANS1535E
(RC5705) Proxy Rejected: ASNODENAME and NODENAME are identical. Solution: Ensure
TSM for Mail option file NodeName is that of the
Primary nodes. Example; NodeName
SERVER1_TEST TCPServerAddress x.x.x.x TCPPort 1500 PasswordAccess Generate And
TSM BA Client option file’s NodeName is that of the
Proxy node and the AsNodeName is that of the
Primary node. Example; NodeName
SERVER1_ PROXYAGENT AsNodeName
SERVER1_TEST TCPServerAddress x.x.x.x TCPPort 1500 PasswordAccess Generate Error:
Solution: Ensure
you are logged on with an account that has permissions to access Exchange. Error: While
performing a Restore INTO another container the following errors were
encounter. Backup(s)
to be restored: <Logs
: VSS : full : 04/11/2011 14:22:00> <File
: VSS : full : 04/11/2011 14:22:00> ANS1410E
(RC210) Unable to access the network path.
Solution: 1. If you are using “AsNodeName” in
the TSM Baclient option file, remove it and recycle
the “TSM CAD” service. When
the AsNodeName value is set TSM stores the objects
by this name and the file space would look like \\SERVER1_TEST\f$\.... Instead of \\SERVER1\f$\ TRACES: In
the TDP for Exchange Dsm.opt file add the following
trace parameters: TRACEFILE TDP_Trace.out
TRACEFLAGS Service Api In
the TSM Baclient Dsm.opt
file add the following trace parameters: TRACEFILE TSM_Trace.out TRACEFLAGS Service Api Start
TDP GUI with… Tdpexc.exe /TRACEFILE=TDP_Process_trace.out
/TRACEFLAG=service,api The
following lines would appear in one of these trace files. 05/10/2011 14:07:49.824 [007336] [11668] : session.cpp (1554): Length:
417 Code: 000000B5 Type:
<- FSQryRespEnhanced 05/10/2011 14:07:49.824 [007336] [11668] : cufs.cpp (1644): cuGetFSQryResp:
fsName: '\\ server1_test \f$', fsID:
4, fsType: 'NTFS', dirDelimiter:
'\' …… 05/10/2011 14:12:29.885 [007336]
[14728] : dsfifo.cpp ( 589): fifoQgetNextWaitNoTS(1c962f10):
Next object is available. 05/10/2011 14:12:29.885 [007336]
[14728] : dsfifo.cpp ( 242): fifoQchangeWaitTime(1c962f10):
wait time 5953, change 157 05/10/2011 14:12:29.885 [007336]
[14728] : circq.cpp ( 248): Q 1c92e3f0, poped 1c96376c, count 0, top index 5 - 0, bot index 5 - 0 05/10/2011 14:12:29.885 [007336]
[14728] : dsfifo.cpp ( 634): fifoQgetNext(1c962f10):
Giving entry 1c96376c, but next entry is NULL. 05/10/2011 14:12:29.885 [007336]
[14728] : dsfifo.cpp ( 644): fifoQgetNext(1c962f10):
Giving entry 1c96376c, rc 0. 05/10/2011 14:12:29.885 [007336]
[14728] : client2client.cpp (1338):
Exit C2C::C2CRecvVerbBuffer() with rc = 0 05/10/2011 14:12:29.885 [007336]
[14728] : client2client.cpp (1477):
Entering C2C::C2CGetVerbBuffer() 05/10/2011 14:12:29.885 [007336]
[14728] : client2client.cpp (1487):
Exit C2C::C2CGetVerbBuffer() with verbBuff =
1f7f0068 05/10/2011 14:12:29.885 [007336]
[14728] : iccutxn.cpp ( 234): iccuUnpackEndTxn
Entering... 05/10/2011 14:12:29.885 [007336]
[14728] : iccutxn.cpp ( 256): iccuUnpackEndTxn:
Exiting, rc=<0>... 05/10/2011 14:12:29.885 [007336]
[14728] : tsmproxy.cpp (1672): tsmProxyGet
EXIT: rc = >210<. 05/10/2011 14:12:29.885 [007336] [14728]
: dsmmsg.cpp ( 731): dsmRCMsg
ENTRY: tsmHandle=1 rc: 210 msg : 000000001EA6FBB0 05/10/2011 14:12:29.885 [007336]
[14728] : DccRCMap.cpp ( 195): Enter DccRCMap::ccMap:
rc = 210 05/10/2011 14:12:29.885 [007336]
[14728] : dsmmsg.cpp (1129): tsmHandle=1
rc: 210 msg :
>ANS1410E (RC210) Unable to access
the network path. 05/10/2011 14:12:29.885 [007336]
[14728] : amsglog.cpp ( 427): nlLogPrintf:
msg number = 1410 05/10/2011 14:12:29.885 [007336]
[14728] : GlobalRC.cpp ( 326): msgNum =
1410 changed the Global RC. 05/10/2011 14:12:29.885 [007336]
[14728] : GlobalRC.cpp ( 327): Old values: rc = 0, rcMacroMax = 0, rcMax = 0. 05/10/2011 14:12:29.885 [007336]
[14728] : GlobalRC.cpp ( 341): New values: rc = 12, rcMacroMax = 12, rcMax = 12. 05/10/2011 14:12:29.885 [007336]
[14728] : cuopt.cpp ( 530): return from nlLogPrintf: 05/10/2011 14:12:29.885 [007336]
[14728] : cuopt.cpp ( 531): msg length :
00044 05/10/2011 14:12:29.885 [007336] [14728]
: cuopt.cpp ( 532): arg num : 00000 05/10/2011 14:12:29.885 [007336]
[14728] : cuopt.cpp ( 533): msg size : 00044 05/10/2011 14:12:29.885 [007336]
[14728] : cuopt.cpp ( 534): severity
: 0 05/10/2011 14:12:29.932 [007336]
[14728] : tsmproxy.cpp ( 363): tsmProxyTerminate
ENTRY: tsmHandle=1 proxyHandle
=1 05/10/2011 14:12:29.932 [007336]
[14728] : client2client.cpp (1401):
Entering C2C::C2CEndSession() with handle = 1 05/10/2011 14:12:29.932 [007336]
[14728] : dsfifo.cpp ( 350): fifoQinsert(1c9637c0):
Posting that next object available. 05/10/2011 14:12:29.932 [007336]
[14728] : dsfifo.cpp ( 355): fifoQinsert(1c9637c0):
Queue insert of entry deadbeef, return rc of 0 In
looking at the trace this shows the failure is at the windows OS. The
processing looks at: Object 'F:\Recovery\EXCDB1' exists. It
then attempts to use the UNC name to access this file/location: Opening
file '\\server1_test\f$\Recovery\ EXCDB1\MailboxDatabaseNA002.edb However
this fails with: TransWin32RC():
Translated Win32 RC 53 (0x00000035) from HlOpen(): GetFileAttributes to TSM RC 210 The
RC=53 from windows is: Error code 53:
ERROR_BAD_NETPATH - The network path was not found.
Or 2. Run the QUERY PROXYNODE command on
the TSM Server to verify that the proxy relationships are setup
correctly. Check
that the administrative user exists on the TSM Server with the same name as
the exchange node. For
example when you run the QUERY ADMIN command, you should see within the list
the name:
SERVER1_TEST
Set
the IP address for the client on the TSM Server ·
On
the TSM Server run the command: QUERY NODE SERVER1_TDPEXC_TEST F=D ·
Check
if the HL_ADDRESS and LL_ADDRESS are set for the SERVER1_TEST node. If
not, issue this command to update it: Update
node SERVER1_TDPEXC_TEST HLADDRESS=ClientIPAddress
LLADDRESS=1501 ANS8000I
Server command: 'Update node SERVER1_TDPEXC_TEST HLAddress=10.x.x.x
LLAddress=1501' ANR2063I
Node SERVER1_TDPEXC_TEST updated. ANS8002I
Highest return code was 0. Check
the HL and LL address for the Proxy agent node ·
On
the TSM Server run the command: QUERY NODE SERVER1_TDPEXC_PROXYAGENT F=D If
they are not already set issue this command to update them: Update
node SERVER1_TDPEXC_TEST_PROXYAGENT HLADDRESS=ClientIPAddress
LLADDRESS=1501 ANS8000I
Server command: 'Update node SERVER1_TDPEXC_TEST_PROXYAGENT HLAddress=10.x.x.x LLAddress=1501' ANR2063I
Node SERVER1_TDPEXC_TEST_PROXYAGENT updated. ANS8002I
Highest return code was 0. Error:
Solution: The
id used to perform the requested function is not authorized. Make sure the ID
is assigned the appropriate roles. Error: During
a backup DP for Mail crashes with the following message.
Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: tdpexc.exe P2: 6.1.3.1 P3: 4d3e1aab P4: KERNELBASE.dll P5: 6.1.7601.17514 P6: 4ce7c78c P7: e0434f4d P8: 000000000000a49d P9: P10: Attached files: These files may be available here: C:\Users\excadmin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_tdpexc.exe_edd5533ce41060b3bb6228b6465c54cce5cca16_1fe5d0a6 Analysis symbol: Rechecking for solution: 0 Report Id:
69b2b9f6-8ae6-11e0-8517-00505692253d Report Status: 0 Application Event Log: Faulting application name:
tdpexc.exe, version: 6.1.3.1, time stamp: 0x4d3e1aab Faulting module name: KERNELBASE.dll,
version: 6.1.7601.17514, time stamp: 0x4ce7c78c Exception code: 0xe0434f4d Fault offset: 0x000000000000a49d Faulting process id: 0x9dc Faulting application start time:
0x01cc1ef293cf59ff Faulting application path: C:\Program
Files\EXCAgent\TDPExchange\tdpexc.exe Faulting module path:
C:\Windows\system32\KERNELBASE.dll Report Id:
69b2b9f6-8ae6-11e0-8517-00505692253d Solution: Add
the following option to the Data Protection Config
file (tdpexc.cfg): STOREMAILBOXInfo NO This
will stop the mailbox history from being queried or saved by Data Protection.
This is a workaround. Investigation by Microsoft support states that: "The behavior is
by design. KB833789 was released to describe the symptom and provide the
solution to get around it. The solution was released to improve the API's
usability. http://support.microsoft.com/kb/833789" The
solution in the KB833789 gave application author the ability to add waitForPagedSearchData="true" to the app config file. This setting causes S.DS to continue to
retry retrieving data from the server when error code 0x800700EA is
encountered. Without this the app must
handle this condition and retry.
Authors must decide whether they want the ability to have control over
when the search times out ( app handles error code )
or not.
TSM
development doesn't believe this is a bug in their code because its changed behavior from Microsoft, and they don't know
if/when they'll change the behavior again. Instead, they'll write a technote on this topic.
To workaround this Active Directory limitation, you need to add the
following to your tdpexcc.exe.config and tdpexc.exe.config files: <configSections>
<section name="system.directoryservices" type="System.DirectoryServices.SearchWaitHandler, System.DirectoryServices, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
/> </configSections> <system.directoryservices> <DirectorySearcher
waitForPagedSearchData="true" /> </system.directoryservices> NOTE. A customer should specify in the
records a Version and PublicKeyToken of system.directoryservices assembly that he is running. In
the end, your tdpexc.exe.config and tdpexcc.exe.config should look like:
<?xml version="1.0" encoding="utf-8"?> <configuration> <configSections> <section name="system.directoryservices" type="System.DirectoryServices.SearchWaitHandler, System.DirectoryServices, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
/>
</configSections> <system.directoryservices> <DirectorySearcher
waitForPagedSearchData="true" /> </system.directoryservices> <runtime> <generatePublisherEvidence
enabled="false" /> </runtime> </configuration> Error: When
running a VSS backup on a Windows 2003 server with Exchange 2003 the
following error appeared.
Return
code 5853 unknown ANS0322E
(RC5853) no text available for this return code. ANS0322E
no text available for this return code. ACN5060E
A Tivoli Storage Manager API error has occurred. Solution: “Tivoli
Storage Manager backup-archive client Version 6.2.1 is required when running
in an Exchange Server 2010 environment” Upgrade
to Tivoli Storage Manager backup-archive client Version 6.2.2.x |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note: Southern-Minds and its
representatives are not responsible for any problems occurring from use of these
instructions. You are responsible to test in an appropriate environment to
verify these instructions works for you. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
