Re: Newbie Question cluster backups

[Robben Leaf]

The Windows B/A Client manual has a good description on how to do this in
one of its appendices.

In general terms, you need to define a separate node name for the data to
be backed up from the new drive; get an option file on the new drive; set
up services (TSM Schedules, Client Acceptor, and Remote Agent) on EACH of
the physical hosts that the vnode can fail over to, and set up cluster
services in Windows' Cluster Administrator to control those services.

Some gotchas: For clustered services, make sure you choose an HTTP port and
TCP client port that are different from those used by all other nodes
within the cluster. Make sure the option file has only the drives for that
vnode in its Domain statement. The set of services on the different
physical hosts for that vnode must have IDENTICAL names (i.e. the service
called "TSM Scheduler: VNODENAME" must be named exactly the same way on
every host that that vnode can fail over to). The local services on each
physical host for the vnode must be set to Manual, not Automatic - they
will be controlled by the cluster services. The most straightforward way to
get the password validated for the services on each physical host is to
fail the vnode over to that physical host before you create the services.

Hope this helps - good luck!

Robben



 "Matthews, Gary"
 <[EMAIL PROTECTED]
 GICACMG.COM>   To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
 .EDU>     [ADSM-L] Newbie Question cluster
   backups

 09/25/2006 07:50
 AM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Hi,

Have a question about setting a backup. I've inherited a Tivoli backup
solution and am very slowly getting to grips with it ( have a NetBackup
background) and now need help in setting up a new backup. We've a sql
cluster wdccdb01 which has been set up backup the local drives via each
side of the cluster separately (wdccsq01/02) - The clustered disk
resource hold the SQL database and that backs up the SQL agent, so
there's a dsm.opt file  in TSM/baclient locally  for each node  and a
dsm.opt file in TSM/TDPsql locally on each client. Now we've just put on
another drive to the cluster( non SQL) - First time for me to set up a
new backup -  What's the best way to set this backup up

Cheers

Gary


This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.




--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==

Newbie Question cluster backups

[Matthews, Gary]

Hi,

Have a question about setting a backup. I've inherited a Tivoli backup
solution and am very slowly getting to grips with it ( have a NetBackup
background) and now need help in setting up a new backup. We've a sql
cluster wdccdb01 which has been set up backup the local drives via each
side of the cluster separately (wdccsq01/02) - The clustered disk
resource hold the SQL database and that backs up the SQL agent, so
there's a dsm.opt file  in TSM/baclient locally  for each node  and a
dsm.opt file in TSM/TDPsql locally on each client. Now we've just put on
another drive to the cluster( non SQL) - First time for me to set up a
new backup -  What's the best way to set this backup up

Cheers

Gary 


This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

cluster backups

[Gill, Geoffrey L.]

Would there be any reason that this message would show up in the log of one
of the nodes, not the clusternode, when the domain statement says C: D: on
node2? Node 1 is not reporting this error. The backup is reporting as failed
because of it. I've looked at the dsm.opt files and they are identical on
node 1 and 2 except for the nodename. The only thing I can think of is the
dsm.opt file maybe have had DOMAIN ALL-LOCAL and after it was changed to C:
D: the service was not restarted.



Client Windows 2003 Client version is 5.2.2.10

TSM server AIX 5.2 TSM 5.2.6.1



08/15/2006 21:57:27 ANS1228E Sending of object '\\clusternode\e$' failed

08/15/2006 21:57:27 ANS1154E Drive \\clusternode\e$ is a cluster disk.

Not valid for backup/archive when CLUSTERNODE option is NO.



08/15/2006 21:57:27 --- SCHEDULEREC STATUS BEGIN

08/15/2006 21:57:27 Total number of objects inspected:   34,793

08/15/2006 21:57:27 Total number of objects backed up:  133

08/15/2006 21:57:27 Total number of objects updated:  0

08/15/2006 21:57:27 Total number of objects rebound:  0

08/15/2006 21:57:27 Total number of objects deleted:  0

08/15/2006 21:57:27 Total number of objects expired: 85

08/15/2006 21:57:27 Total number of objects failed:   1

08/15/2006 21:57:27 Total number of bytes transferred:47.20 MB

08/15/2006 21:57:27 Data transfer time:   47.92 sec

08/15/2006 21:57:27 Network data transfer rate:1,008.64 KB/sec

08/15/2006 21:57:27 Aggregate data transfer rate:174.19 KB/sec

08/15/2006 21:57:27 Objects compressed by:   53%

08/15/2006 21:57:27 Elapsed processing time:   00:04:37

08/15/2006 21:57:27 --- SCHEDULEREC STATUS END

08/15/2006 21:57:27 --- SCHEDULEREC OBJECT END CLIENT-M-F 08/15/2006
21:30:00

08/15/2006 21:57:27 ANS1512E Scheduled event 'CLIENT-M-F'.





Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:   [EMAIL PROTECTED]

Cluster backups

[Barnes, Kenny]

I would like to pick the brains of anyone backing up Windows clusters
and/or Veritas clusters running on Solaris.  This is something I have
struggled with and cannot get any TSM method to word reliable.  We were
somewhat stable while running on 5.2 server and clients at 5.2.  
 
We are running 5.3.2.3 server on Solaris 9.
Host are at 5.3.2 
 
 
Kenny Barnes
Enterprise Storage Team
GMAC Insurance
336-770-8280
[EMAIL PROTECTED]
 

--
Note:  The information contained in this message may be privileged and 
confidential
and protected from disclosure.  If the reader of this message is not the 
intended recipient,
or an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution or copying of this 
communication
is strictly prohibited.  If you have received this communication in error, 
please notify us 
immediately by replying to the message and deleting it from your computer.  
Thank you.
--

Re: Linux Cluster Backups

[Bos, Karel]

Hi,

Same here. Just finishing configuring the back-up of the shared storage
and looking at the filespace info on the ITSM server, I start to wonder:

  Node Name: NULBEAWEBCLUSTER
 Filespace Name: /data-ext
 Hexadecimal Filespace Name: 
   FSID: 1
   Platform: Linux86
 Filespace Type: UNKNOWN
  Is Filespace Unicode?: No

The part "UNKNOWN", I do not like. Back-up runs, restore works but
still

Anyone?

FYI, because the cluster software isn't configured to contain any
resources (I would say, not used) and the GFS software is a bit to much
to handle for the Linux Administrator, I did:
-create a folder on the shared storage containing the dsm.opt and log
files;
-on all cluster nodes a put a stanze in de dsm.sys for the cluster
resource;
-start the tsm service/gui etc with -optfile=/share_stg/folder/dsm.opt. 
Options as "clusternode yes" gave errors like "no cluster resource"
:-(

Its time for a google search.  

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David Longo
Sent: dinsdag 25 juli 2006 23:39
To: ADSM-L@VM.MARIST.EDU
Subject: Linux Cluster Backups

I haven't found any docs on backing up Linux Clusters.  I've done W2K
and Netware Clusters with no problem per docs.

New system we have is: RHEL 4 AS u3;  Red Hat Cluster Suite 4; GFS 6.1.
Cluster disks are Fibre connected to IBM DS8100 and DS4800.
Using TSM client 5.3.2.

Do I simply follow the methods of setting up Cluster Services that are
used on this system and sort of "translate" how TSM is done, say like on
W2K Cluster?

Anybody done this yet?  Any gotchas? 

Thanks,


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


##
This message is for the named person's use only.  It may contain
confidential, proprietary, or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it, and
notify the sender.  You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.  Health First reserves the right to monitor all
e-mail communications through its networks.  Any views or opinions
expressed in this message are solely those of the individual sender,
except (1) where the message states such views or opinions are on behalf
of a particular entity;  and (2) the sender is authorized by the entity
to give such views or opinions.
##

Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel
bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd,
verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te
vernietigen.
Aangezien de integriteit van het bericht niet veilig gesteld is middels
verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden
voor de inhoud daarvan.
Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven
wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij
enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit
bericht.
 
Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder
Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle
andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing.
Deze worden u op aanvraag direct kosteloos toegezonden.
 
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender
does not warrant that this transmission is virus-free and will not be
liable for any damages resulting from any virus transmitted.
 
On all offers and agreements under which Atos Origin supplies goods and/or
services of whatever nature, the Terms of Delivery from Atos Origin
exclusively apply. 
The Terms of Delivery shall be promptly submitted to you on your request.

Linux Cluster Backups

[David Longo]

I haven't found any docs on backing up Linux Clusters.  I've done W2K and 
Netware
Clusters with no problem per docs.

New system we have is: RHEL 4 AS u3;  Red Hat Cluster Suite 4; GFS 6.1.
Cluster disks are Fibre connected to IBM DS8100 and DS4800.
Using TSM client 5.3.2.

Do I simply follow the methods of setting up Cluster Services that are used on 
this
system and sort of "translate" how TSM is done, say like on W2K Cluster?

Anybody done this yet?  Any gotchas? 

Thanks,


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


##
This message is for the named person's use only.  It may 
contain confidential, proprietary, or legally privileged 
information.  No confidentiality or privilege is waived or 
lost by any mistransmission.  If you receive this message 
in error, please immediately delete it and all copies of it 
from your system, destroy any hard copies of it, and notify 
the sender.  You must not, directly or indirectly, use, 
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient.  Health First reserves
the right to monitor all e-mail communications through its
networks.  Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of 
a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.
##

Re: need help with ms-exchange 2003 cluster backups

[Kauffman, Tom]

Thanks to all for the pointers --

Del, the magic was your note about /EXCSERVER (along with getting the
resources for server one back on server one -- sigh).

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 11:34 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

Can you please get the answers to these questions
from your people?

1. What do you see in the TDPEXC.LOG file?

2. What errors messages are you getting?
   Check the output the TDPEXC.LOG file and the
   output of the TDPEXCC command?

3. Does the userid that owns the Windows Scheduler
   Service have enough authority to back up
   the Exchange server and access the Windows registry?

One thing to keep in mind for a cluster setup is that
you should only be running the scheduled backup on the
machine that currently has the running instance of the
Exchange virtual server. When running with the TSM BA
client scheduler this is accomplished by creating
a cluster resource for the TSM BA scheduler that
is dependant on the Exchange virtual server cluster resource.

Also, when running in a cluster, you need to run
specify the "/EXCSERVER=virt-exch-server-name" option,
where "virt-exch-server-name" is the name of your
Exchange virtual server.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
11:15:17 AM:

> I know it's not much to go on -- that's what I'm getting from MY
people
> :-(
>
> At the server side, I see no connect from the cluster, so I'm making
the
> assumption that the Windows 2003 scheduling process (whatever it is)
> isn't actually working (Is there anything besides the 'at' command? I
> haven't looked at this aspect of Windows since NT 3.51 . . .)
>
> Tom Kauffman
> NIBCO, Inc

Re: need help with ms-exchange 2003 cluster backups

[Kauffman, Tom]

Thanks, Del -- I feel a bit better now.

I'll have the guys look at the tdpexch.log and see if there's any
indication of the process trying to start and then quitting without
attempting to contact the tsm server (or reporting it can't FIND the tsm
server).

One note, which I think I mentioned up front -- this is an active/active
cluster, with both sides running at all times with half the workload
each. In the event of a failure, either side will fail over to the other
which will run both info-stores.

All set up by a pair of Dell consultants with a fair bit of experience
under their belts. Now they're off to the next project and our people
are trying to remember what they were told and figure out what the
forgot to ask about (there are other alligators in this swamp they're
working with). And, in all fairness, I've had the same results with AIX
consultants and my memory.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 12:27 PM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

This isn't the problem. Data Protection for Exchange
automatically ships and installs the TSM API.
You do not need to install the TSM BA client
unless you decide to the use the TSM BA client scheduler.

Please refer to my previous append to get more
details about the problem.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
01:17:51 PM:

> Drat! I missed that! . . . What is fascinating is that the backups can
> be run by hand and look like they're working correctly . . .
>
> We'll drop the API on and see if anything changes.
>
> Thanks.
>
> Tom Kauffman
> NIBCO, Inc
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
> Bos, Karel
> Sent: Monday, June 14, 2004 10:42 AM
> To: [EMAIL PROTECTED]
> Subject: Re: need help with ms-exchange 2003 cluster backups
>
> Tom,
>
> From the looks of it, only the TDP is installed. In the readme it is
> stated that:
>
> Software Requirements
> -
>
> Data Protection for Microsoft Exchange version 5.2.1
> requires the following MINIMUM software levels:
>
>  -  IBM Tivoli Storage Manager API 5.1.5
>
> The API is deliverd in the BA client package. Before scheduling the
> back-ups, I would recommend making one session from the GUI, to see if
> the communication between the TDP is working.
>
> Regards,
>
> Karel Bos
> Customer Unit Nuon

Re: need help with ms-exchange 2003 cluster backups

[Del Hoobler]

Tom,

This isn't the problem. Data Protection for Exchange
automatically ships and installs the TSM API.
You do not need to install the TSM BA client
unless you decide to the use the TSM BA client scheduler.

Please refer to my previous append to get more
details about the problem.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
01:17:51 PM:

> Drat! I missed that! . . . What is fascinating is that the backups can
> be run by hand and look like they're working correctly . . .
>
> We'll drop the API on and see if anything changes.
>
> Thanks.
>
> Tom Kauffman
> NIBCO, Inc
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Bos, Karel
> Sent: Monday, June 14, 2004 10:42 AM
> To: [EMAIL PROTECTED]
> Subject: Re: need help with ms-exchange 2003 cluster backups
>
> Tom,
>
> From the looks of it, only the TDP is installed. In the readme it is
> stated that:
>
> Software Requirements
> -
>
> Data Protection for Microsoft Exchange version 5.2.1
> requires the following MINIMUM software levels:
>
>  -  IBM Tivoli Storage Manager API 5.1.5
>
> The API is deliverd in the BA client package. Before scheduling the
> back-ups, I would recommend making one session from the GUI, to see if
> the communication between the TDP is working.
>
> Regards,
>
> Karel Bos
> Customer Unit Nuon

Re: need help with ms-exchange 2003 cluster backups

[Kauffman, Tom]

Drat! I missed that! . . . What is fascinating is that the backups can
be run by hand and look like they're working correctly . . .

We'll drop the API on and see if anything changes.

Thanks.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bos, Karel
Sent: Monday, June 14, 2004 10:42 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

>From the looks of it, only the TDP is installed. In the readme it is
stated that:

Software Requirements
-

Data Protection for Microsoft Exchange version 5.2.1 
requires the following MINIMUM software levels:

 -  IBM Tivoli Storage Manager API 5.1.5

The API is deliverd in the BA client package. Before scheduling the
back-ups, I would recommend making one session from the GUI, to see if
the communication between the TDP is working. 

Regards,

Karel Bos
Customer Unit Nuon

Atos Origin 
Naritaweg 50-52
1043 BZ Amsterdam

Office: +31 (0)20 4841132
Fax:+31 (0)20
Mobile: +31 (0)6 51 29 88 01 
[EMAIL PROTECTED]
www.atosorigin.com

This e-mail and the documents attached are confidential and intended
solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin
group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender
does
not warrant that this transmission is virus-free and will not be liable
for
any damages resulting from any virus transmitted.






-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kauffman, Tom
Sent: maandag 14 juni 2004 17:15
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups


I know it's not much to go on -- that's what I'm getting from MY people
:-(

At the server side, I see no connect from the cluster, so I'm making the
assumption that the Windows 2003 scheduling process (whatever it is)
isn't actually working (Is there anything besides the 'at' command? I
haven't looked at this aspect of Windows since NT 3.51 . . .)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

"it's not happening" is not much to go on.  :-)
Can you get more details on what is not working?
What do you see in the TDPEXC.LOG file?
What errors are you getting?
Does the user-id that owns the Windows Scheduler
Service have enough authority to back up
the Exchange server and access the Windows registry?

Data Protection for Exchange 5.2.1 has been tested
in an Exchange 2003 Active/Active Cluster environment.
All "scheduler" testing was done using the
TSM backup/archive client scheduler.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
09:37:24 AM:

> I don't do windows and my windows support people have hit a blank
wall.
> We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is)
> and went to a clustered environment - two nodes in active/active mode,
> with the userbase and info-store split between them. And, of course,
> went to the current TDP Exchange client that claims to know both
> Exchange 2003 and clustering.
>
> We're using the Windows scheduling process to kick off the backups -
and
> it's not happening. I don't have the regular TSM client on these two
> systems, as our 'bare metal restore' concept is rebuild/relaod from CD
> and then restore the info-store.
>
> I'm looking for suggestions on what to tell the guys to look for, and
> where to look. Any help would be appreciated!
>
> Tom Kauffman
> NIBCO, Inc

Re: need help with ms-exchange 2003 cluster backups

[Kauffman, Tom]

1) Yes
2) Yes

