Seeding with partial file updating

[eadams]

I'm wondering if it's possible to seed a Syncovery backup if I plan on using partial file updating. I have a computer in my main office that has about 20GB than I need to backup. I'd like to use the $DWMQ rotation (not versioning) and to back up over a VPN to a NAS at a remote office. My backup set contains about 5000 files that change only infrequently and 3 database files (from 2 to 10 GB each) that change frequently. The inital backup is taking more than 24 hours, but it did get done. My question is there any way to seed a backup like this? In my remote office, I can copy a backup folder on the NAS and make a duplicate in a few minutes. If the first backup created a Sunday folder, could I manually create other folders for the $DWMQ rotation that could be read by Syncovery to take advantage of partial file updating?

[superflexible]

Yes you can do this, but the Partial File Updating will re-copy the three database files completely unless you install the Syncovery Remote Service on a computer near the backup NAS. The Remote Service will generate the necessary checksums for Partial File Updating on the fly every time. This is the only way you can combine Partial File Updating with variables such as $DWMQ.

The Remote Service needs to watch every one of the possible $DWMQ folders. On the Remote Service Control Panel, please avoid the checkmark "Check subfolders too" and list each folder separately instead. Because the subfolders watching is probably not going to work well with the NAS.

[eadams]

If I generate checksums with the Remote Service once from my satellite office, is this something I could turn off and still get partial file updating working with the Syncovery program running on a computer in my main office? Or once I start a backup profile with the Remote Service, will I always need to depend on it running?

[superflexible]

You have to keep the Remote Service running because the destination folder is different every day.

Without the Remote Service, Partial Updating cannot be combined with the $DWMQ variable, or any other variable in the path.

See also
http://www.syncovery.com/block-level-copying/

http://www.syncovery.com/remoteservice/

[eadams]

Just to let you know, everything worked perfectly with the Remote Service. I made one original backup to the NAS with the $DWMQ variable (I think it was Sunday), manually made copies on the NAS (Tuesday, Wednesday, Week 2, Month 2, etc.), and set the local computer monitoring the NAS to watch all of those folders. All the backups are working fine now. With my 21GB backup, instead of taking 24 plus hours, it now completes in about an hour.

You have a new customer. I bought my licenses. Thanks.