Google Workspace Recovery Planning Starts Before an Employee Leaves

A recovery discussion with a deadline

N-able published Google Workspace backup guidance October 14, urging MSPs and IT teams to test recovery and protect backup copies separately from production. The vendor sells backup services, so its recommendations should be evaluated alongside the platform’s own documentation. Google’s current administrator guidance supplies a particularly useful boundary: a deleted user account can be restored for up to 20 days. After that period, Google says the account and its data cannot be restored through that process.

Restoring an account has prerequisites

Google also documents conditions that can prevent restoration, including the absence of an available license for the user’s previous service or edition, or a domain that is no longer available or has moved to another Workspace account. Its instructions say restoration usually takes up to 24 hours, with rare cases taking up to five days. These limits describe the deleted-user restoration workflow; they should not be generalized to every Drive, Gmail or retention feature. A customer’s recovery plan needs the correct procedure for the particular loss.

Translate retention into an operating decision

For a small media business, a departing producer’s account may be connected to production schedules and working documents. A school may need continuity when a staff member leaves during term. Those are illustrative planning scenarios, not reported incidents. Our analysis is that the offboarding ticket should record a decision about the required information before an administrator deletes the account. Identify the business owner, the approved destination for continuing work, and the retention or legal requirements that apply. Keeping every account indefinitely is not a substitute for making those decisions.

Test the service the client is buying

An MSP can demonstrate recovery with a controlled test using non-sensitive sample data and an authorized test account. Record what is restored, how long the process takes, who authorizes it and whether the resulting access matches the client’s needs. If a separate backup product is used, ask the supplier to demonstrate the relevant recovery scenario rather than relying on a broad feature list. Our recommendation is to include recovery limits and responsibilities in the service review, so the client knows which losses the agreed service can address and which require another arrangement.

Related: WatchGuard’s October Platform Rollout Gives MSPs an Automation Test →