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

[Feature] Improve the creation of VSS Volume Shadow Copies #3371

Closed
LakeishaKowalczyk opened this issue Oct 4, 2023 · 2 comments · Fixed by #3543
Closed

[Feature] Improve the creation of VSS Volume Shadow Copies #3371

LakeishaKowalczyk opened this issue Oct 4, 2023 · 2 comments · Fixed by #3543
Labels

Comments

@LakeishaKowalczyk
Copy link

LakeishaKowalczyk commented Oct 4, 2023

Enabling VSS can provide write-on-copy and improved backup consistency (from inconsistent-backup to crash-consistent-backup), it would be highly beneficial if improvements could be made or enabled by default

  1. allow parallel creation of snapshots after enabling
  2. compatible with unicode characters, it now always reports ERROR upload error: The system cannot find the path specified if the snapshot path contains some unicode characters
  3. unneeded shadow copies are prone to residual
  4. configure it in policy --enable-vss=true
@philiplb
Copy link

philiplb commented Oct 4, 2023

This would be awesome :)

@mxk
Copy link
Contributor

mxk commented Dec 26, 2023

There was an attempt to do this before, but it didn't get merged (#2334). I just wrote my own replacement for the PowerShell scripts and a separate package for managing shadow copies. I could take a look at how much effort it would be to integrate this. The main motivation for me would be the ability to backup files without having to symlink or mount the shadow copy anywhere.

Until then, you are welcome to try my replacement to see if it fixes your unicode handling issues. Run go install github.com/mxk/fsx, and set fsx.exe vss kopia as your before and after snapshot action. It's been working well for me, but the tool is a work-in-progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants