It doesn't sound like they are talking about the same thing. The consultant sounds like he wants to backup SITE-A servers to the local TSM and then send the copypool over to the other server via virtual volumes. Khalid wants to backup SITE-A servers over the link directly to SITE-B TSM server. That way when the backup is complete, the backup data is offsite to the original server. If either site goes down, you'll still be rebuilding a TSM server, but the clients can immediately start recovery because the data is on the TSM server at the other site.
I've recently set up this configuration for a client. Each TSM server creates copypool tapes that also go offsite (more for redundancy), but I also have each server do a DBSnapshot across server-to-server in addition to the DBBackup that goes offsite. Lots of redundancy....it's a government agency! The only issue is the recoveries or just restores going across that link during business hours. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Daniel Sparrman Sent: Tuesday, November 11, 2003 10:39 AM To: [EMAIL PROTECTED] Subject: Re: Server-Server DRM Configuration ... Hi Khalid You and you're consultant are talking about the same procedure.... To backup your primary site to the second site, you'll need to use server-to-server virtual volumes(if you cant get a FC connection to your library on your secondary site). You then define a devclass and a copypool based on that devclass. After that, you'll just have to start the process of backup stgpool primarypool copypool. I cant see any other way of backing up the two servers to eachother rather than using server-to-server communication. This method is also called "Electronic Vaulting" and is a part of TSM Disaster Recovery Manager. You cannot use any form of TSM backup/archive client procedure to backup the server data, as the client wont have access to the information stored on your tapes. Best Regards Daniel Sparrman ----------------------------------- Daniel Sparrman Exist i Stockholm AB Propellervdgen 6B 183 62 TDBY Vdxel: 08 - 754 98 00 Mobil: 070 - 399 27 51 "Khan, Khalid B." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2003-11-11 16:16 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Server-Server DRM Configuration ... I have a humble question regarding the benefits of Server-Server communication. I have two sites 60 miles apart with 45MB pipe in between, and each of them has a TSM server and a library. I was proposed by a TSM consultant to establish server-server DRM configuration to enable quick recovery in case of disaster. My humble proposal in response is to NOT do that but rather backup each site to the other location. That way the DB is offsite as well as the primary copy, therefore DR copy of the primary is NOT needed either. I would do this reciprocally for the other site. In case of DR, data is locally available at the other site. Is this not a better solution than configuring server-server communication and send a copy of the primary pool as well as the DB tape offsite. Please help me understand what I may be missing in my proposal, or what benefits I don't see in the traditional DRM using Server-Server configuration. Please advise! Thank you, Khalid Khan