Re: [ADSM-L] tsm tdp vss issues exchange 2010
2013-04-17 07:16:54
Hello Steve,
If you mentioned client part we have done everything manually without scripts.
TSM server site scripts are:
register node KWTMB1 XXX passexp=0 userid=none type=client domain=NT
compression=yes archdelete=yes backdelete=yes
url=http://KWTMB1.kuwait.aub.net:1581
register node KWTMB1_EXC XXX passexp=0 userid=none type=client domain=MAIL
compression=yes archdelete=yes backdelete=yes
url=http://KWTMB1.kuwait.aub.net:1581
register node KWTMB2 XXX passexp=0 userid=none type=client domain=NT
compression=yes archdelete=yes backdelete=yes
url=http://KWTMB2.kuwait.aub.net:1581
register node KWTMB2_EXC XXX passexp=0 userid=none type=client domain=MAIL
compression=yes archdelete=yes backdelete=yes
url=http://KWTMB2.kuwait.aub.net:1581
register node KWDAG XXX passexp=0 userid=none type=client domain=MAIL
compression=yes archdelete=yes backdelete=yes
url=http://KWDAG.kuwait.aub.net:1581
grant proxynode target=KWTMB1_EXC agent=KWTMB1
grant proxynode target=KWTMB2_EXC agent=KWTMB2
grant proxynode target=KWDAG agent=KWTMB1
grant proxynode target=KWDAG agent=KWTMB1_EXC
grant proxynode target=KWDAG agent=KWTMB2
grant proxynode target=KWDAG agent=KWTMB2_EXC
register admin KWTMB1 XXX
grant authority KWTMB1 class=node authority=owner node=KWTMB1
register admin KWTMB2 XXX
grant authority KWTMB2 class=node authority=owner node=KWTMB2
register admin KWTMB1_EXC XXX
grant authority KWTMB1_EXC class=node authority=owner node=KWTMB1_EXC
register admin KWTMB2_EXC XXX
grant authority KWTMB2_EXC class=node authority=owner node=KWTMB2_EXC
I hope it will help you. I can provide *.OPT files from clients as well if
required.
Grigori G. Solonovitch
Senior Systems Architect Ahli United Bank Kuwait www.ahliunited.com.kw
Please consider the environment before printing this E-mail
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Schaub, Steve
Sent: 17 04 2013 2:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] tsm tdp vss issues exchange 2010
Grigori,
Did you happen to use a scripted install for the TDP?
If so, would you be willing to share?
Thanks,
Steve Schaub
Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Grigori Solonovitch
Sent: Wednesday, April 17, 2013 1:23 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] tsm tdp vss issues exchange 2010
We have implemented TSM Client 6.4.0/TDP for Exchange 6.4.0 for Exchange 2010
(DAG configuration ) recently.
It was not easy - a few SRs to IBM and Microsoft have been raised.
Implementation was quite painful, but final result is good.
Grigori G. Solonovitch
Senior Systems Architect Ahli United Bank Kuwait www.ahliunited.com.kw
Please consider the environment before printing this E-mail
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: 16 04 2013 5:52 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] tsm tdp vss issues exchange 2010
Has anyone had numerous issues with TSM TDP for Exchange 2010. We continue to
struggle with VSS issues and Microsoft claims its not their issue. We initially
had Exchange circular logging enabled and have since turned that off as
recommended. I see that TSM TDP for Exchange 6.4 is available.
Configuration
TSM 6.3.1.15 server on Windows 2008 R2 Enterprise TSM 6.3.1 BA client on
Exchange servers TSM TDP Exchange 6.3.1 Exchange 2010 Version 14.02.0247.005
Exchange Windows servers 2008 R2 Enterprise SP1
Recent dsmerror.log during tdpexcc full backup
04/16/2013 07:42:04 ANS5252E TSM attempted to execute a system command which
failed.
command : "C:\Program Files\Tivoli\TSM\baclient\excvssic.exe"
C:\adsm.sys\vss_staging\TDP_EXCH2\TSMPOK\20130416071952\b6d6da44-9ba6-4426-9503-1e2183bab0d3_Audit.txt
rc : -1032
04/16/2013 07:42:05 ANS5250E An unexpected error was encountered.
TSM function name : baHandleSnapshot
TSM function : BaHandleSystemPostSnapshotCmd() failed.
TSM return code : -1032
TSM file : backsnap.cpp (4300)
04/16/2013 07:42:05 ANS1327W The snapshot operation for
'\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20\' failed with error code:
-1032.
04/16/2013 07:42:05 Return code -1032 unknown
04/16/2013 07:42:05 Unknown system error Please check the TSM Error Log for any
additional information
04/16/2013 08:02:12 ANS1577I The Windows console event handler received a
'Ctrl-C' console event.
Thanks,
Tim Brown
Please consider the environment before printing this Email.
________________________________
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail
message and any attachments hereto may be legally privileged and confidential.
The information is intended only for the recipient(s) named in this message. If
you are not the intended recipient you are notified that any use, disclosure,
copying or distribution is prohibited. If you have received this in error
please contact the sender and delete this message and any attachments from your
computer system. We do not guarantee that this message or any attachment to it
is secure or free from errors, computer viruses or other conditions that may
damage or interfere with data, hardware or software.
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm
________________________________
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail
message and any attachments hereto may be legally privileged and confidential.
The information is intended only for the recipient(s) named in this message. If
you are not the intended recipient you are notified that any use, disclosure,
copying or distribution is prohibited. If you have received this in error
please contact the sender and delete this message and any attachments from your
computer system. We do not guarantee that this message or any attachment to it
is secure or free from errors, computer viruses or other conditions that may
damage or interfere with data, hardware or software.
|
|
|