Whether you are installing a primary backup solution or complementing an existing one with an additional target or repository, Scarlett's Backup as a Service (BaaS) solutions powered by Veeam and Green Cloud provides a remote, secure, cloud-based storage destination for existing server infrastructures.

Seamless - Use your cloud repository like a local backup repository utilizing any backup strategy you deploy. Simply open the Veeam backup console and make your cloud repository a target for any backup copy job. If you are currently using Veeam, no additional licensing is required.

Efficient - With available WAN Acceleration, it leverages forever-incremental backups, in cloud synthetic full backups, and more to minimize data transfer while maximizing restore points. Get your backups off site quickly and easily without adding bandwidth.

Secure - Rest easy by encrypting your backup at source, in flight and at rest, without negatively impacting data transfer to the cloud (thanks to content-aware compression and WAN Acceleration). Cloud Connect ensures that your data is as safe and confidential as it would be in your own dedicated offsite repository.

Recovery -  With Cloud Connect, your data is always available. With available bandwidth, you can choose to recover your data “over the wire” or you can opt to have physical encrypted media shipped directly to you.

 

 

Frequently Asked Questions

Backup as a Service (BaaS) provides a remote, secure, cloud-based storage destination for existing server infrastructures utilizing Veeam Backup & Replication (version 8). Green Cloud's infrastructure is leveraged as an additional or replacement backup repository. This service better enables Customers to fulfill the “3-2-1” rule: maintain three (3) copies of data, store on two (2) different types of media, and keep at least one (1) copy offline, e.g. in the Cloud.

 

Snapshots are not the same as backups and shouldn't be used in the same way for Disaster Recovery planning. 
 
Here's why:
 
A snapshot is a point-in-time 'picture' of the state of a virtual machine’s disk(s) at the instant the snapshot is taken. Snapshots are also usually saved on the same media as the VM, to save I/O when a recovery is needed. Snapshots are not overwritten in the "grandfather-father-son" schema; they live 'side-by-side' until deleted. It is also not optional to retrieve individual files from a snapshot (the entire disk must be mounted and made available; see the 3 data recovery options for snapshots below).
 
Snapshots are ideal for recovery to the last known good - and recent - VM configuration in case of VM failure.
 
A backup is a full copy of the virtual machine's data and applications, taken while the VM is in a prepared state and is usually saved to separate media (i.e. to a different SAN or a redundant data center). Backup jobs are typically configured to consolidate the files periodically based on the "grandfather-father-son" schema (or similar). For example, daily backups might be consolidated every 8th day to be replaced by a weekly version. The weekly backups might be consolidated after five weeks, as this is when monthly version created; and the monthly copies are replaced by an annual backup, and so on.