Server Recovery: For a single instance of a server designated for protection by ScerIS DRaaS, recovery is completed when:
the operating system as specified in the setup of the DRaaS for the server, including specified.
network address(es), storage device(s), and file system(s) is accessible by the designated.
customer representative located in the designated remote location.
the state of the protected server’s storage device represents the dataset version as defined by.
the recovery point objective (RPO)
server is recovered on the specified compute resource (virtual or physical).
the server is accessible through the specified public IP address(es).
Server: A server is software that includes an operating system and the operating system configuration settings necessary to enable the operating system to attain an operational state that is capable of supporting application software workloads and is accessible remotely through designated network address(es).
Booted Server: A server that has attained an operational state and is accessible remotely from designated network address(es).
Physical computer resource: A computer that includes all hardware elements( processors, memory, communications, storage, power, mechanical enclosure) to support deployment of operating systems and hypervisors.
Virtual computer resource: A virtual computer that includes virtual processor, virtual memory, virtual network and virtual storage to support deployment of operating systems.
ScerIS ON Cloud Services: Services that are operational within and between ScerIS Cloud platforms.
ScerIS OFF Cloud Services: Services that are operational between ScerIS Cloud platform(s) and any other infrastructure platform.
ScerIS network(s): Communications network within the ScerIS Cloud platform for communications within the ScerIS Cloud platform.
ScerIS external network interfaces/ports: For connecting the ScerIS Cloud platform to external networks such as public internet or private networks.
ScerIS Recovery Time Objective (RTO): The time span in hours that starts with the email/phone confirmation timestamp from ScerIS operations to the customer that an event that requires recovery has occurred and ends with the completion of the Server Recovery. The RTO for ScerIS DRaaS is four (4) hours.
ScerIS Recovery Point Objective (RPO): The specified maximum age, in minutes, hours or days, of the recovery point dataset to be used in the Server Recovery. The age of the recovery point dataset is determined by the time between the successful completions of two (2) sequential recovery points.
ScerIS Recovery Point: This is storage volume(s) that are a replication of the storage volume(s) specified for a DRaaS protected server with a data state representing the state of the protected server’s storage volume at the time of replication.
Server Recovery Authorization: Communication via POV ticket or phone by the designated customer representative(s) to ScerIS operations that server recovery for the specified server(s) is authorized.
Server downtime: The time span that starts with the event that interrupts the protected server operation and includes the elapsed time to:
identify the server is off line plus.
authorize a server recovery at ScerIS plus.
perform server recovery at ScerIS plus.
perform application recovery.
Application recovery: All activities required to recover any workloads and/or applications including customer configurations, settings, and access protocols that utilize protected servers.
Private Networks: These are network connections between ScerIS External Network Interfaces and any other compute infrastructure whose network capacity, security, performance, features, supplier and maintenance are designated and purchased by the customer. These networks are not part of the ScerIS Cloud platform.
ScerIS DRaaS Verification Test (DRVT): DRaaS customer requests a DRVT and ScerIS operations performs the DRVT as soon as commercial possible but in no case sooner than 3 calendar days or later than 10 calendar days after receipt of the request. ScerIS operations performs the DR recovery by creating server(s) at the disaster recovery site using the most recent recovery point dataset and notifying the customer when the server(s) are online and accessible for testing by the customer through a ScerIS defined IP address. The server(s) remain accessible for 5 calendar days after notification by ScerIS. There are no charges for virtual server(s) CPU and Memory during the DRVT time period. The DVRT provides a method for customers to verify the effectiveness of their disaster recovery plan without affecting production operations at the primary site.