from: Jeffrey Hutzelman <[EMAIL PROTECTED]>
> from: Jim Rowan <[EMAIL PROTECTED]>
>
> luan> I think the file backup/virus
> luan> check/garbage collection programs should avoid entering a volume
> if it luan> had not been updated since last cycle.
>
> Yes, but not too practical, unfortunately. This implies that all your
> software knows about AFS ... Then we'd have to wait for the version
> that runs on DFS...
>
> Depends on the savings you get. When our vos backupsys for the cell
> started taking 12-14 hours a day, we wrote a "smarter" vos backupsys,
> so that it only backs up the touched volumes. We then shorten the
> backupsys time to 1-2 hours, and it's only 121 lines of perl.
Hmm.... We have each fileserver run vos backupsys for its own volumes
each night. By doing all the fileservers in parallel, the whole process
only takes around an hour. We have about 500GB in 6000 volumes, spread
across around 40 fileservers.
This works well, unless you want to start a backup as soon as the
backupsys is finished, unless you write some code to inform the backup
servers when they can start you have no real way of getting a "safe"
backup. (Safe as in, after all the backup volumes are created...)
So, what I did was serialize the backup procedure, so it first creates the
volumes, then runs a script to check for a tape in the DLT, and then runs
the backup, and then ejects the tape. I'm using a single DLT drive, non-
stacker to do these backups.
Scott
