Thank you very much Del.
I know it is much better to use TSM Server 6.3.3, TSM Client 6.4 and TDPE
6.4......
But we have TSM Server 5.5.6 and were told by IBM support TDPE 6.4 is not
certified with TSM Server 5.5.6 and it cannot be used with TSM Client 6.2.4.
So we decided to wait a few weeks till TSM Server is upgraded to 6.3.3.
Grigori G. Solonovitch
Senior Technical 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
Del Hoobler
Sent: 28 02 2013 3:06 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Exchange 2010 backup configuration
Hello Grigori,
The first thing I notice is that you said:
"We also installed TDPE 6.1.3.3"
You should install Data Protection for Exchange 6.4.
This has full DAG support including configuration wizards that will handle all
of this for you
"backup_archive_client_node" is the NODENAME of the BA Client (DSMAGENT) on the
actual Exchange Server.
I am guessing these will be "MB1" and "MB2" in your case.
"data_protection_node" is the NODENAME of the DP/Exchange node. I am guessing
these will be something like "MB1_EXC" and "MB2_EXC" in your case.
You won't need one for the CAS server if you don't have any mailboxes on it.
Again, I really recommend that you install and use Data Protection for Exchange
6.4 since it has full Exchange Server DAG support including the ability to
manage all Exchange Server database backups under a common code (DAGNODE).
Thanks,
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 02/28/2013
12:07:34 AM:
> From: Grigori Solonovitch <Grigori.Solonovitch AT AHLIUNITED DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 02/28/2013 12:09 AM
> Subject: Exchange 2010 backup configuration Sent by: "ADSM: Dist Stor
> Manager" <ADSM-L AT vm.marist DOT edu>
>
> Hello Everybody,
> We are implementing Exchange 2010 and want to use TDPE and TSM Client
> to backup databases to TSM Server 5.5.6.
> I am not very cool in Exchange and our Exchange administrator is not
> very cool in TSM.
> Two servers MB1 and MB2 are configured to keep databases in active-
> active mode and server CAS1 is configured to keep DAG directory.
> I have installed TSM Client 6.2.4.7 on MB1, MB2 and CAS1 and defined
> TSM nodes for MB1, MB2, CAS1 and DAG (cluster node).
> We also installed TDPE 6.1.3.3 on the both MB1 and MB2.
> I am not sure it is possible to use this configuration at all (Server
> 5.5.6, Client 6.2.4.7, TDPE 6.1.3.3 and Exchange 2010), but our
> upgrade project to TSM 6.3.3 is just started now and it will take time
> definitely.
> According to TDPE 6.4 documentation we need to define proxy nodes to
> run database backups one time:
>
> register node backup_archive_client_node password register node
> data_protection_node password grant proxynode
> target=data_protection_node
agent=backup_archive_client_node
> register node DAG_node password
> grant proxynode target=DAG_node agent=backup_archive_client_node grant
> proxynode target=DAG_node agent=data_protection_node
>
> As far as I understand "DAG_node" is TSM node DAG in our case.
> Could somebody explain me what is " backup_archive_client_node" and
> "data_protection_node" in our case?
> Any links for documentation?
> Thank you very much in advance.
> Kindest regards,
>
> Grigori G. Solonovitch
> Senior Technical Architect Ahli United Bank Kuwait
www.ahliunited.com.kw
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.
|
