Ashish,
Changing the serialization parameter in your backup copygroup definition
from shrstatic or static to shrdynamic or dynamic will force TSM to
backup open files; HOWEVER, there is no guarantee that you will be able
to make use of the backed up open files in the case of restore.
You should NOT backup exchange with the regular Baclient. You could make
of use of Tivoli Data Protection for Exchange or FastBack to backup
Exchange. Both products require a license.
Look at the following site for TDP for Exchange
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp under
Storage Manager for Mail >> Data Protection for Microsoft Exchange
Server Installation
BERTAUT TCHUISE
TSM/NetApp Storage Administrator
Legg Mason Technology Services
*410-580-7032
BTchuise AT leggmason DOT com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
ashish sharma
Sent: Monday, October 12, 2009 9:25 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] How to backup open log files in exchange
Hello all,
I have to configure TSM backup for Microsoft exchange server.The problem
is that TSM BAC client is unable to backup open files and the mail admin
requires these files to be backed up anyway.According to him, all log
files , whcih are always open are needed for recovery.So , my question
is that , do we have anyway through which we can backup open files in
exchange?
Thanks in advance for your reply.
--
Best Regards
Ashish Sharma
ST Microelectronics Ltd.
919717003853
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
|