Who is this article for?
CrashPlan for Enterprise, no.
Code42 for Enterprise, yes.
CrashPlan for Small Business, yes.
This article applies to on-premises authority server version 3.
A destination is a logical grouping of enterprise servers and storage servers within a single LAN or a single data center. Devices back up to destinations. For best data protection we always recommend backing up your devices to at least two destinations.
There are four layers to the Code42 environment storage hierarchy: destinations, enterprise servers, store points, and backup archives. Users only see destinations.
- Destination: The top level of the storage hierarchy; storage within a single LAN or data center that is grouped together logically. A destination must have at least one server and at least one store point in order to successfully receive backup data. By default, the data balancer automatically balances storage within a destination.
- Enterprise Server: A machine running Code42 environment software. An enterprise server can have multiple store points (e.g., the CrashPlan PROe managed appliance ships with two store points).
- Store point: Single directory where backup data for one or many devices is stored. A store point must be associated with one and only one server. There is no limit to how large a store point can be.
- Backup Archive: A directory where the backup data for a single device is stored. The directory is named after the source device's GUID. Within a single destination, the automatic data balancer may move a backup archive from one store point to another.
At any given time, a device is assigned to and backs up to one and only one store point within a destination. Details about the server or store point that a device backs up to is abstracted and never displayed to the user. Rather, the user is able to see information only about the destination.
Multi-server support and automatic data balancing enable the Code42 environment to easily scale with your company's or organization's growing backup needs.
If storage at one of your destinations fills, simply add a storage server to the destination. Adding a storage server to a destination is completely invisible to the user.
The enterprise server can automatically balance consumed space within a single destination so all its store points have approximately the same amount of free space, within a range of tolerance that you can define. It does this by safely moving backup archives between store points within the destination. Devices can continue to back up and restore while an associated backup archive is being balanced, a process that is completely invisible to users.
Data balancing is enabled by default for all new destinations and all new storage servers. However, the administrator must explicitly turn on data balancing for each store point. Balancing takes place only after balancing is enabled on two or more store points within the destination.
For all environments, we strongly recommend using the default data balancing settings. The default settings are based on years of experience with managing online storage and are fine-tuned to optimize storage across deployments of all sizes.
The Destination Overview displays a list of all destinations configured within your environment.
|a||Action menu||Contains commands available in the Destinations list view.|
|b||Add destination||Displays sheet in which you enter information required to add a destination.|
|c||–||Click to select all the destinations in the list.|
|d||Name||Destination name. Click a destination's Name to display the destination's details.|
|e||Servers||Number of enterprise servers under this destination. Click the number of servers to view a list of all servers under this destination.|
|f||Store points||Number of store points under this destination. Click the number of store points to view a list of all store points under this destination.|
|g||Sessions||Number of devices currently connected to this destination. Click a destination's Sessions value to display the destination's details.|
|h||Devices||Count of the number of devices backing up to this destination. Click a destination's Devices value to display the destination's details.|
|i||Stored||Total amount of disk space used for backed up files for all storage servers in this destination. Click a destination's Stored value to display a list of backup archives residing within the chosen destination.|
|j||Free||Amount of free space for all storage servers in this destination. Click a destination's Free value to display the destination's details.|
|k||Inbound Backup status||(Enabled or Disabled) Indicates whether devices are allowed to back up to this destination. If enabled, devices are allowed to back up to this destination. If disabled, devices are not allowed to back up to this destination. Click a destination's Inbound Backup status to display the destination's details.|
|l||Balancing status||(Enabled or Disabled) Indicates whether data balancing is enabled for this destination. Click a destination's Balancing status to display the destination's details.|
|m||Online status||(Online or Offline) Indicates whether the destination is online. Click a destination's Online status to display the destination's details.|
|Export All||Export all destinations in the list to a CSV file|
|Print the list of destinations|
Export all visible list items to a CSV file by selecting > Export All. If no destination is selected, all destinations in the list are exported.
The identification number of the destination.
|destinationName||Name of the destination.|
|guid||Globally Unique IDentifier for this destination.|
Servers are either CLUSTER or PROVIDER.
CLUSTER: A local server for which you have access.
Indicates whether devices are allowed (enabled) or are not allowed (disabled) to send new data to existing archives on this destination, server, or store point.
Indicates whether data balancing is enabled or disabled for this destination, server, or store point.
|Number of store points with data balancing enabled.|
|Indicates whether the server is online.|
|Identification number for the cluster server.|
|Number of enterprise servers under this destination.|
Number of enterprise servers under this destination that are offline.
|Number of store points under this destination.|
|Number of organizations under this destination.|
|Number of users under this destination.|
|Number of devices under this destination.|
|Number of devices currently connected to this destination.|
|Total storage capacity of the storage servers in this destination.|
|usedBytes||Amount of space used for all the storage servers in this destination.|
|usedPercentage||Percentage of used disk space for all the storage servers in this destination.|
|freeBytes||Amount of free space for all storage servers in this destination.|
|freePercentage||Percent of free space for all storage servers in this destination.|
Amount of space consumed by archives in cold storage.
Percentage of used space consumed by archives in cold storage.
Percentage of total space consumed by archives in cold storage.
|Number of devices currently backing up and syncing to this destination.|
|Bandwidth the server is currently using for inbound backups.|
|Amount of bandwidth currently being used for restores.|
|Total size of files selected for back up and sync.|
Total number of bytes selected for back up.
Total size of files waiting to be backed up.
Add a new destination
Use the Add a New Destination command to create a new destination.
|a||Destination Name||Unique name of new destination|
|b||Provider||Enable when you are using someone else's storage as a destination (e.g. when you've purchased storage at PROe Cloud for use as a secondary destination)|
Destination Details displays stats and settings for the selected destination.
|a||Destination GUID||Globally unique identifier for this destination.|
|b||Action menu||Actions that you can apply to this destination.|
|c||Online||Stats related to currently connected devices.|
|d||Stored||Stats related to the amount of data stored for this destination.|
|e||Storage Utilization||Comparison of storage consumed per user. Chart regions are clickable.|
|f||Backing Up||Stats related to devices currently backing up. Displayed averages are per enterprise server and per storage server.|
|g||Offline Servers||Number of servers within the destination that are currently offline.|
|h||Balancing||Displays balancing operations currently in progress.|
|i||Free||Free space remaining within the selected destination.|
|j||Cold||Amount of space consumed by archives in cold storage.|
|k||Inbound backup status||Indicates whether devices are allowed to back up to this destination.|
|l||Balancing status||Indicates whether data balancing is enabled for this destination.|
|m||Enable Balancer||Indicates whether data balancing is enabled for this destination.|
|n||Allowed Disk Variance||The amount of variation allowed in disk utilization per storage server within the destination.|
|o||Priority Of Local Copy||Process priority allocated to balancing actions between storage servers under a single server.|
|p||Priority Of Remote Copy||Process priority allocated to balancing actions between storage servers across servers.|
|Edit||Edit the selected destination's name and data balancing settings.|
Add a storage server to this destination.
|Remove||Remove this destination. Enabled only if this destination is not in use and has no assigned servers or storage servers.|
|Print details for this destination.|
|a||Name||Name for the selected destination.|
|b||Enable balancer||Toggle to enable or disable data balancing for this destination. Recommended setting is enabled.|
|c||Allowed disk variance||The amount of variation allowed in disk utilization per storage server within the destination. Default of 20% is the recommended value.|
|d||Priority of local copy||Process priority for copy actions performed during balancing between store points on the same server. Decrease priority to consume fewer system resources, generally disk I/O.|
|e||Priority of remote copy||Process priority for copy actions performed during balancing between storage servers on different enterprise servers. Even though enterprise servers within a destination should be on the same LAN, bandwidth between enterprise servers is generally the limiting factor in copy speed for remote copies, so we recommend keeping the priority of remote copy at 100% in most cases.|
From the Destinations Overview, click a destination's Stored value to display a list of backup archives residing within the chosen Destination.
|a||Action menu||Display action menu.|
|b||Select All||Select all backup archives on this page.|
|c||Selected||Total size (on the device's file system) of files selected for backup.|
|d||Selected Files||Total number of files selected for backup for this device.|
|e||Todo||Number of files waiting to be backed up.|
|f||Stored||Size the backup archive consumes on its storage server.|
|g||Last Backup||Date and time when the device was last 100% backed up. If the device has never been 100% backed up, then this value displays the date and time when the device last backed up data.|
|h||Last Maintained||The most recent date on which archive maintenance was performed on the backup archive.|
|i||Cold||A green dot indicates that the archive is in cold storage.|
When backup archives are selected from the Archives list, the following commands are available from the action menu.
|Migrate Archive...||Moves selected backup archives to a different store point. Data balancing must be on for target destination. To migrate all archives from one store point to another, turn off balancing on the store point you want to empty.|
Reassigns selected backup archives to a different store point. Backups start from the beginning on the new store point. Use Reassign Archive when a store point has completely failed and there is no way to get the archives off the store point.
|Maintain Archive...||Places the selected backup archive(s) into the system archive maintenance queue.|
|Reset Archive...||Deletes the contents of the selected backup archive(s).|
|Print...||Print the list of selected backup archives. Prints the list of all backup archives if no backup archives are selected.|
|Export All||Export the list of selected backup archives to a CSV file. Exports the list of all backup archives if no backup archives are selected.|
Export all visible list items to a CSV file by selecting > Export All. If no archive is selected, all archives in the list are exported.
|guid||Globally Unique IDentifier for the archive.|
|computerId||Identification number for the computer associated with the archive.|
|targetGuid||Globally Unique IDentifier for the destination associated with the archive.|
|destinationId||Identification number of the destination associated with the archive.|
|storePointId||Identification number of the store point associated with the archive.|
|lastCompletedBackup||Date and time when the device was last 100% backed up. If the device has never been 100% backed up, then this value displays the date and time when the device last backed up data.|
|archivesBytes||Total size of files selected for back up and sync.|
|selectedBytes||Total number of files selected for back up.|
|selectedFiles||Total number of files selected for back up and sync.|
|todoBytes||Total size of files remaining to back up and sync.|
|lastMaintained||Most recent date on which archive maintenance was performed on the archive.|
|Total amount of time needed to complete the archive maintenance job.|
|compactBytesRemoved||Total size of the files removed from the archive due to archive maintenance operations.|
|isColdStroage||Indicates if the archive is in cold storage.|
|service||Indicates if the archive is associated with the CrashPlan app or SharePlan app.|
|archiveGuid||Globally Unique IDentifier for the plan or backup associated with the archive.|
To view balancing activity:
- Navigate to Destinations > Overview
- Select your desired destination
- Click the value in the Balancing column
|a||Start Time||Time each data balancing job began|
|b||Archive||GUID of the archive moved by data balancing|
|c||From||Store point that the archive was moved from|
|d||To||Store point that the archive was moved to|
|e||Size||Size of the archive that was moved by data balancing|
|f||Run Time||Elapsed time of the data balancing job|