>Good question. Our primary goal is to find a cost-effective way to
>send our data off-site (Domino & vanilla NT files). Additionally, we
>need to extend our data retention. We can retain only 5 versions of
>our Domino db's in our library (which is pretty much full and not
>upgradeable), but need to keep 3 months.
Eric - I haven't experience with Domino backups, but consider if
the following scheme might accomplish what you need...
>From previous *SM API experience, I suspect that your Domino backups
are each their own "filespace".
Given that disk is cheap these days, consider setting up a 2-level
storage pool hierarchy: The first level is sufficient disk space to
hold recent backups, in case of restoral need. You define this disk
storage pool to have caching active, and to fully migrate to the next
storage pool in the hierarchy, which is your tape. Collocated by
filespace (if you like) the backups land on tape, and from there you
can do a Move Media with tape ejection, to store that tape offsite,
with tracking information and mount requestability.
New backups will automatically find space as needed in the disk
storage pool, as caching means the objects there are premigrated
and can be supplanted by age.
Richard Sims, BU
"Think different." - Apple
