Duplicacy doesn’t recognize backups after migrating to a new Google Drive account – Need help!

[wbrkct]

Hi everyone,

I use Duplicacy to back up my local server. Some of the data is stored on Google Drive, while other files are backed up to a local NAS. Since my original Google Drive account ran out of space, I created a new Google Drive account.

My plan to move the backups was as follows:
1. Download the files from the old Google Drive account.
2. Upload them from my PC to the new Google Drive account.

I completed these steps. However, when I try to set up the new Google Drive account as storage in Duplicacy, I run into issues:
• When I keep the old config file, Duplicacy logs indicate that the storage is not initialized.
• When I use the new config file, Duplicacy detects 0 chunks and 0 files.

Does anyone know how to migrate the files to the new Google Drive account so that Duplicacy can recognize them correctly?

Thanks in advance for your help!

[saspus]

@wbrkct

However, when I try to set up the new Google Drive account as storage in Duplicacy, I run into issues:

More details are needed. Where was old storage located, where was new storage located, how do you try to initialize it, including the token and path.

Duplicacy does not care where the storage is located, all it needs is to be able to read the config file and find other folders at the same level.

@wbrkct

Since my original Google Drive account ran out of space

What account do you use? I’m pretty sure you cannot run out of space on google drive. You would hit chunk enumeration performance limitations way before that, around 5 TB mark. How much space have you used?

[wbrkct]

I switched Google Drive Accounts because in my case i just need about 10GB of storage for the Backup. At first I had the Backup in my private Google Drive. But because there are also other files. I ran in the free 15GB limit.
So i created a new Google Account with again 15 GB free space, which I use for the Backups only.

@saspus

More details are needed. Where was old storage located, where was new storage located, how do you try to initialize it, including the token and path.

The old storage was in my old google drive (gcd://Backup/HIVE/appdata). The new storage is in the same spot.
I’ve created a new Storage with the same name and password as the old one. The token to access the google drive is newly created.

When snapshots-folder and chunks-folder and config are all copied to Backup/HIVE/appdata a new "config"file is created after creating the storage.

[saspus]

The problem is likely that copying the data manually and then attempting to adopt that backup with duplicacy does not work due to new stricter access policy enforcement on Google Drive: Duplicacy can only access data it created itself. If you copied data manually — Duplicacy won’t be able to read it, because it did not create it.

What you need to do instead:

• initialize a new empty storage on your new Google Drive
• add that new storage to the old repository
• run duplicacy copy … to copy everything from old storage to the new
• from there on start making subsequent backups into the new storage.

Side note — it would be much cheaper to give Google $2/month and get 100GB there than spend time trying to juggle multiple Google accounts and moving data. What will happen when you run out of 15GB and need more? You would need to move it back and add storage anyway. $2/month is not worth anyone’s time. Alternatively, you can start backing up to an actual cloud storage designed for the job. For example, Backblaze B2 or Storj. At cost of $0.004/tb/month your 15GB will cost you about 6 cents per month. Not only it would be vastly cheaper but also perform much better. It’s a no-brainer really.