I had been running my WHS 2011 with DrivePool 2.2.0.651 for a long time with CrashPlan without any problems. After updating to 2.2.0.852, which required a clean install because of hibernation failures, I have discovered CrashPlan can no longer detect new file creation or changed files in the Pool (it still can on my C: drive). So, the real time file backups are not occurring for anything created or modified in the Pool. The new and changed files are not found until CrashPlan scans the entire Pool at the end of the day.
I know CrashPlan requires NTFS volumes for real time file backup, and my Pool is NTFS.
Is there a reasonable possibility something changed with the update that would cause CrashPlan to have trouble seeing file changes in the Pool? I will also check with CrashPlan to see if there is anything I can troubleshoot.
Question
Wonko
I had been running my WHS 2011 with DrivePool 2.2.0.651 for a long time with CrashPlan without any problems. After updating to 2.2.0.852, which required a clean install because of hibernation failures, I have discovered CrashPlan can no longer detect new file creation or changed files in the Pool (it still can on my C: drive). So, the real time file backups are not occurring for anything created or modified in the Pool. The new and changed files are not found until CrashPlan scans the entire Pool at the end of the day.
I know CrashPlan requires NTFS volumes for real time file backup, and my Pool is NTFS.
Is there a reasonable possibility something changed with the update that would cause CrashPlan to have trouble seeing file changes in the Pool? I will also check with CrashPlan to see if there is anything I can troubleshoot.
Thank you for your assistance.
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.