I've only just finally given the Onepass migration a go, and I'm a little concerned with some of its implementation restrictions. Perhaps I'm missing something, or perhaps there's a way around it that someone has across.
It comes down to storage policy allocation.
Previously the backup agent would write to the backup SP, and the archvie clients could be configured to write to a different policy. In some situations, these SPs may be writing to seperate maglibs. Not an unreasonable design in certain situations.
Implemententing OnePass now means you have to write all data to a single SP, and this can cause issues due to:
Wanting to seperate backup and archvie data to different maglibs, perhaps on different arrays/locations etc.
Content Indexing of the archived data only, and not all backed up data. As CI is enabled at an SP level, you'd have to consume more CI DB space and licences if processing all backup and archive data!
Also, you will end up have historic data spread across two storage policies.
Has anyone come across these situations at all yet?
Comments welcome :-)