[Help] USB Copy update breaks folder structure [SOLVED]

[magnus4ever]

After the recent USB-copy update (July 24th), I'm having issues because USB Copy now creates new paths for each backup task instead of snychronizing the files like it should do. I Noticed it beacuse all of a sudden my external Backup drive was "full" when it schouldn't be even near max capacity.

Before the update it behaved like this:

Code: Select all

usb_disk\"Name of Backup Folder on USB drive"\ "Name of Source folder"

After the update USB copy now all of a sudden creates a subfolder named after the Volume where the source is located, so:

Code: Select all

usb_disk\"Name of Backup Folder on USB drive"\ [b]"Volume Name"[/b] \ "Name of Source folder" 

This of course now creates an issue because instead of just syncing changes, USB copy now wants to copy over ALL files again, filling up the drive.

Interestingly, TOS6 wont let me move my files into the subfolder stating "not enough space"....

[MissionAborted]

Same here. This pretty much ruined my backups for the time being.

I have 4 folders in the backup source labeled "Music," "Movies," "TV Shows," and "Other." USB Copy always copied these folders to the root of the backup destination with no issue using mirroring... now, it creates a new folder structure in the root of the backup destination - Volume1/MyNASName/Music (etc.)

This absolutely SUCKS and I hope it gets fixed soon. I'm in the same boat - can't backup anything else because I don't have enough space for 2 full backups.

[Gremlin]

Maybe take a look at TFM backup & using the mirroring function there.

[GevinKe]

Same here. This pretty much ruined my backups for the time being.

I have 4 folders in the backup source labeled "Music," "Movies," "TV Shows," and "Other." USB Copy always copied these folders to the root of the backup destination with no issue using mirroring... now, it creates a new folder structure in the root of the backup destination - Volume1/MyNASName/Music (etc.)

This absolutely SUCKS and I hope it gets fixed soon. I'm in the same boat - can't backup anything else because I don't have enough space for 2 full backups.

We sincerely apologize for any inconvenience this may have caused.

In this update, we’ve addressed a core pain point in the previous version of USBCopy: previously, users could only select a single folder as the backup source per task. To back up multiple directories, multiple tasks had to be created—an approach that was cumbersome and difficult to manage.
To enhance usability, the latest update now allows multiple folders to be selected as backup sources within a single task, significantly simplifying the process of backing up multiple directories.

However, allowing multiple folders in one task introduces the challenge of potential folder name conflicts.
For example, when selecting the following paths:

• Volume1/ShareFolderA/Music

• Volume1/Music

• Volume2/ShareFolderB/Music

If only the folder name (e.g., “Music”) is used as the backup destination, these identically named folders would conflict or overwrite each other, potentially leading to data loss or corruption.
To avoid this, the application now retains the full path structure of each selected folder during backup. This ensures that each source directory can be accurately restored and prevents data conflicts caused by duplicate folder names.

Since the new version uses a different path structure compared to your original backup tasks, the application does not automatically migrate or merge historical backup data in order to ensure data security and integrity. Therefore, when performing a backup again, the application will re-execute a full backup using the new path structure.

Note: Your previous backup data will not be overwritten or deleted automatically and will remain in its original location. If you confirm that the old data is no longer needed, you may manually delete the original backup files to free up storage space.
Alternatively, you can choose to recreate the backup task to take full advantage of the new features introduced in this update (such as enhanced file filtering rules).

[GevinKe]

We sincerely apologize for the inconvenience caused by this update.

Regarding the newly introduced features—support for selecting multiple folders within a single task and backup using full path structure—please refer to my previous explanation in response to @MissionAborted. These changes aim to improve the convenience of backing up multiple directories while preventing data overwrite issues caused by folders with identical names.
Since the new version uses a different path structure compared to your original backup tasks, the application does not automatically migrate or merge historical backup data in order to ensure data security and integrity. Therefore, when performing a backup again, the application will re-execute a full backup using the new path structure.

Note: Your previous backup data will not be overwritten or deleted automatically and will remain in its original location. If you confirm that the old data is no longer needed, you may manually delete the original backup files to free up storage space.
Alternatively, you can choose to recreate the backup task to take full advantage of the new features introduced in this update (such as enhanced file filtering rules).

