Re: [ADSM-L] RFE 17805

2012-03-29 16:12:39
Subject: Re: [ADSM-L] RFE 17805
From: Remco Post < AT PLCS DOT NL>
Date: Thu, 29 Mar 2012 22:09:15 +0200

node replication is nice, but there is no automatic failover, yet.

So, in a dual-DC setup you can failover TSM in HACMP, but it's completely 
useless, same for replication, noting automatic. Now, what do you do when 
everything (and I mean everything; mainframe LPARS, databases, file servers, 
application servers,  NAS filers, everything) fails over in a dual-DC setup but 
you have to manually reconfigure either every TSM client in the node 
replication setup, or all of your TSM storage pools. Either way your crucial 
databases have stopped archiving their logs and filled up the active log 
filespace long before 24x7 staff even comes round to calling the TSM admins.

On 29 mrt. 2012, at 20:23, John Monahan wrote:

> I believe TSM 6.3 node replication is one answer to your request.
> _______________________________________
> John Monahan
> Delivery Consultant
> Logicalis, Inc. 
> _______________________________________
> Business and technology working as one 
> This e-mail message is intended only for the confidential and privileged use 
> of the addressee (or others authorized to receive for the addressee). If you 
> are not an intended recipient, please delete the e-mail and any attachments 
> and notify the sender immediately
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Loon, EJ van - SPLXO
> Sent: Thursday, March 29, 2012 3:31 AM
> Subject: Re: RFE 17805
> Hi Remco!
> I totally agree!
> In our shop we had to create a dedicated server to enable backups in case of 
> a disaster. It contains a standby primary pool with 500 tapes, just sitting 
> there, costing money. This pool is located on the remote location and is 
> readonly. When the primary pool is lost, we have to make this pool readwrite 
> so backups can continue.
> In this case you can see that the primary focus of development is still on 
> restore, while backing up became equally vital. Oracle database rely on a 
> frequent backup of the archive logs. When they become full, Oracle simply 
> stops.
> I voted for your RFE and request others to do the same. It takes just one 
> minute of your time.
> Kind regards,
> Eric van Loon
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Remco Post
> Sent: woensdag 28 maart 2012 20:43
> Subject: RFE 17805
> Hi all,
> I submitted a RFE for TSM regarding the behavior of copy pools.
> You can find the RFE via
> and search 
> for RFE ID 17805.
> I'd like to invite all off you to vote on this RFE if you find it useful, so 
> that development can get a good idea of how important this FRE would be to 
> the customers.
> Below you find the input I submitted:
> Description:  For one storage pool to be an exact replica of another
> pool and be equivalent in every way, to the extend that if one pool becomes 
> unavailable all activity continues on the remaining pool, including write 
> activity.
> This would also involve changing the behavior of commands like delete volume, 
> migration, etc.
> Use case:     In a dual-site setup with two tape libraries, one would
> want operations to continue as seamless as possible in case of a site 
> disaster. Current copy storage pools can't be promoted to primary pools, so 
> with the current technology one has to create new storage pools on the second 
> site, even though a copy storage pool is already available.
> Business justification:       there are many dual site setup with IBM and its
> customers. All data in a TSM server environment (disk) can be mirrored, but 
> as soon as the primary tape storage pools become unavailable, there is a lot 
> of manual intervention involved before normal operations can continue.
> --
> Met vriendelijke groeten/Kind Regards,
> Remco Post
> AT plcs DOT nl
> +31 6 248 21 622
> ********************************************************
> For information, services and offers, please visit our web site: 
> This e-mail and any attachment may contain confidential 
> and privileged material intended for the addressee only. If you are not the 
> addressee, you are notified that no part of the e-mail or any attachment may 
> be disclosed, copied or distributed, and that any other action related to 
> this e-mail or attachment is strictly prohibited, and may be unlawful. If you 
> have received this e-mail by error, please notify the sender immediately by 
> return e-mail, and delete this message. 
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
> employees shall not be liable for the incorrect or incomplete transmission of 
> this e-mail or any attachments, nor responsible for any delay in receipt. 
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
> Airlines) is registered in Amstelveen, The Netherlands, with registered 
> number 33014286
> ********************************************************

Met vriendelijke groeten/Kind Regards,

Remco Post AT plcs DOT nl
+31 6 248 21 622

<Prev in Thread] Current Thread [Next in Thread>