Reconnect a revoked cloud account used by DriveBackupV2

Applies to: DriveBackupV2; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

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

If authorisation succeeds but uploads still fail, compare cloud quota, folder ownership and provider availability. Repeating the linking flow will not repair a full destination or an unreadable local source. Preserve the exact provider error for support.

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.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report