And this is why I'm thinking it's actually a scheduling issue.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Ochs, Duane
Sent: Monday, June 14, 2004 11:30 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

1) Can they connect from the TDP gui and/or command line ?
2) If so, can they backup the Exchange server ?
3) If not, what are the errors they are receiving ?

Check the tsm\tdpexc\dsierror.log and dsmerror.log, also, check the
event viewer for this system and see if any additional errors are
logged. 

You do not need the BA client software to use the TDP client.

> Duane Ochs
> Enterprise Computing
> 
> Quad/Graphics
> 
> Sussex, Wisconsin
> 414-566-2375 phone
> 414-917-0736 beeper 
> [EMAIL PROTECTED]
> www.QG.com
> 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 14, 2004 10:15 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups


I know it's not much to go on -- that's what I'm getting from MY people
:-(

At the server side, I see no connect from the cluster, so I'm making the
assumption that the Windows 2003 scheduling process (whatever it is)
isn't actually working (Is there anything besides the 'at' command? I
haven't looked at this aspect of Windows since NT 3.51 . . .)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

"it's not happening" is not much to go on.  :-)
Can you get more details on what is not working?
What do you see in the TDPEXC.LOG file?
What errors are you getting?
Does the user-id that owns the Windows Scheduler
Service have enough authority to back up
the Exchange server and access the Windows registry?

