Skip to main content

Request a Virtual Server

How to request a virtual server. Basic information about cost, maintenance, and high availability. 

This article applies to: Managed Servers

Request a Virtual Server

To request a centrally-managed virtual server, use one of the following forms.

  • Self-serve customers: Some groups on campus have created templates for servers for their needs. These groups use a self-serve order form that applies pre-defined default options for subnets, policies, and administrators. If you are requesting a server for a group that is set up in self-serve, use the self-serve form. You can also consult the documentation for self-serve.

    Am I in a self-serve group? Current self-serve customers are: Arts and Sciences, CALS, COECIS, Facilities, Forest Home (Human Ecology and others), SAS.
  • Other customers: All other requests use the manual request form.


Monthly Rates: See the Fees and Billing page.


Maintenance of Virtual Servers

Operating system patches are maintained by CIT. Scheduled down times are required to install patches. More information is available:

Maintenance of Underlying Virtual Data Center

The high availability options outlined below allow virtual servers to be moved while the underlying physical server is upgraded and maintained. There should be no server interruption during maintenance and upgrades.

High Availability

The current VMware Virtual Data Center has multiple independent clusters in separate data centers. Each cluster is connected to both the tier 1 and tier 2 networks for redundancy and redundantly connected to storage located in that datacenter. Virtual servers can be transparently moved between physical hosts within a cluster so that the VMware physical servers and operating systems can be maintained and upgraded without service interruption. If one of the physical VMware servers fails in a cluster, the virtual servers are automatically restarted on another physical VMware server within the cluster. Mission critical applications can be horizontally scaled across independent clusters in the two datacenters optionally behind highly-available load balancers. 

Storage is local to each datacenter. In the event of a datacenter outage, storage in a cluster in one building would not be available to VMs in the other building. A complete disaster recovery solution should include mechanisms to propagate data between the two datacenters. This is not built-in to our current VMware service.

See the High Availability Options and Disaster Recovery page for more information about current options.

Was this page helpful?

Your feedback helps improve the site.