Loop Backup's two-administrator approval controls add a separate check before protected backup data can be permanently deleted, even when the requester is a root administrator.
Backup deletion protection separates requesting permanent deletion from approving it. One administrator selects protected backup data and submits a request, which enters a pending approval queue. The backup data remains protected while a different authorised administrator reviews the request and approves or declines it. Only after separate approval is deletion scheduled. This is dual-control authorisation, also called the four-eyes principle. In the root-administrator test reported by the Loop Backup team, a backed-up file could not be deleted by the root administrator alone: another administrator had to approve the request. The interactive simulated demo uses fictional administrators and sample files to show a request, blocked self-approval, second-administrator review, approval and decline; it does not access or delete real backups. Separate approval adds a barrier against a single compromised account, accidental deletion and insider misuse, but does not guarantee protection against every attack or establish compliance. Organisations should also use multifactor authentication, appropriate permissions, secure retention policies and regular recovery testing. Explore related guidance on separate backup access and ransomware cloud sync, plus Microsoft 365 (formerly Office 365) and Google Workspace backup. Loop Backup runs 4 backups per day and offers a standard 14-day free trial with free assisted setup over Google Meet or Zoom.
In Loop Backup's reported root-administrator test, the permanent-deletion request went into a pending approval queue. A different authorised administrator had to review and approve it; the requester could not complete deletion alone.
Submitting a request does not immediately delete the selected protected backup data. It remains protected while a different authorised administrator reviews the request.
Dual control, also called the four-eyes principle, separates requesting a sensitive operation from approving it. One administrator requests permanent backup deletion and another authorised administrator approves or declines it.
The workflow described here schedules deletion only after separate approval. The demonstration does not specify a deletion delay or retention override, and does not delete real backups.
No. Separate approval adds a barrier against a single compromised administrator account, accidental deletion and insider misuse, but no individual feature stops every attack. Use multifactor authentication, appropriate permissions, secure retention policies and regular recovery tests as well.
No. It uses fictional administrators and sample backup files in your browser. Requests, approvals and the audit trail are simulated; no customer data is accessed or deleted.