Create resource! Just thought it would be worth a little description or overview at the beginning of each of the tutorials, or perhaps an overal overview. Interested in why certain (non obvious) choices have been made - using multiple disks for example was a new one to me.
Thanks again,
Martin.
Thanks Martin,
Excellent point. Truth is, the current post was a rough draft. This is how I write: I start out with screenshots and minimum text, then add more descriptive text after the fact. I showed what I had written to a few people and they convinced me the community could use it now.
I plan to update the documents for RC and RTM versions. This should provide an opportunity to add more descriptive text.
So you know, I've always preferred to separate functional volumes on servers. It's a preference - apparently shared by whomever built the VPCs for Microsoft, as they built theirs the same way. I built this version with almost everything on the C: drive in the interests of getting it done (using default installation folders). It was probably wise as this is pre-release software. On production servers, I like to place the OS and little else on the C: drive, applications on D:, and the most volatile data on E:.
Again, it's mostly a preference, but it lends itself to a concise backup strategy. If I have the disk space and time, I ghost the entire server (each drive separately). If I have the usual amount of time and drive space, I only ghost the volatile stuff on E:.
:{>
Andy
Thanks for the insight, I set up production servers a similar way but had never done this with my VPC's before.
Understood about this being in draft, but thanks for it anyway. I've read Rob Caron's chm file that many times that the words all blend in to one with me now-a-days. I'm just doing a Dec 05 CTP VPC at the mo and I'm going to try and use your docs as a guide. I'll let you know if I spot anything missing.
M.
Hi Martin,
I will be very interested in your results!
:{> Andy