Hi All I'd like to start using DECOM VM to manage our obsolete VM backups. Our current practice is to rename the filespace to \\VMFULL-<vmname>_DECOM<file:///\\VMFULL-%3cvmname%3e_DECOM> and let it sit for a year before deleting manually. In order to accomplish that with DECOM VM I would need first to alter the retentions from the current unlimited,unlimited,32,32 to unlimited,unlimited,32,366
Now if I were to do that for a copygroup used by Windows or Unix BA Backups, the space and database usage would blow out because of all the temporary files that those OSes spin off by the hundred, and which would then hang about for a year. I'm reasonably sure that VM backups (VMware) name the files in a manner that is invariant, and the number of files should normally only ever increase, so increasing retonly for VMs will not have this issue. Am I correct? Is anyone else using this method successfully? Any other gotchas I might not have thought of? Thanks Steve Steven Harris TSM Admin/Consultant Canberra Australia This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. You should immediately delete the message if you are not the intended recipient. If you have received this email by mistake please delete it from your system; you should not copy the message or disclose its content to anyone. This electronic communication may contain general financial product advice but should not be relied upon or construed as a recommendation of any financial product. The information has been prepared without taking into account your objectives, financial situation or needs. You should consider the Product Disclosure Statement relating to the financial product and consult your financial adviser before making a decision about whether to acquire, hold or dispose of a financial product. For further details on the financial product please go to http://www.bt.com.au Past performance is not a reliable indicator of future performance.
