5,2,30,180 makes more sense than what you have now for the following
reasons.  How likely is it that you would go back 90 days for a db restore?
Not very.  If you need to keep data this long, consider an export to ASCII
and archive.  Having raw binary database data in an archive doesn't make a
lot of sense.

Determine exactly how far back you might actually need to go.  Usually not
more than two weeks for a database (if you went back even that far you
probably couldn't catch up anyway).  Ensure you will catch any corruption to
the db within that time and set all parameters to 14, 14, 14, 14.  Since you
get a new db backup everyday, the 30 and 180 you had would never apply
anyway.

Folks often keep too many copies of a database backup.  This wastes a lot of
space and resources on the server.  Cut it down to meet your business needs.
Use archive to keep data around for longer periods and seriously consider
dumping or exporting the db rather than keeping binary data for long periods
of time.  It's unlikely that you would be able to restore a two year old
binary representation of a db.  There is a White Paper on backup vs. archive
on our website.  Take a look at that for more ammo.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80919
(719)531-5926
Fax: (719)260-5991
www.storsol.com
lipp AT storsol DOT com