We are a smal software company. A problem we have is supporting new early instalations. We do al developmen i DOT.NET. A customer need their specific enviroment like VS2003 and SQL 2000 perhaps. After a year or two, servers and developer PC's are cluttered with databases and code in all sizes and shapes. One way to get this to work is to do our development on virtual servers. One virtual machine (or vhd-file) per customer project. After developent and production setting, the VHD-file can be pushed to tape, and when tha customer calls again after maybe a year or 2, we restore it and pick up where we left it. Fast and efficient!
As we need to update most of our system anyway, I want to move to Server 2008 and Hyper-V for the virtual enviroment, and DPM to keep track of all VHDs. the source code will be administred from Team Foundation Server (TFS). The TFS server is pland to be a virtual mashine itself.
This is a sizable effort in work and capital. I would be interested in comments from somone outther how have tried som of these concepts already. Mabe you can help me steer this project in a better direction?
- Will I need backup software like BackupExec 12.5 to take backup Disk-to-tape?
- Is it too early to use Server 2008, Hyper-V, DPM in production?
Your input is appreciated!