Data Protection for Exchange 5.2.1 has been tested
in an Exchange 2003 Active/Active Cluster environment.
All "scheduler" testing was done using the
TSM backup/archive client scheduler.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
09:37:24 AM:

> I don't do windows and my windows support people have hit a blank
wall.
> We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is)

> and went to a clustered environment - two nodes in active/active mode,

> with the userbase and info-store split between them. And, of course, 
> went to the current TDP Exchange client that claims to know both 
> Exchange 2003 and clustering.
>
> We're using the Windows scheduling process to kick off the backups -
and
> it's not happening. I don't have the regular TSM client on these two 
> systems, as our 'bare metal restore' concept is rebuild/relaod from CD

> and then restore the info-store.
>
> I'm looking for suggestions on what to tell the guys to look for, and 
> where to look. Any help would be appreciated!
>
> Tom Kauffman
> NIBCO, Inc

Re: need help with ms-exchange 2003 cluster backups

[Del Hoobler]

Tom,

Can you please get the answers to these questions
from your people?

1. What do you see in the TDPEXC.LOG file?

2. What errors messages are you getting?
   Check the output the TDPEXC.LOG file and the
   output of the TDPEXCC command?

3. Does the userid that owns the Windows Scheduler
   Service have enough authority to back up
   the Exchange server and access the Windows registry?

One thing to keep in mind for a cluster setup is that
you should only be running the scheduled backup on the
machine that currently has the running instance of the
Exchange virtual server. When running with the TSM BA
client scheduler this is accomplished by creating
a cluster resource for the TSM BA scheduler that
is dependant on the Exchange virtual server cluster resource.

Also, when running in a cluster, you need to run
specify the "/EXCSERVER=virt-exch-server-name" option,
where "virt-exch-server-name" is the name of your
Exchange virtual server.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
11:15:17 AM:

> I know it's not much to go on -- that's what I'm getting from MY people
> :-(
>
> At the server side, I see no connect from the cluster, so I'm making the
> assumption that the Windows 2003 scheduling process (whatever it is)
> isn't actually working (Is there anything besides the 'at' command? I
> haven't looked at this aspect of Windows since NT 3.51 . . .)
>
> Tom Kauffman
> NIBCO, Inc

Re: need help with ms-exchange 2003 cluster backups

[Ochs, Duane]

1) Can they connect from the TDP gui and/or command line ?
2) If so, can they backup the Exchange server ?
3) If not, what are the errors they are receiving ?

Check the tsm\tdpexc\dsierror.log and dsmerror.log, also, check the
event viewer for this system and see if any additional errors are
logged. 

You do not need the BA client software to use the TDP client.

> Duane Ochs
> Enterprise Computing
> 
> Quad/Graphics
> 
> Sussex, Wisconsin
> 414-566-2375 phone
> 414-917-0736 beeper 
> [EMAIL PROTECTED]
> www.QG.com
> 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 14, 2004 10:15 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups


I know it's not much to go on -- that's what I'm getting from MY people
:-(

At the server side, I see no connect from the cluster, so I'm making the
assumption that the Windows 2003 scheduling process (whatever it is)
isn't actually working (Is there anything besides the 'at' command? I
haven't looked at this aspect of Windows since NT 3.51 . . .)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

"it's not happening" is not much to go on.  :-)
Can you get more details on what is not working?
What do you see in the TDPEXC.LOG file?
What errors are you getting?
Does the user-id that owns the Windows Scheduler
Service have enough authority to back up
the Exchange server and access the Windows registry?

Data Protection for Exchange 5.2.1 has been tested
in an Exchange 2003 Active/Active Cluster environment.
All "scheduler" testing was done using the
TSM backup/archive client scheduler.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
09:37:24 AM:

> I don't do windows and my windows support people have hit a blank
wall.
> We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is)

> and went to a clustered environment - two nodes in active/active mode,

