jarrodatCode42

3 ms·

1.
by jarrodatCode42 10y ago
Wanted to pop in here and expound on the topic. CrashPlan has versioning that is set (by default) to back up changed files in 15 minute increments. If a file is corrupted, CrashPlan will attempt to back up the changes as it is not a corrupt
2.
by jarrodatCode42 10y ago
Just wanted to clarify this policy. CrashPlan requires a device to connect to it's backup at least once within a 6 month period. This is to ensure the integrity of the data we're storing. Part of CrashPlan’s ability to maintain th
3.
by jarrodatCode42 10y ago
Since the infrastructure for CrashPlan's backup engine is the same between our Business/Consumer clients, we recommend that all users routinely connect their devices to the backup destinations. That being said, this policy only af
4.
by jarrodatCode42 10y ago
Hello Everyone, Wanted to jump in here to confirm. This policy only affects devices that have not connected to CrashPlan Central in 6 months or longer. This does not affect volumes that have not connected to the device in that period of tim
5.
by jarrodatCode42 11y ago
Hello Everyone, Great questions, let’s dive right in. One thing I wanted to clarify is that this policy only affects devices that have not connected to CrashPlan Central in 6 months or longer. This does not affect volumes that have not conn
6.
by jarrodatCode42 11y ago
Hello All, Jarrod from Code42 here. Sorry about the scare. Wanted to clarify a few things. If a restore has been initiated from the archive of the device in question it's considered "connected" and your data won't be del