Hello again, I wanted to clarify a couple of items. A couple of people suggested that I look at the FAQ. The FAQ isn't really the type of information I'm interested in. This tends to be much more "How-to-technical", where I'm looking for "how-to-management". I also received several technical practices (and some management). An example of what I *think* I'm looking for is: Our site has an average of 150gb of data per machine. Since we require mirroring on all our systems, we back this up completely every 14 days. We do partial backups every night, with an on-line backup tool. Our data is 20% dynamic, meaning 30gb of data changes each day. or We hold all non-device-specified output spool files for 24 hours before printing. Since we have an end-user report writer, sometimes our users accidently request hardcopy or their report is much larger than they thought it would be. This allows the user to contact Operations and cancel the printing. I would prefer to have a short paragraph such as these, instead of just a one line suggestion. What is the 'practice' and what's your justification for doing this? I'm not going to be making any judgments on the practice. *And* I want them sent to me, because I know we (well, at least a lot of us on this list:) love to comment on other practices. We either agree or disagree and would like everyone to know :) I *really* want to get this list together. When you get your copy, you can decide if you agree or not and implement the ones you like. I have also received some requests for copies. I would like to wait on getting these, as it may be a while before I get this list in a publishable manner. BTW, I think I have received more requests for the list than 'best practices'. I was afraid this would happen. Everyone wants to know what the other guy is doing, and we forget to share our own. Finally, don't forget to let me know if your name/company can be used. I will add the ones that specifically says "yes" and have the information. Thanks for the help, Larry Boyd <[log in to unmask]> "Each problem solved creates the opportunity to solve the next problem that the last solution created." - Richard Pascale (These opinions are my own and not those of Hewlett-Packard.)