CrashPlan PROe Architectures
Who is this article for?
Incydr, no.
CrashPlan for Enterprise, no.
Code42 for Enterprise, yes.
CrashPlan for Small Business, yes.
This article applies to on-premises authority server version 3.
Considerations
Which CrashPlan PROe architecture is best for your organization depends on several factors:
- Your level of IT infrastructure and maintenance
- Your organization's security policies and requirements
- Service Level Agreements
- Legal or regulatory requirements
Contact sales to discuss which architecture best fits the needs of your organization.
Architectures defined
CrashPlan PROe offers three main architecture options: public cloud, private cloud (including Managed Private Cloud deployments), and hybrid cloud deployments.
Public cloud
In the public cloud architecture, your data is stored at one of several secured Code42 data centers. Your data remains protected by CrashPlan PROe's multi-layered security protocols.
Your encryption keys can be stored either in the secure Code42 data center or in a master server in your organization's control (called public cloud with keys on premises).
- Organizations wanting to empower end users
- Organizations that don't want to manage their own data center(s)
- Global organizations lacking data centers in certain regions
- Organizations whose corporate IT strategy mandates it
- Minimal set up required—start backing up almost immediately
- Unlimited—really unlimited—storage of data / file types / metadata
- Sign in, authenticate, and restore from anywhere
- Requires zero infrastructure
- Offsite data storage provides an instant disaster recovery strategy
- Acts as an operating expense instead of capital expenditure
- Take your data to a private cloud at any time
Private cloud
In the private cloud architecture, your data and encryption keys are stored at your organization's own data center. Private cloud deployments offer the same industry-leading support from Code42 as public cloud deployments.
You can configure your own server with the CrashPlan PROe software, or you can use a Code42 managed appliance within your datacenter (called "Managed Private Cloud").
- Larger organizations with existing, internal data center infrastructure
- Organizations requiring total control over their data
- Organizations whose corporate IT strategy mandates it
- All data, encryption keys, and backup and restore transmissions are kept within your secure network
- Full control of network and quality-of-service configurations, since communication stays within your secure network
- All information about your deployment is private, even from Code42
Managed Private Cloud
A Managed Private Cloud is a type of private cloud deployment in which Code42 continuously monitors the performance, reliability, and status of your backups. A Managed Private Cloud requires use of a managed appliance. Contact the Code42 sales team for details on using a Managed Private Cloud in your organization.
- Larger organizations with existing, internal data center infrastructure
- Organizations requiring total control over their data
- Organizations whose corporate IT strategy mandates it
- All data, encryption keys, and backup and restore transmissions are kept within your secure network
- Full control of network and quality-of-service configurations, since communication stays within your secure network
- 24/7 monitoring and support by Code42
Hybrid cloud
In the hybrid cloud architecture, your data is stored at two locations: your organization's own data center and one of several secure Code42 data centers.
Your encryption keys are stored in a master server in your organization's control.
- Organizations whose disaster recovery strategy requires both onsite and offsite data backup
- Organizations that want to use public cloud, yet control the encryption keys
- Global organizations lacking data centers in certain regions
- Organizations needing more flexibility around enterprise directory services integration
- Organizations whose corporate IT strategy mandates it
- Flexibility of public cloud storage alongside the full control of private cloud configuration
- Assured data continuity via multi-destination backup strategy
- Offsite data storage provides an instant disaster recovery strategy
- Easy separation of different classes of data
Examples
Case study 1
- Growing Startup
- Approximate number of users: 150
- Small office with some remote workers
- Very little IT infrastructure or IT staff
Recommendation: Public Cloud. This is by far the easiest way to get workers backing up immediately and with very few IT staff. The Public Cloud allows all workers to back up and restore from anywhere.
Case study 2
- Advertising agency
- Approximate number of users: 550
- Offices in Los Angeles, Chicago and New York City
- Serves high-profile clients
Recommendation: Managed Private Cloud. It is critical to the business that its sensitive intellectual property is tightly controlled and protected, especially from theft or breach, and the Managed Private Cloud ensures that data is stored securely on the internal network. Additionally, the management services included with the business's managed appliance support the reliability and availability of backup operations in each location. The IT department in New York is able to manage the agency's internal backups for all three offices.
Case study 3
- Fast-moving global company
- Approximate number of users: 23,000
- Data centers in US, Europe
- No data center in the high-growth Asia Pacific region
Recommendation: Hybrid Cloud. While most users can back up to data centers on the same continent, users in the growing Asia Pacific region cannot. Backups and especially restores from across the ocean would be painfully slow. The Hybrid Cloud deployment allows US and European users access to an internal data center, while Asia Pacific users can quickly and efficiently back up to Code42's regional data center.
Next steps
- Review all Planning resources
- Read our enterprise overview of Cloud Deployment Strategies
- See the CrashPlan PROe FAQs
- See the setup guide for your chosen architecture: