The only file that gets kept for retonly days is the copy of the file that
was deleted from the filespace.  All the other copies are kept for 30 days
with the active file (a copy of the file on the filespace that has not been
deleted) being kept forever (as long as the file on the filespace isn't
deleted).

If your goal is to be able to offer the user the ability to restore a file
to any state within the previous 90 days, say, then you should set things up
as follows:

Versions Data Exists       unlimited
Versions Data Deleted      unlimited
Retain Extra Versions       90
Retain Only Version          90

You set the versions to unlimited since there is a possibility you could
perform backups more than once per day.  Is this setting going to consume
lots of space on your server?  Consider that the vast majority of files do
not change everyday.  Only some of them.  Keeping a big database this long
could be a problem so don't do that!  You would probably never restore a
database back 90 days anyway.  But then someone will scream "but what about
long term archive of databases?"  Export to ascii and use Arvhive, not
backup.  See my paper!

Am I rambling?

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: lipp AT storsol DOT com or lipp AT storserver DOT com
www.storsol.com
www.storserver.com