Interactive demo · about 3 min

Backup

Back up any storage to any destination in minutes

Follow a complete backup from start to finish — pick a source, choose a destination, and watch the transfer complete. Any direction works, across 70+ cloud providers and local folders.

  • Back up cloud-to-cloud, local-to-cloud or local-to-local
  • Track progress live and review detailed job logs
  • Save the job and re-run it with one click
Open in new tab ↗

Watch next

See all demos →

Step-by-step guide

How to back up files to cloud storage

The same 27 steps as the interactive demo, with screenshots — skim it, or jump into the demo at any step.

  1. 1

    Open the Wizard for a guided setup.

    We begin on the RcloneView home screen. Click Wizard to open the guided setup.

    Try this step ↗
    Step 1: Open the Wizard for a guided setup.
  2. 2

    Backup is a one way copy: your originals are never changed.

    The wizard can handle several jobs. One way means files travel from source to destination only. Your originals are never touched, and neither is anything already sitting at the destination.

    Try this step ↗
    Step 2: Backup is a one way copy: your originals are never changed.
  3. 3

    Pick the cloud that will hold the backup. More than eighty providers are supported.

    First we add a remote to back up to. RcloneView supports more than eighty backends, and any of them can be a backup destination. For this demo we will use Google Drive.

    Try this step ↗
    Step 3: Pick the cloud that will hold the backup. More than eighty providers are supported.
  4. 4

    Provider chosen. Next you name the connection and authorize it.

    With the provider selected, click Next.

    Try this step ↗
    Step 4: Provider chosen. Next you name the connection and authorize it.
  5. 5

    Give this connection a short name you will recognize later.

    Give the new remote a short name you will recognize later. This is simply a label for the connection, and you will see it everywhere in RcloneView.

    Try this step ↗
    Step 5: Give this connection a short name you will recognize later.
  6. 6

    The name you type here is how this cloud appears everywhere in RcloneView.

    We will call ours my google drive. Click Next to save it and start the connection test.

    Try this step ↗
    Step 6: The name you type here is how this cloud appears everywhere in RcloneView.
  7. 7

    Sign in on Google's own page. RcloneView never sees your password.

    Your provider's own sign in page opens. Authorize the connection there. The access token is stored locally on your computer, and RcloneView never sees your password.

    Try this step ↗
    Step 7: Sign in on Google's own page. RcloneView never sees your password.
  8. 8

    Once that's done, click on the element.

    RcloneView verifies the remote right away. Connect, authenticate, and list root all pass, so you know the connection works before you rely on it. Click Next.

    Try this step ↗
    Step 8: Once that's done, click on the element.
  9. 9

    The source is what you back up. Your local disk is a remote here, just like the cloud.

    Now tell the wizard what to back up. Notice that your local disk sits in the same row as your cloud remotes. In RcloneView any configured location can be a source, and here we start from the local disk.

    Try this step ↗
    Step 9: The source is what you back up. Your local disk is a remote here, just like the cloud.
  10. 10

    Open a folder to narrow the source down to exactly what you want copied.

    We will use My Pictures, which contains the Adtech folder with thirty three photos inside.

    Try this step ↗
    Step 10: Open a folder to narrow the source down to exactly what you want copied.
  11. 11

    Source is set. Next you choose where the copy lands.

    Click Next to choose where the copy will land.

    Try this step ↗
    Step 11: Source is set. Next you choose where the copy lands.
  12. 12

    The destination receives the copy. Any remote can go here, including another cloud.

    The destination is the side that receives the files. Any remote can go here, including a second cloud account or another folder on the same machine. We will pick my google drive.

    Try this step ↗
    Step 12: The destination receives the copy. Any remote can go here, including another cloud.
  13. 13

    Open or create the folder that will hold the backup.

    Ours is called My Pictures Backup. Keep in mind that this folder is not empty, because that will matter in a moment.

    Try this step ↗
    Step 13: Open or create the folder that will hold the backup.
  14. 14

    Both sides are set: My Pictures on your disk, My Pictures Backup in the cloud.

    My Pictures on the local disk is the source, and My Pictures Backup in Google Drive is the destination. Click Next.

    Try this step ↗
    Step 14: Both sides are set: My Pictures on your disk, My Pictures Backup in the cloud.
  15. 15

    The defaults suit most backups. Just click "Next"

    Filters let you skip files that are too large, too old, or too deep in the folder tree. The recommended defaults are already in place, so most people can simply click Next.

    Try this step ↗
    Step 15: The defaults suit most backups. Just click "Next"
  16. 16

    A dry run lists every file it would copy, before anything moves.

    Before anything is written, RcloneView does a dry run. Every file it intends to copy is listed here by name and size. Nothing has left your computer yet.

    Try this step ↗
    Step 16: A dry run lists every file it would copy, before anything moves.
  17. 17

    33 to copy, 0 to delete. A one way copy never removes anything at the destination. Click "Execute"

    Read the summary line. Thirty three files to copy, nothing skipped, and zero to delete. That zero is the difference between a backup and a sync. A sync makes the destination match the source and removes whatever is extra. A copy only adds and updates.

    Try this step ↗
    Step 17: 33 to copy, 0 to delete. A one way copy never removes anything at the destination. Click "Execute"
  18. 18

    The backup started, and the wizard saved it as a reusable job.

    The backup is running, and notice what else happened. Everything you just answered was saved as a job. You never have to walk through the wizard again for this pair of folders. Open Job Manager to see it.

    Try this step ↗
    Step 18: The backup started, and the wizard saved it as a reusable job.
  19. 19

    Your wizard answers are now one saved job: source, destination and options together.

    Here is that job. Source, destination, job type and options are all stored in a Job. It is unscheduled for now, so it runs when you tell it to, and you can give it a schedule later.

    Try this step ↗
    Step 19: Your wizard answers are now one saved job: source, destination and options together.
  20. 20

    Watch the transfer live: progress, speed and time left, file by file.

    While the job runs, the transfer panel shows progress, speed and time remaining, file by file. Seventeen percent through, and the first photos are already marked success.

    Try this step ↗
    Step 20: Watch the transfer live: progress, speed and time left, file by file.
  21. 21

    Open the destination in its own tab to check the result yourself.

    Open a new tab so we can look at the destination directly.

    Try this step ↗
    Step 21: Open the destination in its own tab to check the result yourself.
  22. 22

    Choose the remote you just backed up to.

    Choose my google drive, the remote we just backed up to.

    Try this step ↗
    Step 22: Choose the remote you just backed up to.
  23. 23

    The Adtech folder was created by the copy, mirroring your local structure.

    Open My Pictures Backup. Open it.

    Try this step ↗
    Step 23: The Adtech folder was created by the copy, mirroring your local structure.
  24. 24

    33 files on the left, 34 on the right. The extra file was already there and survived the backup.

    Now compare the two panes. The local folder holds thirty three photos. The backup holds thirty four. The extra one was already in the destination before we started, and the backup left it exactly where it was. A sync would have deleted it. That is what a one way copy protects you from.

    Try this step ↗
    Step 24: 33 files on the left, 34 on the right. The extra file was already there and survived the backup.
  25. 25

    Come back to the saved job to see what it is worth.

    The files are safe. Now let's go back to that saved job and see what it is worth. Open Job Manager.

    Try this step ↗
    Step 25: Come back to the saved job to see what it is worth.
  26. 26

    The same job, now with a last execution time recorded.

    The job is still here, and it now shows when it last ran. Select it to work with it.

    Try this step ↗
    Step 26: The same job, now with a last execution time recorded.
  27. 27

    Run repeats the whole backup with one click. Dry run previews it first.

    This is the payoff. One click on Run repeats the entire backup, and because it is a copy, only new and changed files move. Dry run previews it first, and Edit Job lets you change the paths or add a schedule.

    Try this step ↗
    Step 27: Run repeats the whole backup with one click. Dry run previews it first.
  28. Ready to try it yourself?Free for Windows, macOS and Linux.
    Get RcloneView Free