Add a copy to the Plan using the new HS.
Aux Copy jobs from old HS to the new HS.
Promote the new copy to be Primary copy. (May need Java?)
Delete the old copy using the old HS.

Thanks,
Scott
 

Hi Scott,

In the new HS i already have other storage policies with its own primary copy and another aux/selective copy to cloud. migrated data probably will not be needed to restore, promoting this kind of copy is necessary?

Anyways trying to create a new copy task i can only select data sources from new HS policies

dead topic? i posted yesterday only… 

You can’t migrate between Storage Policies. 

You will need to create / promote a copy within the existing “old” Storage Policy. 

But in this way i can’t ever purge old data/policies from old hardware or libraries. I used commvault software since 2008 and you can imagine the variety of systems we have used and decomissed. Long time retained jobs are always a pain in my ***. Is my only choice to wait until this kind of data could be deleted?

I'd prefer don’t keep a storage policy with a lot of copies only to retain certain data sets. We had to do in the past, but i keep a little hope modern versions of simpana would have a improvement in this aspect

Anyways, thanks for the explanation
And love and respect to your nickname XD

The Storage Policy will need to exist for the duration of the retention period, but there isn’t anything stopping you from purging your old data / hardware if you follow the above advice.

As others have explained, configure a new Aux Copy using the new HS Storage within your existing Storage Policy.

Run the AuxCopy, once completed and all relevant jobs are on the new Aux Copy (and therefore on the new HS Storage), you should be able to delete the old Copy and free up the old HS Storage.