I think what you suggested is the best thing to do.
Just make a new copystgpool, with a copy of your new prim.stgpool.
After that, you can delete the old copystgpool. Or if the databasespace is
the problem, and you can risk the very littlebit of risk: after migration
delete the old copypool and d
How much data? What if you did a db backup, deleted all the old copy stg
volumes and then ran a new backup stg? The concern is what happens if I
take a disaster while I'm creating this new copy pool. With the db backup
you could always restore to before you deleted the stuff on the off chance
t
