Reconnect a revoked cloud account used by DriveBackupV2
A cloud upload can fail after account access is revoked, an organisation changes policy or stored authorisation expires. A successful local archive does not mean a remote recovery copy exists. Check the upload result separately before assuming the backup is protected off-server.
Record the starting point
Keep the relevant upload error, plugin version and last confirmed remote backup time. Verify that the cloud account is still available and has capacity. Do not paste access tokens, refresh tokens or linking URLs into a public ticket or chat.
Work through the change
- Distinguish an authorisation failure from a full quota, provider outage or local archive error. Use the log's first relevant message rather than only the final failed status.
- Follow the maintainer's linking instructions for the selected provider. The documented linkaccount flow includes Google Drive and OneDrive; use the command and provider name supported by the installed release.
- Complete authorisation with the intended backup account and review the requested access. Keep any returned secret in the plugin's private configuration rather than a public note.
- Run a controlled backup and check that the expected archive appears in the intended remote folder. Download and inspect it separately from the local copy.
Check the result
The new upload should complete and the remote archive should be usable. Record the relinking date and last verified recovery point without storing credentials in the change note. Check the next scheduled cycle too, because an interactive test alone does not prove the normal schedule works.
If the result differs
Keep local recovery archives while cloud access is repaired. If the wrong account was authorised, revoke that access and relink deliberately. Do not delete the only recent backup or switch to a public file share to bypass an account problem.