On Oct 30, 5:23am, Mickey Beddingfield wrote:
>
> In our case we plan to use a near line storage device that will allow
> access to the volume at a reasonable rate??? Anyway, the Load Bal. scripts
> will detect a use of the volume & it will be moved back to real disk the
> night after an access.
I am interested in how the Load Bal would detect a use of a volume that had
be migrated to tape. I was thinking this must be triggered by vldb not being
able to locate a migrated volume. Once this can be detected, the "reloading"
of the volume should happen right away, why wait till the night?
>
> If a volume is dectected to be "not used" it must have been so for a period
> of time that will allow us to go through at least one full backup cycle.
> Once its moved to nearline storage then we don't really need to keep
> backing up the volume? I don't think??? Or I can't see any reason why we
> would need to do so. Anyway, the next time it is "used" it will be
> scheduled for a move & thus be back on the backup list. We should always
> have a good backup copy of this volume on tape even if we have a problem
> with the near line storage device.
If a volume stay migrated for a long time, the backup done before the migration
might get expired and overwritten. This is especially true if you are using
the AFS backup system (backup, butc, buserver) and tape recycling, right?
Shyh-Wei
