Copy - Two storages are not compatiable for the copy operation


#1

Having some issues getting copy to work using Duplicacy with my vertical backups. I’m potentially getting things a little muddled up so appreciate some advice on where I might be going wrong.

Vertical backup currently runs on my ESXi host and backups to an NFS share on my NAS (FreeNAS).

I’m running a jail on FreeNAS that hosts Duplicacy and has the same directory mounted within the jail to carry out maintenance (been working fine for months).

I did this by doing an init on the /root directory of the jail with a dummy snapshot id (DuplicacyNAS01) that uses the same storage as my vertical backups.

I’m now trying to copy the storage to my B2 storage which is already being used by Duplicacy.

From /root on my jail I ran:

Duplicacy add -copy DuplicacyNAS01 -e DuplicacyNAS01 Vertical_Backups b2://<storage_url>

This worked fine and I got:

/root will be backed up to b2://<storage_url> with id Vertical_Backups

Now I run the following from /root:

duplicacy copy -d <snapshot id> -from default -to DuplicacyNAS01

I get the following:

Source storage set to /mnt/Backup/Vertical_Backup/
Destination storage set to b2://<storage url>
Enter Backblaze Account ID:############
Enter Backblaze Application Key:################################
Enter destination storage password:********************
Two storages are not compatiable for the copy operation

Little stuck now, I’m not sure what I’ve missed?

Duplicacy version: 2.0.10

Vertical Backup version: 1.2.0


#2

So, after a bit of reading I understand that the compression level and chunk sizes need to match in the 2 storage locations.

Unfortunately this is not the case:

NFS:

Compression level: 100

Average chunk size: 1048576

Maximum chunk size: 1048576

Minimum chunk size: 1048576

Chunk seed: 766572746963616c6261636b7570

B2:

Compression level: 100

Average chunk size: 4194304

Maximum chunk size: 16777216

Minimum chunk size: 1048576

Chunk seed:

f2e10094d7056c8136e2fdb75ecc4bb03f9b33e300875648b982ac8b2296dfdc

I’ve no idea how to set them up so they match?


#3

When you run this command:

Duplicacy add -copy DuplicacyNAS01 -e DuplicacyNAS01 Vertical_Backups b2://<storage_url>

the B2 storage at storage_url should not have been initialized before.

The chunk sizes of your B2 storage mean that it was initialized by Duplicacy with the default options.


#4

So is it a case that I can’t use vertical backup to back up to the same storage I already use for Duplicacy backups?

Or is there some precursive actions I need to take if I want the two applications to backup to the same storage (the intention here is to maximise the deduplication of my cloud backups).


#5

You won’t get any deduplication between Duplicacy and Vertical Backup due to the differences in how they split files into chunks. Duplicacy uses variable-size chunking while Vertical Backup uses fixed size chunks so chunks will most likely be different in sizes.

It is technically possible for Duplicacy to back up to a storage initialized by Vertical Backup but the performance will be terrible if there are too many small files which will need to be uploaded individually (instead of being packed first).