Throughout all of our communications, we continued to offer other options for his consideration in order to comply. At this point Greg refused to engage with us in efforts to reduce his archive size and indicated that he was going to pursue other options, including discussing with a lawyer. We did note to Greg on May 3rd, 15 days after our initial communication, that he had made some changes to reduce the size of his archive he did need to see more reductions in order to comply with our policy. Because we recognize that there are situations where very large amounts of data will need to be protected with CrashPlan for Small Business, we offered an alternative to Greg where he could split his backup across multiple devices to keep his archive size smaller and thereby ensuring that, should the worst happen, he will be able to have access to his data.įinally, our procedure is to not take adverse action against an account if they are making a good-faith attempt to resolve the situation. Even the 10TB goal that we set will cause issues during a restore. As we notified Greg of in our communications, we also know that anyone with a very large backup archive is at a very high risk of never being able to retrieve information from the backup. When we notified Greg of the situation, we provided a complimentary subscription extension for approximately 2 months to allow Greg time to make any needed changes to his backup. Under the terms of our MSA, we reserve the right to take action when this occurs, additionally, our MSA notes that we will work with the account holder to remediate the situation before taking any adverse action against an account. During normal scans of our systems, Greg’s account was flagged for having a storage amount that had a detrimental effect on other subscriber’s use of our software.
0 kommentar(er)
