Honest answers about how GWS Backup works.
When you backup a workspace for the first time, GWS Backup must perform a complete initial sync of all users, emails, and drive files. Google enforces strict API quotas and limitations on how often we can request information and how much data we can transfer per day.
Because we respect these limits to prevent your Google Workspace from being temporarily locked, the first run can take significantly longer than subsequent differential backups.
This is a feature, not a bug! Many other backup products will silently fail or claim a backup was "successful" even if Google throttled the connection midway through.
If we hit a Google API limit during a backup, we immediately mark the status as "Stopped" and explain the exact error. We believe in total transparency. We will wait for the next scheduled window, and the run will automatically continue exactly where it left off.
You don't need to do anything. GWS Backup uses Differential SQLite Tracing. During the next scheduled run, the engine will instantly recognize what has already been downloaded and will resume fetching the remaining data. Once the entire backup is completely verified, it will be marked as successful.
You can use the Restore Console to recover entire workspaces, specific accounts, or individual files and emails. Simply search for the item using our deep indexing tool and click restore to push it directly back to its original location.
You can set custom retention policies per client. Instead of a hard delete, we offer granular control so you can comply with data protection laws while avoiding accidental wipes. This allows you to phase out old data responsibly.