1 included CPU is fine for most uses. Some parallelized applications can benefit from more. Check the documentation for the application you intend to use on the VPS."


1GB is normally sufficient for linux and Windows purposes. Application intensive or memory cacheing applications may prefer 2-3GB total. Most applications do not need more in virtual environments because of virtualization memory optimizations including shared memory savings and burst modes for occasional peaks. The sweet spot for most configurations is 2CPU/2GB RAM/Standard Storage Tier. Custom requests can include more RAM than listed here, but that has not been necessary so far. Even high use campus wide systems rarely need more than 10GB.

OS Management

See 'more info' on management services. Some storage restrictions apply for IST managed virtual machines. Self-managed VPSs, formerly referred to as Virtual Machines(VM), are provided as bare metal provisions with requested storage amounts. Several preinstalled OS flavors with a base install are available when ordering.

OS Drive Tier

Highly used file, web, and database server should generally use Performance Tier (greater than 500 IOPs). Less busy workloads such as archival servers or lightly used development servers should use Utility Tier.

Backup Options

The UC Backup team recommends both on and off-site backups for production servers for maximum protection. If you have a single backup copy, then all of your backup data could be lost in a single hardware failure, natural disaster, etc.


UC Backup charges are based on actual utilization and the percentage of file changes your server. Rapidly changing data will have larger fees, but most systems have largely static content. This quote errs on the side of caution for data that changes frequently. Static data, custom rules, and custom retention policies can save signicant costs. This calculator uses base license plus 2.5 x (Total Storage(GB)) x (backup rate per GB) to compute the estimate.

Non-UC Berkeley Customers

UC billingContactPhones outside of UC Berkeley, pay the standard 7% cross campus administrative finance charge(AFC) on recharge services. Non UC Berkeley units can request quotes for planning and review using this estimator, but they cannot order a VPS on demand until they have coordinated affiliate login IDs and appropriate billing chartstrings beforehand with the IST TAMs.

VPS Template

Pick the pre-installed operating system and version. If you are unsure which template to use, please make your best guess here. Your request will be reviewed before approval. You can add comments in the notes section if necesssary.

Server Name

Please enter a name for the VPS. This will typically be the same name as the computer name for easy reference. Your external web presense and SSL cert could be an DNS alias(es) to this etc. The server name must be unique in the Virtual environment as well as CalnetAD for domain joined machines. Please DO NOT enter the FQDN here.

Data Classification

Please see the information posted here. Note the new IS3 levels that replace older UCB protection levels..

Availability Level

Please see the information posted here. Availability levels are new to IS3..

VPS Location

UC Berkeley IST provides two datacenters. One located on the UC Berkeley campus, and one located at the San Diego Supercomputer Center. Note that some services may not be available at SDSC, please consult with IST for details.

Network Type

Most server systems, especially systems that hold sensitive data should go on non-routed private 1918 addresses to conserve IP space and provide another layer of security. Public IPs are generally only required for public facing web servers. Campus staff systems can get access to the 1918 address space via the campus VPN or a departmental RDP gateway server.

DNS Subdomain

Please type in your PREFIX and confirm the SUFFIX. Machines must be in the namespace but can be or etc. Trusted certificates are now free for campus via a Comodo site license. For web servers, for example, typically, we use a naming convention for the 'Server Name' and DNS A record and a DNS alias for the web address.

Functional Owner

Functional owner is usually the billing manager, manager, or IT manager over the project team.

Technical Contact

The technical point person or list for technical issues.

Billing Contact

Billing contact can be the functional owner or a separate individual responsible for billing.


If you are used to the short versions of COA, remember to put in the Acct here, usually 59001 for Berkeley. Fund might be 19900 for example. Business unit is almost always 1."

Backup Tag

vCenter tag provided by the UC Backup Team to colo customers for backing up VMs.