> with the userbase and info-store split between them. And, of course, 
> went to the current TDP Exchange client that claims to know both 
> Exchange 2003 and clustering.
>
> We're using the Windows scheduling process to kick off the backups -
and
> it's not happening. I don't have the regular TSM client on these two 
> systems, as our 'bare metal restore' concept is rebuild/relaod from CD

> and then restore the info-store.
>
> I'm looking for suggestions on what to tell the guys to look for, and 
> where to look. Any help would be appreciated!
>
> Tom Kauffman
> NIBCO, Inc

Re: need help with ms-exchange 2003 cluster backups

[Bos, Karel]

Tom,

>From the looks of it, only the TDP is installed. In the readme it is stated that:

Software Requirements
-

Data Protection for Microsoft Exchange version 5.2.1 
requires the following MINIMUM software levels:

 -  IBM Tivoli Storage Manager API 5.1.5

The API is deliverd in the BA client package. Before scheduling the back-ups, I would 
recommend making one session from the GUI, to see if the communication between the TDP 
is working. 

Regards,

Karel Bos
Customer Unit Nuon

Atos Origin 
Naritaweg 50-52
1043 BZ Amsterdam

Office: +31 (0)20 4841132
Fax:+31 (0)20
Mobile: +31 (0)6 51 29 88 01 
[EMAIL PROTECTED]
www.atosorigin.com

This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender does
not warrant that this transmission is virus-free and will not be liable for
any damages resulting from any virus transmitted.






-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Kauffman, Tom
Sent: maandag 14 juni 2004 17:15
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups


I know it's not much to go on -- that's what I'm getting from MY people
:-(

At the server side, I see no connect from the cluster, so I'm making the
assumption that the Windows 2003 scheduling process (whatever it is)
isn't actually working (Is there anything besides the 'at' command? I
haven't looked at this aspect of Windows since NT 3.51 . . .)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

"it's not happening" is not much to go on.  :-)
Can you get more details on what is not working?
What do you see in the TDPEXC.LOG file?
What errors are you getting?
Does the user-id that owns the Windows Scheduler
Service have enough authority to back up
the Exchange server and access the Windows registry?

Data Protection for Exchange 5.2.1 has been tested
in an Exchange 2003 Active/Active Cluster environment.
All "scheduler" testing was done using the
TSM backup/archive client scheduler.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
09:37:24 AM:

> I don't do windows and my windows support people have hit a blank
wall.
> We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is)
> and went to a clustered environment - two nodes in active/active mode,
> with the userbase and info-store split between them. And, of course,
> went to the current TDP Exchange client that claims to know both
> Exchange 2003 and clustering.
>
> We're using the Windows scheduling process to kick off the backups -
and
> it's not happening. I don't have the regular TSM client on these two
> systems, as our 'bare metal restore' concept is rebuild/relaod from CD
> and then restore the info-store.
>
> I'm looking for suggestions on what to tell the guys to look for, and
> where to look. Any help would be appreciated!
>
> Tom Kauffman
> NIBCO, Inc

Re: need help with ms-exchange 2003 cluster backups

[Kauffman, Tom]

I know it's not much to go on -- that's what I'm getting from MY people
:-(

At the server side, I see no connect from the cluster, so I'm making the
assumption that the Windows 2003 scheduling process (whatever it is)
isn't actually working (Is there anything besides the 'at' command? I
haven't looked at this aspect of Windows since NT 3.51 . . .)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 9:12 AM
To: [EMAIL PROTECTED]
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

"it's not happening" is not much to go on.  :-)
Can you get more details on what is not working?
What do you see in the TDPEXC.LOG file?
What errors are you getting?
Does the user-id that owns the Windows Scheduler
Service have enough authority to back up
the Exchange server and access the Windows registry?

Data Protection for Exchange 5.2.1 has been tested
in an Exchange 2003 Active/Active Cluster environment.
All "scheduler" testing was done using the
TSM backup/archive client scheduler.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
09:37:24 AM:

> I don't do windows and my windows support people have hit a blank
wall.
> We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is)
> and went to a clustered environment - two nodes in active/active mode,
> with the userbase and info-store split between them. And, of course,
> went to the current TDP Exchange client that claims to know both
> Exchange 2003 and clustering.
>
> We're using the Windows scheduling process to kick off the backups -
and
> it's not happening. I don't have the regular TSM client on these two
> systems, as our 'bare metal restore' concept is rebuild/relaod from CD
> and then restore the info-store.
>
> I'm looking for suggestions on what to tell the guys to look for, and
> where to look. Any help would be appreciated!
>
> Tom Kauffman
> NIBCO, Inc

