CrashPlan - Modify backup times
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
CrashPlan can occupy substantial CPU time when backing up or verifying files. You can prevent this from occurring during work hours.
- Login to crashplan https://console.us2.crashplan.com/app
- You should be presented with a dashboard listing your machines that CrashPlan is aware of. This can include machines that have been replaced by newer machines. Find the machine you are currently using in the list and click its Device Name link.
- You should be taken to a page giving a read-only overview of the machine's backup settings. Click the drop-down at the top-right (with a gear icon) and select "Edit...".
- You should be shown a dialog with several tabs. Select the "Backup" tab.
- Ensure backups are enabled. If you see the "enable" button in the "General" section, click it to enable backups.
- Set "Backup will run:" dropdown to "Between specified times"
- Enter reasonable times in 24-hr format in the next two boxes. I used 23:00 in the first box (start time) and 07:00 in the second box (end time). Feel free to select days when the backup is allowed to run.
- Set "Preferred time for verification scan:" dropdown to "hours".
- Enter a reasonable number of hours. I used 2. We may need to experiment to find an optimal value. This is necessary as the "days" option will conflict in unexpected ways with the "Between specified times" option of "Backup will run".
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No target file is named. Start by locating the repository's existing backup or CrashPlan documentation, then add the numbered procedure from the issue, including the scheduling and verification settings. Done means a reader can follow the documented steps to limit backup activity to the selected hours.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100