Additionally, you mentioned encountering a “not enough space” warning when transferring files. Could you please confirm whether this operation was performed on a USB device mounted on the NAS? To help us identify the root cause more accurately, could you kindly provide the following:

• Detailed steps of the operation

• Screenshot or screen recording of the error message

• The exact storage location involved (e.g., USB device path, volume name, etc.)

We will analyze the issue based on the information you provide and offer a solution as soon as possible.
Thank you for your understanding and continued support. Please feel free to contact us if you have any further questions.

[MissionAborted]

I appreciate the work you do on USB Copy.

The new update, however, simply doesn't work for me, as it means I will indeed need to manually delete my current backups in order to complete a full Volume1/ShareFolderA/Music type backup. I am not getting insufficient space messages but can see I don't have enough to have 2 complete backups on my backup destination, which absolutely sucks and puts me in a hard spot.

Having lost a significant amount of data in the past (not with USB Copy), I am very reluctant to delete any form of backup to start again.

I wish I knew this was planned for the update. I wouldn't have updated to the new version. If there was a way to opt to save multiple folders or not (user choice) that would be amazing.

Thanks again for the work you put in on this.

[MissionAborted]

Maybe take a look at TFM backup & using the mirroring function there.

Thanks! Might be the best option for me moving forward.

[GevinKe]

I appreciate the work you do on USB Copy.

The new update, however, simply doesn't work for me, as it means I will indeed need to manually delete my current backups in order to complete a full Volume1/ShareFolderA/Music type backup. I am not getting insufficient space messages but can see I don't have enough to have 2 complete backups on my backup destination, which absolutely sucks and puts me in a hard spot.

Having lost a significant amount of data in the past (not with USB Copy), I am very reluctant to delete any form of backup to start again.

I wish I knew this was planned for the update. I wouldn't have updated to the new version. If there was a way to opt to save multiple folders or not (user choice) that would be amazing.

Thanks again for the work you put in on this.

We sincerely apologize for the inconvenience caused by this update.

After evaluating multiple solutions, we found that only two methods are currently effective: manually clearing old backup data or recreating the backup task.

We regret not providing sufficient notice about the path structure changes, which may have caused confusion. Your feedback is valuable and will help us improve future updates and notifications.

Thank you for your understanding and support. Please feel free to contact us if you need further assistance.

[magnus4ever]

Thanks for your explanation Gevin, the update to include multiple folders in a single task is a well appreciated addition!

My next move is to use my Laptop and a Linux Live Distro to move all data into a folder structure USB Copy can sync to, if that doesnt work i might just wipe it and start clean, as I have a second Backup to rely on.

Recreating the task didnt work for me as no matter what, USB copy always will add the "Volume X" subfolder.

[GevinKe]

Thanks for your explanation Gevin, the update to include multiple folders in a single task is a well appreciated addition!

My next move is to use my Laptop and a Linux Live Distro to move all data into a folder structure USB Copy can sync to, if that doesnt work i might just wipe it and start clean, as I have a second Backup to rely on.

Recreating the task didnt work for me as no matter what, USB copy always will add the "Volume X" subfolder.

Hello,

Since "VolumeX" is inherently part of the real-time path, even if a backup task is recreated, the generated path structure will still use a subfolder named "VolumeX" as the first-level directory.

Why is "VolumeX" used as the top-level of the real-time path?
In scenarios where one task backs up multiple folders, we introduced the "VolumeX" level for two key reasons:

1.To avoid name conflicts in the target path
Without this layer, multiple source folders would be placed directly at the backup destination. If several folders have the same name (e.g., Music or Photos), they could easily overwrite each other or cause conflicts, resulting in disorganized data.

2.To improve data management and migration
With the "VolumeX" structure, backup data has a clear and consistent layout, making it easier to identify the source volume and more efficient to transfer, restore, or clean up later.

We understand your request to simplify the path structure by removing the "VolumeX" folder. This suggestion has been submitted for internal evaluation, and we will consider it along with broader user feedback and experience.

However, removing this level due to another adjustment in the path structure may lead to previously discussed issues:

1.A full backup may be triggered upon the first run of old tasks due to path structure changes.

2.Manual cleanup of old backup data may be required to free up storage.

Thank you again for your valuable feedback — it plays an important role in helping us improve our product!