In my search for the most optimum way to automatically move stubbed files only to the tape aux copies, many have recommended the seperate backupset model, default backupset does the regular backups to disk, then have essentially the same subclients defined in another backupset which only does archiving.
Plan seems logical but when testing this v10 SP6 on a RHEL5.8 system with VXFS, the default bu set backs up fine. If I turn on disk cleanup it stubs and works good until you want to do the aux copies of the synth fulls, and you wind up copying the entire FS instead of just the stubs. So, turned off disk cleanup on the main subclient, created another backupset and identical subclient but only backing up archived files (in order to be able to move stubbed files around seperately via aux copies), ran the disk cleanup, all is fine. Stubs work fine but when you subsequently backup the original subclient under the default backupset, those files which were stubbed from the "new" backupset job appear as "files" not stubs in the content list. Plus, if you restore what should be a "stub" it restores the whole file (matching what is displayed in the backup file list when browsed). Now, to me this does not seem like it has connected the dots quite right. I understand this may sound confusing and it is until you actually see it in action. The default backup set does not honor the stubs of the secondary backupset disk cleanup.
Anybody tried this or know whether this needs an incident open?