Hello Richard That's just as I'd assumed. Thanks for the quick response.
Steven On Nov 30, 2011 1:03 AM, "Richard Sims" <r...@bu.edu> wrote: > > Steven - > > The TSM storage pool info remains in stasis until the situation is resolved by a TSM server administrator. Whereas the database entries remain intact, incremental backups will not cause new backup copies to be made. The Destroyed state is just a flag, which can be removed; and it is the case that a volume in that (perhaps temporary) state does not mean that files on it cannot be copied (when that state is un-done for a Move Data, for example). > > I guess the thing to do is assess what the actual significance is of "destroyed" in this volume's case. > > Richard Sims > > On Nov 29, 2011, at 5:42 PM, Steven Langdale wrote: > > > Hi all > > > > Can someone confirm my thinking... > > > > Client backs up to a volume (stgpool has NO copypool) > > Volume is marked destroyed. > > > > So now restores will fail (obviously) but i'm assuming incremental backups > > will NOT re-backup the missing files because TSM still knows about them. > > I'm also assuming they will only get picked up in the next incremental only > > after the volume is deleted. > > > > True / False??? > > > > Thanks > > > > Steven
