This FAQ is a living document and will grow and change in line with the services and their usage.
- Campus Network
- The Campus Network connection allows your VLAN to be extended into the data centre or private cloud. It is delivered an additional annexe connection and the cost is rolled into the data centre charges, thus the typical Frodo port cost is included. A single connection will be supplied to a rack and all switching is then the responsibility of the tenant. If multiple racks are rented then cross patching between racks will be put in place to allow connections. Each rack can only be connected to one VLAN.
- Data Centre Network (Managed Switching)
- The DC Network is a fully managed network. Tenants cannot run network switching equipment in racks provided with multiple DC network connections. All switching is centrally managed to minimise the likelihood of failures due to networks being joined or similar situations. The DC Network offers a no single-point-of-failure design for dual-homed systems.
- Data Centre Network (Unmanaged Switching)
- This offer the additonal IP space of the data centre network along with its upstream resilience but only provides a single port connection to a rack. Tenants can run network switching equipment and firewalls in racks provided with a single DC network connections. This network model is designed for those who want to make use of the DC Network but also want to run their own firewall device in the data centre.
- Mixed Networking
- A rack or virtual data centre is either on the DC Network or the Campus Network. They cannot be mixed.
- Private Unrouted Network Connections
- Hosts on the data centre network (with managed switching) can also have private, unrouted, connections made between them. This is useful for management networks (note the end-user must supply a bastion host or VPN device), cluster heartbeats and the like.
- Virtual Data Centre Pricing
- vDCs are priced as a multiple of virtual machines, storage, CPU and memory to match the required resources. The vDC cost includes licenses not required if you just scale up a single virtual machine by adding resources.
- VM Image Backup
- Virtual machines should be backed up from within the VM operating system using traditional methods such as the HFS. Next year we will be adding image level backup and restore to the platform using the HFS as a secure data destination. This will be an optional extra for virtual machines with the cost set just to cover the license and media costs incurred.
- Private Cloud Disaster Recovery
- The private cloud is built across two sites. All data at one site is mirrored to the other. In the event of failure, all data is secure (replication is asynchronous so it is to within the last minute or so) and the Private Cloud team will evaluate the likely duration of the failure. If the failure will be prolonged they will contact initiate a full failover and virtual machines will be restarted at the other site.
- NSMS VM-for-rent
- OUCS already offer a virtual infrastructure where virtual machines can be rented. This is offered via our NSMS group. This infrastructure is being replaced by the Private Cloud and all virtual machines will be migrated to the Private Cloud infrastructure in consultation with their owners.