>>> Does it make sense to include them in DRM process. In case of disaster, these applications are already running in DR site and no need to recover by TSM.
That could depend upon the nature of the application and failure (or failures) - if an application or service needs to be recovered to an historical point in time in the remote location (i.e. prior to a corruption or dataloss which has in turn been replicated to the DR site) then recovery from TSM might be your only way to achieve this (again, depending upon the application implementation). It's important, as part of documenting a data protection strategy for a given service, to look at the failure scenarios (and multiple concurrent failure scenarios) against which you wish to provide service resilience - as you indicate, TSM forms only part of this, but it's important to understand its place in the whole. /DMc London, UK -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Mehdi Salehi Sent: 05 May 2010 13:19 To: [email protected] Subject: [ADSM-L] Application-side disaster/recovery and DRM Hi all, Many applications have their own disaster/recovery strategies like DB2 HADR or Oracle DaraGaurd. Does it make sense to include them in DRM process. In case of disaster, these applications are already running in DR site and no need to recover by TSM. Moreover, in my opinion, DRM for above-mentioned applications could cause bandwidth loss if electronic vaulting is used. Thanks in advance.
