Here's a question. I just started thinking about what I've been doing and have a concern.
We've been going through a lot of server migrations and things lately, as well as refreshing older machines and rebuilding them. Just for safety I've been moving nodes from one domain to a domain I created called 'NO BACKUP'. We don't use archiving currently. I set the retention to 365 days in the new domain in hopes that I can move nodes to this domain for safe keeping until I'm ready to get rid of them. Should I? - Be copying the node's data to a new tape pool for this and activate collocation? - Use Archiving instead? Also, when I move data from one domain to the next, is it using the new management class' retention period, or where ever the data actually is (it's old domain and backup pool)? I know what I said above but I'm second guessing myself. I have a few weird errors in my console log and I'm curious if it's because I have the node in a new domain, but didnt move the data from one pool to the other. Thoughts? Opinions? On 12/11/06, Markus Engelhard <[EMAIL PROTECTED]> wrote:
Take care! As far as I know, Archives are not rebound. To be on the safe side, create a management class with exactly the same name and with the reqired retention parameters in the new domain. The copygroup destination can be to the desired collocated storagepool. To be sure, you could even change the archive retention of your default management class until you have checked the archives table. Data will have to be moved as pointed out. If your aim is just to collocate, why not hav a close look at collocation grouping? Great effect at very little cost. Regards, Markus Engelhard -- 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.
