Depending on the circumstances, you have several options for keeping users from accessing, backing up and restoring with CrashPlan.
All these actions can be reversed, but in cases where loss of data results, the loss of data is not reversible. Only the ability to reinstate the object is possible. Reinstating does not restore an archive that has been removed.
As this table illustrates, each option that prevents user access has different consequences. Choose the option that best fits your situation.
| Command | Prevents backup for | Archive | Destinations | Frees a license | Situation |
|---|---|---|---|---|---|
| Deauthorize | This user's computer | Retained | Retained | No | Computer has been misplaced, but not confirmed lost or stolen |
| Block User | This user and all of this user's computers | Removed according to archive retention policy | Deleted | Yes | User has left the company |
| Deactivate Computer | This computer for this user | Removed according to archive retention policy | Deleted | Yes | User has confirmed that computer is lost |
| Deactivate User | This user and all of this user's computers | Removed according to archive retention policy | Deleted | Yes | User has left the company |
| Deactivate Org | This org and all of this orgs's users and computers | Removed according to archive retention policy | Deleted | Yes | Mass removal of users, computers and backup data |
Use the follow table to reinstate users whose access you have prevented.
| To | To This |
|---|---|
| Reauthorize a computer | USER: User logs in to the computer for which he was deauthorized. |
| Activate a computer | ADMIN: In admin console, display computer info, then click Activate or… USER: User logs in on new computer. |
| Activate a user | ADMIN: In admin console, display user info, then click Activate or… USER: There is no way for users to reactivate themselves. |
| Unblock a user | ADMIN: In admin console, display user info, then click Unblock. USER: There is no way for a user to reverse a Block operation. |
Deauthorize computers to prevent unauthorized access to the CrashPlan desktop (including access to Restore), especially in configurations where the client's security settings do not require the account password for access to the CrashPlan Desktop. Deauthorize may also be used for troubleshooting to force the user to log into the CrashPlan desktop. Deauthorization of a computer results in the following:
Issue the deauthorize client command.
A computer must be reauthorized from the CrashPlan desktop. To do so, log into the CrashPlan desktop.
You can deactivate computers, users or orgs. Deactivation of any object is a potentially destructive operation. Always treat deactivation as a destructive operations and use with care.
Deactivate a computer when a computer is reassigned, decommissioned, lost or stolen. Deactivating a computer results in the following:
Other computers in the user's account are unaffected by deactivation of another computer. Deactivated computers are able to be reactivated. However, if any backup archives were removed during deactivation, the archive(s) are not recoverable by reactivation.
In order to reactivate a computer from the CrashPlan desktop, the user must be active.
Use the Deactivate User option to remove a user's access to CrashPlan globally (for example, when an employee has left the company). When you deactivate a user:
Deactivate an org to remove an org you are no longer using. When you deactivate an org, all active users and computers within the org are also deactivated. See Deactivate User and Deactivate Computer.
Blocking a user works exactly as deactivating a user and should be treated as a destructive operation. When you block a user: