If you backup to a different nodename you will reset the CBT info. So you can 
do that monthly full backup to the different nodename, but when you switch back 
to the original, it will also require a full. So in essence you need to do 2 
back to back fulls to get this done. I've been down this road. 



_______________________________________
John Monahan
Professional Services Consultant
Logicalis, Inc. 



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Prather, Wanda
Sent: Monday, March 10, 2014 11:43 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM for VE and "monthly fulls"

Would like to know if anyone has solved the conundrum of TSM VE and customers 
who want "monthly fulls" in the vault for a year or more.

Now I know that's a bad idea, and it doesn't play well with TSM 
incremental-forever.  But still there are customers who insist, or have 
managers with ill-thought-out pseudo-requirements for it, or parent firms who 
insist on it.  And I can work those issues with backupsets or exports or 
nodename-monthly node owners or sometimes even archives for other types of data.

But I have not been able to do an export on deduped VE filespaces.  It takes so 
long and puts on so many locks it has to be cancelled.
So I'm pondering the idea of doing a true VM full, to a different datamover 
with a different filespace owner.  But I don't really like that idea either 
because the full will have the snapshot outstanding for a long time, and the 
scheduling will be tricky so we don't overlap the incremental snapshots.

SO, anybody else have insight into this particular can of worms?

Thanks
Wanda

**Please note new office phone:
Wanda Prather  |  Senior Technical Specialist  | Wanda.Prather AT icfi DOT 
com<mailto:Wanda.Prather AT icfi DOT com>  |  www.icfi.com<http://www.icfi.com> 
| 410-868-4872 (m) ICF International  | 7125 Thomas Edison Dr., Suite 100, 
Columbia, Md |443-718-4900 (o)