Re: need help with ms-exchange 2003 cluster backups

[Del Hoobler]

Tom,

"it's not happening" is not much to go on.  :-)
Can you get more details on what is not working?
What do you see in the TDPEXC.LOG file?
What errors are you getting?
Does the user-id that owns the Windows Scheduler
Service have enough authority to back up
the Exchange server and access the Windows registry?

Data Protection for Exchange 5.2.1 has been tested
in an Exchange 2003 Active/Active Cluster environment.
All "scheduler" testing was done using the
TSM backup/archive client scheduler.

Thanks,

Del



"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/14/2004
09:37:24 AM:

> I don't do windows and my windows support people have hit a blank wall.
> We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is)
> and went to a clustered environment - two nodes in active/active mode,
> with the userbase and info-store split between them. And, of course,
> went to the current TDP Exchange client that claims to know both
> Exchange 2003 and clustering.
>
> We're using the Windows scheduling process to kick off the backups - and
> it's not happening. I don't have the regular TSM client on these two
> systems, as our 'bare metal restore' concept is rebuild/relaod from CD
> and then restore the info-store.
>
> I'm looking for suggestions on what to tell the guys to look for, and
> where to look. Any help would be appreciated!
>
> Tom Kauffman
> NIBCO, Inc

need help with ms-exchange 2003 cluster backups

[Kauffman, Tom]

I don't do windows and my windows support people have hit a blank wall.
We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is)
and went to a clustered environment - two nodes in active/active mode,
with the userbase and info-store split between them. And, of course,
went to the current TDP Exchange client that claims to know both
Exchange 2003 and clustering.

We're using the Windows scheduling process to kick off the backups - and
it's not happening. I don't have the regular TSM client on these two
systems, as our 'bare metal restore' concept is rebuild/relaod from CD
and then restore the info-store.

I'm looking for suggestions on what to tell the guys to look for, and
where to look. Any help would be appreciated!

Tom Kauffman
NIBCO, Inc

Re: Need Help Getting MS-EXCHANGE Cluster backups to work

[MC Matt Cooper (2838)]

Thanks
Matt

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del
Hoobler
Sent: Wednesday, February 04, 2004 11:45 AM
To: [EMAIL PROTECTED]
Subject: Re: Need Help Getting MS-EXCHANGE Cluster backups to work

Matt,

Data Protection for Exchange was run and tested in an Exchange 2003/Windows
2003 MSCS environment.
When setting up the failover for the scheduler service, you also need to set
up registry replication so that upon a failover, the password stored in the
registry is copied to the failover node registry.
You need to make sure that you are using CLUSTERNODE YES in the DSM.OPT file
so that the encryption/decryption of the TSM password is the same on both
nodes. Take a look at the Data Protection for Exchange User's Guide in the
section that discusses running it in an MSCS environment.
Also, take a look at the Appendix that discusses setting up automated
scheduling. It also talks about what you need to do when setting this up for
an MSCS cluster environment.

If you are still running into problems, please call IBM support and they can
get your through the issues.

Thanks,

Del



> Hello all,
> Our MS people are having a terrible time getting the new MS2003
exchange
> cluster to work.  They have experience on the regular servers but this
> cluster backup seems to have a continues steam of problems.
> The OS on the client is MS 2003, the Exchange is 2003,  the TSM
client
> is 5.1.5.0, the TDP is 5.2.   The TSM server is 5.1.8.1 on z/os 1.4.
>
> It appears that the installation losses the password.  The indivual
servers
> SERVER-A and SERVER-B backup O.K. but the MS-EXchange backup initially
lost
> the License.  So we reloaded that from one of the NEW (same software
levels,
> but not a cluster) MS-Exchanges stand alone servers. I guess they are
tired
> of reinstalling the product.  Anyway, now that it has the License it
looses
> the password.  I, the TSM server admin, am truely confused as to how
this is
> supposed to work.  Were is the MS server supposed to keep a TDP
> Exchange password if the service can fail over to a different server ( A
or B).
> When it would fail over there is no password.  Are all of the TSM
> installation softweare supposed to be in some shared disk directory.
Right
> now I see standard TSM client code on SERVER-A and SERVER-B on there own
> respective C: drives?   Is there a good place to get a good working
diagram
> for this? Maybe a REDBOOK?

Re: Need Help Getting MS-EXCHANGE Cluster backups to work

[Del Hoobler]

Matt,

