data migrator and backup policies

[myuserid7]

hi,
I'm trying to figure out the following commvault concepts in my head,

With data migrator, aged data is moved to secondary storage, leaving stubs on the primary storage.
When a backup subclient starts, lets say, a fullbackup at the end of the week, what is it backing up?
The files from the primary storage with the stubs or all the data and whatever the stubs are referring to ?

appreciate any clarification if i have it all wrong.

thanks
(PS: this forum is a great resource, I'm picking up a lot of concepts from other commvault users posts. Thanks)

 

[Cyklops]

It will only take files from the primary storage with the stubs, it will not backup the original data (this would cause recalls of all migrated data which is not what you want with data migrator).

regards

 

[birky]

the file doesn't exist on the primary anymore...the stub includes the link to where the file now resides.

This is a good reason why more and more people are implementing HSM solutions such as DM, so that their backup window/ media usage is shrunk by not backing up so many copies of inactive files.

 

[myuserid7]

Thanks for the replies,

But what do I do if I want a full backup of all the files?

The secondary storage where (migrated) files reside may fail so I want to make sure I have a copy of all the files on tape media as well.

What would I do in that scenario?

Thanks

 

[dutchtreat]

You can make an Auxiliary Copy of the migrated data. That way, you'll have your migrated data in two different places. Many people migrate data to disk for quick online restores (sometimes with a limited retention time) and make an Aux Copy to tape for disaster recovery.