The Neverfail Continuity Cloud (NCC) is a platform to deliver a set of service offering culminating is a set of SLOs that provide a two levels of protection.
Powered by Continuity Engine, the Neverfail will clone your production workload and ship it into NCC where it will be stood up on the Neverfail Cloud. Continuity Engine provides real time replication and application monitoring to ensure the quick restoration of business services in the event of an outage.
- NCC provisions a Secure Cloud (sCloud) for each customer that functions as a virtual private datacenter.
- This sCloud provides compute, storage and bandwidth for all Neverfail protected applications.
- The premise and NCC are connected via an IPSEC-VPN tunnel that allows users to immediately connect to recovered server via their local area network in the event of failure or an alternate access method such as RDP or Client VPN connectivity.
- The bandwidth between the premise and NCC is determined by the amount of servers that are being protected.
- Each new NCC customer will automatically be provisioned 5 Mbps of bandwidth.
- For each VM provisioned in the sCloud, an additional 1.66 Mbps is allocated in order to scale up the replication and user connectivity to NCC.
Continuity Cloud Platinum (< 60 Minutes RTO)
This service offers less than 60 minute RTO and provides for WAN optimized replication from premise to the NCC for disaster recovery (DR). The target configured for push-button failover in the event of a failure of the local production workload. This provides automated restoration of services after a DR event is initiated if the datacenter or even a catastrophic hardware failure of the premise virtual host cluster. Implementation is typically about a week how many servers are protected.
Un-Managed Service- As this is offered as an un-managed service, the following items fall under the customers responsibility:
- Setup IPSEC-VPN into NCC
- Provide NCC PS with IP Address for Channel
- Provides a VM for the Engine Management Service
- Setup a Domain Controller with DNS installed on the NCC sCloud
- Clone Production Workload After Engine Deployment
- Ship VM Clones Into NCC
- Provide NCC with Target Resource Hydration Requirements
- Maintain Access to Internal EMS for NCC Staff.
- Monitor Engine Clusters
- Setup Notification of Critical Events
- Break/Fix of Replication
- Initiate Failover
- Will validate Secondary is functioning properly after the DR event
- Hydrate Compute Resources
- Initiate DR switchback
- Dehydrate Compute Resources
- Neverfail will provide Continuity Engine standard product support
- Neverfail will provide standard support for sCloud including connectivity and compute and storage
- Provides Full PS for Building sCloud,
- Provides IPSEC-VPN into the NCC
- Engine Installation and Acceptance Testing
- Domain controller provisioned in the same domain as the protected applications in the target NCC sCloud. Minimum 4G of RAM, 1 CPU, 20G HDD
- VPN Router capable to connecting a point to point IPSEC-VPN into the NCC
- Available bandwidth on the both the customer and NCC side at least equal to or greater than what is required for Engine replication estimated at 5Mbps minimum + 1.66Mbps per protected VM.
- Windows 2012 R2 or Higher with 4G of RAM and 20G HDD for Engine Management Service (EMS) on Premise
- Windows 2012 R2 or Higher with 4G of RAM and 20G HDD for Engine Management Service (EMS) on NCC
- During deployment provide NCC PS team with exports in OVA format of deployed Primary Server
- Protected VMs must have at least 2G or higher of available RAM and 2G HDD.
- Passive nodes will be dehybrated to 4G of RAM and 2 CPUs minimum
- Terminal server in the customers sCloud for full site DR accessibility
- VPN remote access to customer sCloud for full site DR accessibility (allows remote Windows and MAC desktops access to the sCloud)
- Workspaces desktops for remote users for full site DR
- NCC sCloud capable of hosting and providing compute resources for target replicated VMs
- Storage for host protected VM's
- During the PS engagement, NCC operations provisions the customer sCloud that will used to host the Contnuity Engine passive nodes.
- NCC also build network communications between the sCloud and the on premise network.
- NCC staff will provide customers with configuration details to establish the VPN connectivity between sites.
After the sCloud is built and network connectivity is established, an Active Directory domain controller installed with DNS must be provisioned in the sCloud in the same domain as the protected applications are members. NCC PS will a planning meeting between the customer and the NCC PS team which will outline the requirements for the premise installation and at this time the implementation will be scheduled. When the premise implementation is completed, the cloned OVAs will be shipped via an external drive into the NCC to be imported into the customer sCloud, put on the appropriate network, resources dehydrated and VM powered on.
After this a full system check (FSC) will ensure the datasets on the premise are mirrored on the target passive VM. After completed, the NCC PS team will schedule testing of the failover process via an acceptance and verification test. The installations will be turned over to the customer (un-managed) or to NCC operations (managed) for ongoing operations.