Steve,

if it's really a pool on a VTL, then there are no major implications for
you.
The reason the metadata should stay on disk is that the metadata is
needed for CBT to detect the blocks needed to be backed up and to get
the right blocks in case of a poit-in-time restore. If these data is on
tape, a VM-backup would run for days.
If, in your case, the data is on a VTL-tape, it will generate tapemounts
on the VTL and thus be slower that a diskpool, but these migrated
metadata will expire with the time so the impact will ease.
 

-- 
Mit freundlichen Grüßen / Kind regards

Michael Prix

On 09/18/2015 03:50 PM, Schaub, Steve wrote:
> 7.1.2.0
>
> Recently, our meta diskpool filled up, and an admin who didn't know any 
> better saw that it didn't have a downstream tapepool (vtl) so he went ahead 
> and added one, to which the meta started flowing.
> What are the implications of having our data and meta in the same vtape pool? 
> Is there any way to pull them back apart?
> For future, can we setup a vtape pool downstream for the meta if that pool is 
> not shared by anyone else?  Or does the meta absolutely need to be on a 
> diskpool?
>
> Thanks,
>
> Steve Schaub
> Systems Engineer II, Backup/Recovery
> Blue Cross Blue Shield of Tennessee
>
>
> ------------------------------------------------------------------------------
> Please see the following link for the BlueCross BlueShield of Tennessee 
> E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm