[IUG] re: Using III Enterprise API backup vs. Legato backup
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
>I've got a quote from my rep, but they have it split as one or the other.
>It's confusing to me why you can't just pick one and switch if you need it to.
III should be able to tell you why you need to commit to one backup solution or
the other. Please post the reason to the list. I'm curious about this, too!
Part of me wonders if they didn't quote the Legato solution separately because
they have a separate Legato Interface product.
>Also their documentation is very abstract in how it works, not like "copies
>to a folder, then you start a backup job" etc.
In essence, that's all it does.
>One key thing I want to know is - with the Enterprise API can I schedule a
>network job anytime and it will backup whatever files the Enterprise API has
As I understand it, yes. We set our API to kick off after the last library
closes, but so that it is finished writing out the data to disk before
NetBackup swings by to back up the machine.
>I'd also like to get more advanced and store the last 7 days on the server
>in a folder, and have our network job backup the entire folder. That way if
>the backup software doesn't work on a given day, we still have the backup on
>the server. Any idea if that or something similar is possible?
We currently keep three days worth of back ups on our server. Each backup is
about 20 gig or so, so three days pushes 60 gig. We went round and round on
this one, and finally decided to only back up the most current day over
NetBackup, instead of three days (at 60 gig) every day. The previous two days
will always be on the NetBackup backup sets if we need to get them. But, you
can definitely keep seven days on your Millennium/Innopac server, so long as
you have the space.
Digital Library Technologies Group
Hanover, NH 03755