MiServer Backup & Recovery

MiServer offers optional file level backup and disk replication for an additional cost:

  • Backup: File level backup using a backup system from IBM called Tivoli Storage Manager (TSM) and will back up the client node based on the schedule you request.
  • Disk replication: Data is replicated to another data center. Replication is intended for disaster recovery purposes and is not intended for restoring lost, deleted, or corrupted files on a daily basis.
Note: VMs created in the ASB Data Center do not have a disk replication option.

On-Premise Stretch Cluster

The MiServer Service is getting an update to bring new functionality to users. A new, on-premise stretch cluster will be developed and implemented for the MiServer environment that will improve the reliability and capacity for applications running on the MiServer environment by seamlessly stretching the network across data centers.

The MiServer on-premise stretch cluster will be available to MiServer users in the early spring semester. We do not anticipate a noticeable impact to current users. Please see below for additional information on the benefits of this upgrade.

The Benefits

  • Quicker disaster recovery and greatly reduced recovery time objective (RTO) and recovery point objective (RPO) times. 
  • Pre-emptive migration for enterprise continuity during critical infrastructure maintenance.
  • Seamless server migration to different data center locations provides a more flexible environment.
  • Easy to request and transparent to the customer—no additional configuration needed.
  • Stretch Cluster capability hosted with newer more robust hardware, which improves overall service performance.


A snapshot preserves the state and data of a virtual machine at a specific point in time. There are two main types of snapshots:

  • State: Which refers to the virtual machine's power state (for example, powered on, powered off, suspended).
  • Data: Which includes all the files that make up the virtual machine, including disks, memory, and other devices, such as virtual network interface cards.

Snapshots Are Not Backups

The snapshot file is only a change log of the original virtual disk, you should not rely upon it as a direct backup process. Snapshots are automatically deleted after 5 days. To retain them for a longer time a request can be submitted to add the VM to the exclusion list.

To properly utilize snapshots, please refer to the Snapshot Best Practice Guide.