Hi *sm ers, I�m presently trying to consolidate 20 odd distributed TSM-Servers that were indiviually managed and have very different logical setups. My aim is to have identical policies across the country, so I thought having standardized policy domains would be a good idea. It�s quite straightforward for backups, so I�m not so worried about those. But what !!!!!really!!!!! happens when a node with archived data is moved to a new policy domain isn�t quite clear to me. I used a TSM 5.1.5 Server on W2K and a 5.1 Client: an archived file will show <unknown> for the Management-class after an "update node" moving it from one policy-domain to another, althougt the management class with the matching archive copy group was defined in both domains. The default management class doesn�t apply either. So it would only be the grace period that stops data expiring with the next "expire inventory", but even that does�nt seem to apply: I changed grace period to one day and did an expire, but the archive is still there. Does anyone have a comprehensive description what happens when moving archives this way or has even gone through this himself? I�m not quite sure I understand the implications decribed in the QuickFacts and IBM support didn�t manage to give a convincing explanation yet. I can�t afford to loose archive data (a real no-go!) and I hate not knowing what is up, so any help will be welcome.
Thanks, Markus ______________________________________________________________________ -- Diese E-Mail enth�lt vertrauliche und/oder rechtlich gesch�tzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt�mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrs�blichen Ma�nahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anh�nge an dieser Nachricht durchzuf�hren. Wir schlie�en au�er f�r den Fall von Vorsatz oder grober Fahrl�ssigkeit die Haftung f�r jeglichen Verlust oder Sch�den durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgf�ltig erstellt worden, dennoch schlie�en wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. ______________________________________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.
