Design Questionnaire

These questions represent some of the possible questions that should be asked when designing out a solution. These questions have been complied from many resources, experience, and trial and error. In no way is this a complete list, but it should be a decent starting point. I will try to keep this list updated as my knowledge grows, feel free to post other questions in the comments area if you feel I’m missing something important.

Questions to ask “C”-Level team include:

  1. What is unique to your processes that can impact our design? (Employees need remote access, must have web site accessable with 99.999% uptime, etc)
  2. What are the budgetary constraints, both current and future?
  3. For Disaster Recovery do you have a defined RPO and RTO (Recovery Time Objective, Recovery Point Objective)?
  4. What services provided by IT are the most critical to the company in your opinion?
  5. How much data loss is acceptable? (If any at all)
  6. How much would it cost the company to be down for 1 hour? 1 Day?
  7. How much downtime can each application have?
    • Email
    • Web
    • ERP
    • SQL
    • Custom App
  8. What types of security concerns do you have?
  9. How many employees are there accessing IT resources? How much do you expect this to grow over the next 12 months? 24 months?

Questions to ask IT team include:

  1. What is unique to your processes that can impact our design?  (Policy and procedural)
  2. What types of SLAs do you have in place?
  3. For each server what is the RTO? RPO?
  4. Do you plan to reuse existing hardware for virtualization? Or will we be purchasing new hardware?
  5. What is your preferred vendor for servers? Switches? Storage?
  6. How many CPU’s, how many cores and what is the CPU speed for each host?(refer to capacity planner)
  7. How much RAM will be configured in each host? (refer to capacity planner)
  8. How much local disk space will be configured?
  9. How many NIC cards and ports will be used for each host?
    • Management?
    • vMotion?
    • Data?
    • SAN?
    • Fault Tolerance?
    • DMZ?
  10. Will you be using Fiber Channel or iSCSI or NAS Storage?
  11. What are your current storage requirements? (refer to capacity planner)
  12. Is there any storage requirements not listed in the capacity planner?
  13. How much do you foresee your data growing over the next year? 2 years?
  14. Are there any applications that are disk latency critical? High IOps? High MBps?
  15. Do you plan to use SAN based snapshotting in conjunction with VM level snapshots?
  16. Do you plan on using thin provisioning?
  17. On the SAN do you have a standard LUN size? If so what are the standard sizes of LUNs?
  18. Do you have a naming convention you would like to use for VMFS volumes?
  19. Do you want to deploy ESXi or ESX?
  20. Do you plan to use any local VMFS volumes?
  21. Is there a requirement or a need to run any monitoring or management software in the ESX service console?
  22. What type of core network is in place now? (eg. Gig switches, 10 gig, 100 Meg?)
  23. Will we be purchasing new switches or using existing? Do you have enough ports available if using existing?
  24. Do you use VLANs? If so, what are the VLANs and how are they used?
  25. Do you have a need to group virtual servers into groups (subnets/VLANs, etc)?
  26. Do you have a server naming convention that needs to be followed?
  27. What subnet do you use for management?
  28. Do you have a physical machine acting as a PDC or BDC? If not can a machine be reclaimed for this purpose?
  29. Do you plan to run Virtual Center Server as a VM or a physical machine?
  30. What database do you plan to use for vCenter? SQL, SQL Express, Oracle?
  31. Will the vCenter database reside on the same server, or on a remote server?
  32. What type of backup technology do you currently use?
  33. Do you want to preform file-level, VM-level, or SAN LUN-level backups?
  34. Are you using storage replication? If yes, what type?
  35. Do you have a policy that requires off-site backups? Tape retention?
  36. Any other information we need to know about your backup policy as it is now?
  37. What is your expected average annual user growth rate?
  38. Will you size your servers for your initial needs or account for all of your expected growth?  (Discuss capacity/server consolidation analysis results.)
  39. How many users will access your applications?
  40. Are you planning on virtualizing any workloads that are mission-critical and cannot afford any downtime?
  41. Are you planning on virtualizing any multi-tiered applications?
  42. What operating systems are currently running your existing applications that you wish to consolidate?
  43. Do any of your physical servers have to have more than one CPU?  (Discuss the risk introduced by vSMP with virtual machines.)
  44. Are any of your current physical servers/application workloads clustered using Microsoft or Veritas clustering solutions?
  45. What type of security concerns do you have?
  46. Is there a disaster recovery plan in place? Has it been tested?
  47. Do you have a list of priority VMs based on groupings? (High, medium, low)
  48. What other sites do you utilize for DR?
  49. What is the connectivity between sites?
  50. Is there a need to replicate ESX/ESXi hosts at the DR site?

2 Responses to "Design Questionnaire"

  1. Is the intention for this in regards to virtualizing server environments, or a good reference for general virtualization practices? I find in general we as IT professionals tend to ask too little about the applications and the business itself. I would add a couple basics to the C-level such as:

    1. How are your users geographically distributed?
    2. What business processes do your applications accomplish, and how do they work with day to day revenue?

    Quite often companies don’t go into enough detail and we miss some extremely important high level information that would allow us to provide a more consultative approach.

Leave a Reply