• Roger Averdahl
    0
    I am using an Backblaze B2 account and noticed a couple of days ago that there is no tickbox in CBB for "Encrypt filenames" when doing a backup directly to Backblaze of when doing Hybrid backups, iow local and then to Backblaze.

    Is there a reason behind this? Are the file names created by CBB simply too long?

    I did a test on a local backup with "Encrypt filenames" enabled and wanted to see if i can restore the backup if i simply move all backupfiles to another drive. I could not test it full since Windows Explorer complained about not being able to move some files because they are too long. That made me think that the length of the file names could be the issue during upload/storage/etc. (Yes, it´s a long shot...)

    Second question:
    When using the "Encrypt filenames" feature, is there a way to reduce the length of the file names?

    CBB: 6.3.2.205
    Win 10 Pro for Workstations: V. 2004, OS Build. 19041.388
  • David Gugick
    57
    It's simply a current limitation in the product. It is scheduled to be released in a future version. I'm checking with the team now to see if it's officially scheduled yet.
  • Roger Averdahl
    0
    O.k, got it! :)

    It would be great if it was an aviable feature for Hybrid backups and it would be great to have the ability to have some control over the length of the file names since Windows Explorer complains when moving them.

    I do realize that moving the backup files is not recommended, but if the disk shows sign of "soon-to-be-dead" it is importand to being able to move the backup from HDD X to HDD Y without any error messages/limitations from Windows Explorer such as this:
    dest-path.png
  • David Gugick
    57
    I am not sure why the names are so long. I will log your request and ask the team. Thanks.
  • David Gugick
    57
    Let me add that the Windows maximum file name length is 32,767 characters. You can easily enable long filename support with a registry or group policy edit. https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

    But I want to confirm with the team this is fully-supported for backups, so stay tuned.
  • Roger Averdahl
    0
    After some testing it seems that this is a bug in Windows Explorer. If i copy the files with Windows Explorer i get tons of those errors but if i use another file explorer, Directory Opus, i can move the files and all files move and match each other and i get no errors from Directory Opus.

    Both HDD´s are NTFS formatted.
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment

Welcome to MSP360 (CloudBerry) Forum!

Thank you for visiting! Please take a moment to register so that you can participate in the discussions!