Short question regarding advanced file device and staging 1

[ozihcs]

I've very recently set up a 1TB disk cache for my daily networker backups. I plan to extend this to 2TB once I get my backup server upgraded to an os that supports such a large filesystem (Solaris 8 currently), however in the meantime it's very important that my staging policy triggers correctly.

My question is the following: How does the staging policy determine how full a given ADV_FILE device is? Does it probe the OS for disk usage, or does it check the Current or Default Capacity settings in the legato device definition?

The manual is not very clear on this issue, and strangely enough, when I set the default & current capacity to 1021GB manually the volumes list still show my file device to be at 0% capacity (it actually contains 480GB).

 

[605]

NW does not check the fullness of the FILE DEVICE but the fullness of the FILE SYSTEM! - If you want these values to match, the easiest way is to use the complete file device for a disk device.

You may set the Volume Default Capacity at any time but the calculation just works properly after you (re-)labeled the media.

 

[ozihcs]

Thanks for the tip; setting capacity and relabeling the volume did the trick. However I seem to have stumbled over a bug in 7.1.2 where the 'data written' counter seems to increment continually in disregard of the staging process, leaving me with a volume with a 1TB volume reported to contain 3TB but actually containing 600GB 8) So I guess the fullness counter is pretty worthless for ADV_FILE devices hehe.

 

[605]

Altough i want to see love any bug to be fixed, it does not really matter on an AFTD. Do not forget that its intention usually is nothing else but creating a big "cache" from where the backups will be staged to tape later.

And do not forget that it is designed in a way that it will never become/set to full, although you will be able to fill it of course.