cite: ...I do this by creating a virtualfs called "Filesystem_01YEAR" and point that to the same file system...
Brilliant Idea, Shawn! I really love the elegance of your solution, which totally avoids tinkering with nodes and such, potentially adding confusion and complexity. Thanks! I have been using virtual filespace mappings for more than 4 years, making 200+ backup threads easy to manage and maintain in less than half a dozen standardized "backup node ...." scripts working with astonishingly little trouble. If you use virtualized nodenames utilizing backup-specific aliases (e.g. NDMPBACKUP01, NDMPBACKUP02), even filers can be swapped on-the fly (only ndmpd-passwords have to be adjusted) without having to deal with "old" backups and new fulls to start with. In addition, implement a standardized naming convention for the virtual filespaces to make life easier in viewing the different distinct incarnations. The fulls would show up as NAS image objects, while the diffs will only show up according to the management class used for the filespace. I personally don´t see the need to differentiate the storage pools for retention distinction, but you might want to address different physics to add more DR-capabilities. Just my personal opinion... Regards, 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.
