PeaSoup Hosting

Zerto Disaster Recovery as a Service (DRaaS)

PeaSoup's Disaster Recovery (powered by Zerto) provides a real-time protection of workloads into the cloud. None-disruptive Disaster Recovery testing can occur at any time, the service benefits from cloud automation with full audit capabilities. DRaaS provides a solid DR assurance without costly second sites and rollback to recover in minutes.


  • Fast disaster recovery time (RTO)
  • Flexible disaster recovery point (RPO)
  • DRaaS protects critical services
  • Eliminate need for secondary DR datacentres
  • Test the DR process anytime with audited results
  • Proven market leading technology
  • Continuous data protection (CDP)
  • DRaaS significantly reduces overall DR costs
  • Full remote access when DRaaS failover is invoked
  • Encrypted Connection across Internet, PSN, N3 and others


  • Improves business contiunity with access to critical systems in minutes
  • Have access to near live data during a disaster
  • Reduce cost by protecting critical systems only
  • Reduce operational cost by replicating to Peasoup UK based cloud
  • Test DR without impacting business operations
  • Built on market leading Zerto and VMware technology
  • Applications and data avaialble at the press of a button
  • Cost effective opex based service. Use only what you need
  • Accesable from anywhere, reduce DR office cost
  • Can seamlessly integrate with existing business continuity plans


£25 a server a month

  • Education pricing available

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at Tell them what format you need. It will help if you say what assistive technology you use.


G-Cloud 12

Service ID

9 0 3 3 1 5 3 5 8 0 4 7 3 8 2


PeaSoup Hosting Kyle Nicholas
Telephone: 01932 450 400

Service scope

Service constraints
The service is limited to a virtualised platform working with either VMware ESX or Microsoft Hyper-V hypervisor.
System requirements
  • Windows 2012R2 or later, Standard server for Zerto Virtual Manager(ZVM)
  • ZVM requires 4GBvRAM, 1vCPU and 40/60GB diskspace (OS dependant)
  • Virtual Replication Adapter(VRA) installed on each ESXi/Hyper-V Host
  • VCenter/SCVMM must be available
  • Site-to-site VPN to your PeaSoup vCloud Organisation firewall OR
  • MPLS into PeaSoup network

User support

Email or online ticketing support
Email or online ticketing
Support response times
Within PeaSoup, any infrastructure issues have the highest priority, 30-minute response. and are constantly monitored 24/7. Customer calls are raised as either Priority1 – (see below) should already be in progress. Customer updates are provided every hour. Or raised as Priority 4 - Operational questions, advice or a change in service. This carries an 8 hour response time and a 95% SLA to resolution within 40 hours. Responses at weekends are answered within 2 hours of the request.
User can manage status and priority of support tickets
Online ticketing support accessibility
None or don’t know
Phone support
Phone support availability
24 hours, 7 days a week
Web chat support
Web chat
Web chat support availability
9 to 5 (UK time), Monday to Friday
Web chat support accessibility standard
None or don’t know
How the web chat support is accessible
Webchat is accessible from any page on the main website at the bottom right hand corner . By contacting us over the webchat, a customer service representative will pick up and arrange for technical support.
Web chat accessibility testing
The webchat is browser based and is compatible with any assistive technology that works within that browser or within the operating system.
Onsite support
Support levels
PeaSoups infrastructure has the highest priority, 30-minute response which is constantly monitored 24/7. This is unseen by our customers. The infrastructure is designed to cope with failure and an internal SLA provides 95% of all calls fixed within a 4hr window. If there is an operational issue preventing the delivery of the service, and customers are affected, updates are provided every hour. Customer raised calls generally are priority 4 calls relating to operational questions, advice or a change in service. This carries an 8 hour response time and a 95% SLA to resolution within 40 hours. Much of this level is mitigated through our support desk with a plethora of videos and documents on general usage of the systems provided. Support is operated by the engineering team, however each client has their own account manager who monitors the support ticket and provides the communication. The support describes is included within the pricing of the service contract covering the infrastructure of the service. PeaSoup do not directly provide support and maintenance of the customers operating systems or applications.
Support available to third parties

