Hello Eric, You will only require scratch tapes in the primary pool or that TSM can move into the primary pool to do backups. TSM really does not think of working with tape-sets, it thinks of working with data. If all your primary storage media is wiped out and you have your copypool data. Then all new backup data can go to new media. The new copypool data can append to the old copypool media and new media.
You can recreate the primary pool media from the copypool media as a background task. But it is not required for your operations. It is just required to enable you to handle a second disaster. Several sites have posted on this list, that they make two copies of the primary storage pool data, To product against the loss of the primary and copy storage pools. len -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. van - SPLXM Sent: Friday, September 01, 2006 10:32 AM To: [email protected] Subject: Re: [ADSM-L] Making TSM twin-center compliant Hi Allen! Thank you very much for your reaction! Correct me if I'm wrong, but as far as I know, you cannot backup to a copypool. Am I wrong here? I cannot wait for the restore storagepool to finish... This will take days and I will have to be able to make client backups immediately. If I was able to convert a copypool into a primary pool, I would be able to backup clients right away. Ok, I would loose my copypool, but in case of a disaster I can live with that for several days. In the meantime I can have my vendor bring in (rental) stuff to rebuild the copypool. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: vrijdag 1 september 2006 16:00 To: [email protected] Subject: Re: Making TSM twin-center compliant >> On Fri, 1 Sep 2006 13:17:17 +0200, "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> said: > We are about to implement a second (fallback) IT center on another > location. The idea is to create a hot standby environment for TSM. > We are already using a separate copypool which will be moved to the > new remote location, so if the primary pool gets lost, we have all > data (up until the last backup stgpool of course) on the remote > location. However, in case of a disaster, not only will we have to be > able to recover clients (from this copypool), but we also need to > continue backup here. > This would be no problem if one could promote a TSM copypool to a > primary pool. In this case one could just continue making (the forever > incremental) backups, but TSM doesn't offer this function (yet). Sure it does. In fact, you can do exactly as you describe; biggest impact will be that the copy stgpools are usually (very) poorly optimized for client restore. Think of it carefully: Two TSM servers: PRIM, and COPY; COPY is housing the offsites. You lose PRIM, but, since you're good at these things you have the database backed up offsite. You restore the PRIM database on hardware at the remote site. Immediately at that point, you have access to the data in the copy pools, and more importantly, you have the -database- that tells you what you have and don't have. The next incremental will only copy the data you didn't have as of the database backup which you used to do the restore. So, between the time you get PRIM restored at the remote site, and the time when the first of your clients have gotten their acts together, you can be RESTORE STGpool ing as fast as your little tape drives can scurry; as you make progress there (according to your previously determined list of priorities...) your replacement PRIM becomes better and better suited to serve the client restores. >From another perspective: Why "promote" a copystgpool to PRIMARY status? You'll just need to re-organize the new PRIMARY pool and then make a copy pool. Less work to take the well-organized (for a copy stgpool) existing copystgpool and make a new PRIMARY. - Allen S. Rout - There is no copy, there is no primary. There is only data. ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. 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 **********************************************************************
