Tip:
Highlight text to annotate it
X
In CrashPlan PROe, this is the screen that a user sees when the backup is running. Each
backup to a different datacenter is shown as a separate destination in the application,
but CrashPlan doesn't display details of where and how data is stored.
This video will explain CrashPlan PROe architecture: Destinations, Servers, and Store Points, so
you can design a system that provides the redundancy, speed and security required by
your organization.
Let's go back to the CrashPlan PROe client. Each entry on this list is a Destination,
a logical grouping of servers and store points at the same location.
Each destination represents a completely separate backup of that computer. Clients back up to
each destination individually, so that any data corruption at one destination does not
affect the backups in others.
Within a destination, this computer's data is stored on a store point, a hard drive attached
to a CrashPlan PROe server. To add storage, you can attach an additional store point to
a server and CrashPlan PROe will automatically balance backup archives to it. You can also
add multiple servers to a destination to increase the total backup capacity of the destination;
all store points in the destination can balance across the LAN to create a private Cloud at
a destination.
Each destination contains only one copy of a backup per client, so to provide redundancy
in your backup, configure each client to back up to multiple destinations. Ideally, you'd
have at least one destination on-site for higher speed backups and restores, and another
one off-site, providing greater protection in case of catastrophe.
One last thing. The first server installed is the Master server. It's what your clients
connect to for authentication, and provides the admin console you use to administer your
backups. All other servers are known as storage servers and are also administered through
the admin console on the master server.
For more information on Destinations, please visit our support site.