Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Sync Option Does Not Use "Backup Instance Name" To Separate Sync'd Files From Different Systems #123

Open
BrettEBowman opened this issue Oct 4, 2023 · 6 comments
Labels
backlog item in backlog stale

Comments

@BrettEBowman
Copy link

When using the "File Sync" option, in OneDrive, the sync'd files from all systems are getting mixed together (and overwritten where duplicates exist?) under the hassio_onedrive_backup/FileSync/ folder. I would expect that the "Backup Instance Name" parameter should be used as the "top level folder" here so that files from each system are kept separate.

@lavinir
Copy link
Owner

lavinir commented Oct 4, 2023

You're right, the instance name only effects the backups (as implied by the name..)
It makes sense to have that ability for File Syncs as well. I will add this to the backlog

@lavinir lavinir added the backlog item in backlog label Oct 4, 2023
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jan 13, 2024
@BrettEBowman
Copy link
Author

I would like to see this ability added. It is confusing (and problematic when there are duplicate file names) with the files from multiple HA servers getting mashed together.

@github-actions github-actions bot removed the stale label Aug 19, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Sep 18, 2024
@lavinir lavinir removed the stale label Sep 25, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Oct 26, 2024
@lavinir lavinir removed the stale label Nov 25, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog item in backlog stale
Projects
None yet
Development

No branches or pull requests

2 participants