Data Protection for Exchange was run and tested in an
Exchange 2003/Windows 2003 MSCS environment.
When setting up the failover for the scheduler service, you also need to
set up registry replication so that upon a failover, the password stored
in
the registry is copied to the failover node registry.
You need to make sure that you are using CLUSTERNODE YES in the DSM.OPT
file so that the encryption/decryption of the TSM password is the same
on both nodes. Take a look at the Data Protection for Exchange User's
Guide
in the section that discusses running it in an MSCS environment.
Also, take a look at the Appendix that discusses setting up
automated scheduling. It also talks about what you need to do
when setting this up for an MSCS cluster environment.

If you are still running into problems, please call IBM support
and they can get your through the issues.

Thanks,

Del



> Hello all,
> Our MS people are having a terrible time getting the new MS2003
exchange
> cluster to work.  They have experience on the regular servers but this
> cluster backup seems to have a continues steam of problems.
> The OS on the client is MS 2003, the Exchange is 2003,  the TSM
client
> is 5.1.5.0, the TDP is 5.2.   The TSM server is 5.1.8.1 on z/os 1.4.
>
> It appears that the installation losses the password.  The indivual
servers
> SERVER-A and SERVER-B backup O.K. but the MS-EXchange backup initially
lost
> the License.  So we reloaded that from one of the NEW (same software
levels,
> but not a cluster) MS-Exchanges stand alone servers. I guess they are
tired
> of reinstalling the product.  Anyway, now that it has the License it
looses
> the password.  I, the TSM server admin, am truely confused as to how
this is
> supposed to work.  Were is the MS server supposed to keep a TDP Exchange
> password if the service can fail over to a different server ( A or B).
> When it would fail over there is no password.  Are all of the TSM
> installation softweare supposed to be in some shared disk directory.
Right
> now I see standard TSM client code on SERVER-A and SERVER-B on there own
> respective C: drives?   Is there a good place to get a good working
diagram
> for this? Maybe a REDBOOK?

Need Help Getting MS-EXCHANGE Cluster backups to work

[MC Matt Cooper (2838)]

Hello all,
Our MS people are having a terrible time getting the new MS2003 exchange
cluster to work.  They have experience on the regular servers but this
cluster backup seems to have a continues steam of problems.
The OS on the client is MS 2003, the Exchange is 2003,  the TSM client
is 5.1.5.0, the TDP is 5.2.   The TSM server is 5.1.8.1 on z/os 1.4.

It appears that the installation losses the password.  The indivual servers
SERVER-A and SERVER-B backup O.K. but the MS-EXchange backup initially lost
the License.  So we reloaded that from one of the NEW (same software levels,
but not a cluster) MS-Exchanges stand alone servers. I guess they are tired
of reinstalling the product.  Anyway, now that it has the License it looses
the password.  I, the TSM server admin, am truely confused as to how this is
supposed to work.  Were is the MS server supposed to keep a TDP Exchange
password if the service can fail over to a different server ( A or B).
When it would fail over there is no password.  Are all of the TSM
installation softweare supposed to be in some shared disk directory.  Right
now I see standard TSM client code on SERVER-A and SERVER-B on there own
respective C: drives?   Is there a good place to get a good working diagram
for this? Maybe a REDBOOK?
Matt

Cluster backups

[Gill, Geoffrey L.]

Hello all,

I posted a question on cluster setup some time ago but never got a helpful
answer. It seems like I've installed all the services properly, I didn't get
any errors when I did it, but everything is not being backed upYes the
services are started. This is on a Win2K cluster, and the client is 4.2.1.15

The 2 nodes local disk back up works fine. I installed a schedule on the
first node to back up the only instance on that node and the first night it
worked. So the next day I installed 3 schedules on the 2nd node to back up
the 3 instances there. The installation was fine and the services started.
All 4 instances use the cluster name as the node name. I can go to the node
and use the GUI to back up the data. Once in the GUI it shows ALL the SAN
connected drives, even though I am only backing up one instance and the OPT
file has the drives associated with their instance. I'm guessing this is
normal since they all use the same node name.

The scheduler starts and is just waiting there to be contacted. Since the
4th only one instance has backed up. The other ones never start or even try
to start far as I can tell. The logs just show it's sitting there waiting to
be contacted by the server, which is AIX 4.3.3 TSM 4.2.1.8

 The the big question is what did I do wrong? Why aren't all the schedules
working? Should I have a seperate node name for each instance? The Redbook I
have, old at best since it's for an NT cluster, says I can do what I did but
it doesn't seem to work.

Any help

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail: [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (888) 997-9614