Onboarding and offboarding

Getting started
During the initial setup, PeaSoup will schedule a call with the client technicians to install all of the required components. Once this work has been undertaken, we provide an onboarding Webex in which we go through all of the features of the service, how to configure and maintain the health of the replication. We will also perform a non-disruptive test failover to ensure that the environment has been correctly setup and functioning as expected.
Service documentation
Documentation formats
  • HTML
  • ODF
  • PDF
End-of-contract data extraction
At the end of the service, we can securely remove all data that has been replicated into the DR environment. In the event that the service is in the failover state and currently running out of the PeaSoup Cloud, a failback procedure can be undertaken to bring all data back on premise.
End-of-contract process
At the end of the contract, the customer may decide to refresh/change/terminate the service.

If the client wishes to renew or change the contract then no additional charges will be made, as the service has already been setup, unless additional space is required.

Using the service

Web browser interface
Using the web interface
In the event of services becoming completely unavailable, users can access a web portal to initiate the failover process into the cloud infrastructure. From the web portal, clients can also access all the features as with the on-premise console such as failover tests, auditing and reporting and review VM's are meeting SLA's.
Web interface accessibility standard
None or don’t know
How the web interface is accessible
Upon signing up to the service, clients are provided with a document on how to connect to the environment, this includes the web page, username and passwords.
Web interface accessibility testing
Command line interface


Scaling available
Scaling type
Independence of resources
All services are dedicated and reserved by each client. This ensures there are no impacts during peak periods or crossover from other users.
Usage notifications
Usage reporting
  • Email
  • Other


Infrastructure or application metrics
Metrics types
  • Number of active instances
  • Other
Other metrics
  • SLA's are met
  • Recovery Point/Time Objectives
Reporting types
  • Real-time dashboards
  • Regular reports
  • Reports on request


Supplier type
Not a reseller

Staff security

Staff security clearance
Conforms to BS7858:2012
Government security clearance

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
United Kingdom
User control over data storage and processing locations
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency
At least once a year
Penetration testing approach
Protecting data at rest
  • Physical access control, complying with CSA CCM v3.0
  • Physical access control, complying with another standard
  • Encryption of all physical media
Data sanitisation process
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
  • Hardware containing data is completely destroyed
Equipment disposal approach
Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Backup and recovery

Backup and recovery
What’s backed up
  • Virtual Machines
  • Files
Backup controls
Streamlined management process from the GUI allows configuration of replication and backups. Users assign VMs to virtual protection groups. The virtual protection groups are then continuously replicated on a transaction by transaction basis into the cloud
Datacentre setup
  • Multiple datacentres with disaster recovery
  • Single datacentre
Scheduling backups
Users schedule backups through a web interface
Backup recovery
Users can recover backups themselves, for example through a web interface

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway

Availability and resilience

Guaranteed availability
Uptime rate of 99.99% non-caveated by planned or unplanned maintenance. A discount of 5% of the monthly Fees payable for each whole 30 minute period of Downtime. Such discounts shall be applied to the Fee payment due immediately following the Downtime. Discounts shall be made up to a maximum of 100% of the Fees payable for a given month.
Approach to resilience
Operating within Tier 3, datacentres with multiple power supplies, generators and cooling units for resilience. Our cloud configuration is maintained under strict change control and protected by internal processes and procedures. Our network connectivity is provided separately from two Points of Presence in two diverse Tier3 datacentres, away from the server environment, where our core internet routers reside, these connect us to our four main internet providers in a BGP configuration. Networking connectivity is one of the most common causes of datacentre outages and we have the ability to survive multiple failure scenarios in our design. We have NO physical SAN architecture, dramatically reducing our risk of failure associated with traditional architectures. The PeaSoup Cloud is a software defined datacentre. Networking, firewalls, compute power and storage are all controlled at the software layer within clusters of physical servers for resilience. We scale out adding more servers as needed to meet demand and with each additional server we add not only more capacity but also more performance across the whole cluster, especially the performance of the storage.
Outage reporting
In the event of an outage, email alerts are sent followed up by a phone call from your dedicated account manager to keep you informed of the progress in resolving any issues.

