A remote backup destination separates recovery data from the hosting server. Configure it with restricted credentials, tested retrieval and a retention policy so a successful upload becomes a dependable recovery option.
IN THIS ARTICLE
Information to have ready
Review the destination types supported by your installed Webuzo Backup & Restore interface. Current options can include SSH-based storage, supported cloud connections and S3-compatible storage. Choose a destination you control and estimate capacity, transfer time and any storage or retrieval charges.
01 Plan remote backup storage for Webuzo
- Open the backup utility and its Backup Servers area. Add a destination with a descriptive name and the exact endpoint, authentication and storage path required by that destination type.
- For an object-store destination, use a dedicated bucket or prefix and narrowly scoped access credentials. For an interactive cloud connection, authorize the intended account rather than a personal account that may later be unavailable.
- Use encrypted transport and validate the expected endpoint. Keep credentials out of public documentation and rotate them through the supported destination settings.
- Test the connection, then run a small real backup. Connection success alone does not prove that a complete archive can be uploaded and later downloaded.
- Confirm the archive at the remote destination, retrieve it and perform an isolated restoration test. Record a recovery route that does not require the failed original server.
- Set retention and monitor failed jobs, available capacity and credential expiry. Keep at least one useful older recovery point while replacing or rotating backups.
Does remote storage automatically make backups immutable?
No. Immutability depends on destination capabilities, versioning, retention and credential permissions. Test the intended protection separately and retain an independent recovery-access plan.
Check the backup or recovered data
Check completion logs and compare remote archive names, dates and sizes with the intended account backup. Test retrieval using the emergency access method. Verify that retention rules do not remove all versions after an accidental local deletion.
Troubleshoot unexpected results
If remote backup fails, distinguish authentication, endpoint, permissions, network and capacity errors. Do not make a private bucket public to resolve an upload error. Retain a protected temporary backup while repairing the destination and confirm later scheduled work uses the corrected credentials.