VEEAM 321 RULE UPDATE
VEEAM 321 RULE ARCHIVE
VEEAM 321 RULE FULL
VEEAM 321 RULE PORTABLE

Per machine protected (When rental licenses from the same service provider are used, the off-site backup copy will not consume a license).

fixed price for the entire storage quota)

Per machine protected (a Veeam license is consumed).

Options generally seen in the market are: Service Providers can charge for the Veeam-powered service in different manners. Please check our Veeam Rental Licensing and Usage Reporting Reference Guide for more details.

Purpose-built products and partner portals to facilitate monthly usage reporting.

VEEAM 321 RULE UPDATE

Automatic license update capabilities to maintain license distribution.

VEEAM 321 RULE PORTABLE

Portable licenses for any customer, any workload, across any cloud.Pay-as-you-grow pricing plans that offer consumption-based licensing.The service is built with the help of the following Veeam solutions: Protect backups from deletion via Insider Protection or Immutability. Backups are encrypted at source, in-transit and at-rest. Fully integrated into the existing Veeam solutions to guarantee a consistent user experience and ease of use.

VEEAM 321 RULE FULL

Full support for PowerShell and RESTful API. Meet compliance requirements for archival and retention. Securily share backup resources among your customers.

Every customer connects directly over the internet using the same single TCP/UDP port protected by SSL/TLS encryption. Managed When offered as managed it can turn into a MSP Backup service.The service provider only provides secure, remote backup storage to the clients. Unmanaged The customer’s entire on-premises backup environment is not managed by the service provider.The solution is a service offering from the Service Provider and can be offered in both scenarios:

VEEAM 321 RULE ARCHIVE

With AWS S3 or Azure Blob object storage, these GFS backups can be tiered further on into the Archive Tier for cost-optimization.

Please check the Veeam Ready database to verify which S3-compatible object storages support immutability.

With AWS S3 or S3-compatible object storage, immutability can be used to provide ransomware protection.

The client can then simply create a mirror of current backups and/or off-load long-term backups to the secure object storage target. With AWS S3 or Azure Blob object storage, these GFS backups can be tiered further on into the Archive Tier for long-term retention and cost-optimization.īy leveraging Object Storage either from in-house (S3-compatible) or a public cloud vendor (such as AWS, Azure, Google, others), the service provider can provide off-site backup storage for the client.

Second, the Backup Storage can be tiered to an Object Storage to provide an additional (immutable) copy of all backups or only to off-load GFS backups.

First, the Backup Storage can be located on a Hardened Linux Repository providing immutability and ransomware protection.

At the back-end the Backup Storage can be further on protected: The client can then simply point backup (or backup copy) jobs to it as a secure backup target destination. (option 1 in the diagram below)īy leveraging Veeam Cloud Connect, the service provider can assign a storage quota on their backup repository for the client.

The storage exposed by the service provider can be one of the following options:Ĭloud repository. The service fundamentally exposes a storage space where customers can safely store their data. A Service Provider can build a Veeam-powered service to provide Off-Site Backup to their customers allowing them to support the 3-2-1 rule, without the need to invest on expensive infrastructure themselves, rather renting it as a service from a Service Provider. The general best practice and recommendation for data protection is to follow the 3-2-1 rule: three copies of your data, on two different media, one being off-site.įor most companies the biggest challenge is achieving the off-site copy. This site uses Just the Docs, a documentation theme for Jekyll. Application-Consistent Backup and Restore.Convert single-server to distributed deployment.

Veeam 321 rule