Absolutely! In fact, we strongly encourage users to back up to multiple destinations and we don't limit the number of destinations your users can back up to.
No. CrashPlan Central is for personal data only. Contact sales@crashplanpro.com for information on our hosted business offerings.
Yes. You can control the file selection at the individual client level or the organization level. Use regular expressions or variables to include or exclude files. You can even lock settings so your users can't change them.
Yes. On Windows, CrashPlan PRO uses Microsoft's Volume Shadow Copy Service to back up open files. However if you are backing up larger database file(s) you will want to read the following FAQ on the topic.
No. CrashPlan PRO is focused on backing up files.
We recommend you use a cloning tool to backup your server from a boot disk so you are guaranteed a clean clone of your drive. Then use CrashPlan to keep the daily and hourly backups. If your hard drive dies, just restore from the clone and use CrashPlan to restore to the latest and greatest data files you truly care about.
Yes. CrashPlan PRO is designed to resume backup upon waking up / reconnecting after a computer goes to sleep or loses network connectivity.
Yes. We recommend that you dump your database regularly and back up the location where the dump files are stored. Read more here.
A computer is assigned a single mount point. A computer's data cannot be split between mount points. A user might have different computers on different mount points, but the user is not considered when a mount point is assigned.
You have multiple options. Full information is available in the PRO Server How To on configuring for faster backup.
All backups to the mount that is out of space will simply stop. CrashPlan will NOT start deleting backed up data in order to make room.
Yes, if the new PRO Server has a copy of the old PRO Server's database.
Otherwise, the answer is “No”. Each PRO Server and its clients are a standalone environment. While you can copy/move backup archives between your server and your own clients in order to seed backups, you cannot send a copy of the backup archive to an entirely separate PRO Server. The necessary encryption keys will not be present in the new server.