Identity and authentication

User authentication
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels
User accounts are set up with specific access using a role-based access system that ensures granularity of the available services within the environment. PeaSoup access is additionally restricted via the internal Information Security Policy which ensures only the authorised personnel within the support team have access to the management interface whereas account managers only have access to read-only reporting information.
Access restriction testing frequency
At least every 6 months
Management access authentication
  • Dedicated link (for example VPN)
  • Username or password
Devices users manage the service through
  • Dedicated device on a segregated network (providers own provision)
  • Any device but through a bastion host (a bastion host is a server that provides access to a private network from an external network such as the internet)

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users have access to real-time audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for

Standards and certifications

ISO/IEC 27001 certification
Who accredited the ISO/IEC 27001
ISO/IEC 27001 accreditation date
What the ISO/IEC 27001 doesn’t cover
Stage 2 - in process with BSI
ISO 28000:2007 certification
CSA STAR certification
CSA STAR accreditation date
CSA STAR certification level
Level 1: CSA STAR Self-Assessment
What the CSA STAR doesn’t cover
Ongoing in line with our certifications with BSI stage 2.
PCI certification
Other security certifications

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
ISO/IEC 27001
Information security policies and processes
Line with our Information Security Policy Peasoup are committed to the development and continual improvement of Information Security and its supporting information security management system, in order to provide; - Assurance with legal, regulatory and contractual obligations - Reputation management - Protection of critical assets.

Operational security

Configuration and change management standard
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach
PeaSoup operates a change control process in-line with our ISO27001 procedures. This covers all the components that use an operating system to control hardware and/or software activity, any building services supplied to PeaSoup (e.g.power, air conditioning) and any service provided to PeaSoup upon which the continuity of service to its customers is reliant. The request for change or emergency change procedure requires top-level authorisation with technical and business approvers. This also aligns with our Continual Improvement and Corrective action Policy. All components of the infrastructure are tracked inline with our Infrastructure Management Policy controlling the configuration tracking of all devices.
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
The PeaSoup Security Steering Group uphold the Risk Management Policy which is aligned to ISO27005:2018-Information Security Risk Management. This ensures risks are identified, evaluated and treated appropriately in an ongoing basis. PeaSoup hold a strong relation with all of our vendors and keep track industry information and also monitor software security mailing lists. Known critical patches are applied as soon as possible following the change control process, less critical patches are assessed through the risk register maintained by the Security Steering Group.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
In line with our Audit and Monitoring Policies - The PeaSoup Security Manager must be informed immediately of any unusual traffic flows or network device activity that arises from regular network monitoring or alerts. Quantitative or qualitative information on network activity may indicate either device failure or network attacks. The Security Manager need to be made aware of this activity to investigate the possibility of a network attack that requires remedial action or escalation.
Incident management type
Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402
Incident management approach
All incidents, are classified, handled, reviewed, resolved and documented using the Incident Management Process in order to aid in business continuity and business recovery activities. The purpose of this policy is to help identify and resolve incidents effectively, minimise the business impact and reduce the risk of similar incidents occurring. There are predefined procedures, for events triggered by suspicious activity in monitoring any evidence of unauthorised activity or critical IDS/IPS alerts. The policy also defines the processes used to report incidents for users. It the security managers responsibility to report and distribute a response and escalate as necessary.

Secure development

Approach to secure software development best practice
Supplier-defined process

Separation between users

Virtualisation technology used to keep applications and users sharing the same infrastructure apart
Who implements virtualisation
Virtualisation technologies used
How shared infrastructure is kept separate
The platform utilises vCloud technology and each organisation is completely separated at the network level by design. The data that is replicated into the clients provisioned virtual private datacentre remains seperate from other users. They have their own login credentials, own networking and own firewalls providing the control of who can access their virtual datacentre.

Energy efficiency

Energy-efficient datacentres
Description of energy efficient datacentres
The datacentre provider, Century link, is a member of the European Energy Efficiency Platform (E3P)


£25 a server a month
Discount for educational organisations
Free trial available

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at Tell them what format you need. It will help if you say what assistive technology you use.