Skip to content

Knowledgebase

Sending a SiteWorx backup to a remote destination

control-panels, backups

Sending a backup to a separate destination reduces dependence on the hosting server’s local storage. Use a supported encrypted transfer method and verify the remote file before considering the job complete.

What you need before you begin

Create a dedicated destination account with access only to the required backup directory. Confirm its hostname, port, credentials, free space and retention arrangements. Keep the destination outside a publicly served folder.

01 Send a SiteWorx backup to a remote destination

  1. Open Backups > Backup Now for an on-demand job, or edit the intended backup schedule.
  2. Choose the required backup scope and the available SFTP/SCP destination option. Continue to its connection details.
  3. Enter the destination hostname, port, username, password and exact remote directory. Coordinate SSH host verification or connection requirements with the provider where necessary.
  4. Run one small representative backup and inspect the completion result. Sign in to the destination independently to verify the archive exists with a plausible size.
  5. Test that the archive can be read or restored using the supported recovery procedure. Monitor subsequent transfers and maintain retention at the remote destination.

Check the backup or recovered data

The archive should arrive at the intended private destination, and recovery should not depend solely on credentials stored on the source server.

Troubleshoot unexpected results

Authentication, firewall, directory permissions and destination capacity can each prevent transfer. Correct the specific error rather than falling back automatically to unencrypted FTP. An archive that was created locally may still have failed during remote transfer.

Does a remote destination make the backup immutable?

No. A writable remote account may also be able to overwrite or delete copies. Independent retention, restricted credentials and destination-side protection require separate configuration.

Sources and further reading

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support