For most users, the default client configuration is sufficient. Some users may wish to modify settings to accommodate specific needs; see the Code42 CrashPlan backup settings documentation for advanced options. Some settings, like encryption, are mandatory.
Should you wish to expand the scope of inclusion so more files are backed up, know that initial backups will take longer, your computer will do more work, and you’ll probably end up using the original installers for applications and operating system if you need to do a full system restore.
Certain file types are always excluded from the University IT Code42 CrashPlan backup, such as caches, files from your Stanford AFS directory, and other miscellaneous system data. You may add to the list of filenames or types of files to be excluded. See the Code42 CrashPlan file exclusions documentation.
Files and directories that have been marked for exclusion administratively by your IT support staff cannot be overridden by end users.
Data in a folder that has _NoBackup in the name (e.g., PersonalFiles_NoBackup) will always be excluded from backup. You may create this folder anywhere on your computer and Code42 CrashPlan will always ignore the contents.
Always perform a test restore to evaluate whether your settings should be adjusted to protect data.
You may choose to add a second destination for your personal backup data. Code42 CrashPlan can be configured to use an attached portable hard drive or another device running Code42 CrashPlan.