- #Does backblaze support folder backup archive#
- #Does backblaze support folder backup zip#
- #Does backblaze support folder backup free#
But now it seems that is not the case.īefore immutability was supported, it took me 45 days to get them to review their advice on lifecycles settings and finally admit that it should be set to "keep only the latest version". Based on communication with Veeam support and responses here, I got the impression that the problem is now understood, and a fix is forthcoming. My problem is about SOBR offload failing due to the "DeleteMultiplObjects" error. So, once again, I'm not complaining about logging of some seemingly innocuous error. The backup to performance extents continue without error, but that is no consolation. I have been working with Veeam support for over 2 weeks now and still waiting for a solution. If that was not the case this thread wouldn't have existed. Offloading to capacitty tier does fail on this error and, in my case, the offload is now behind 25 restore points.
#Does backblaze support folder backup free#
I hope that helps? If not - please feel free to reply OR open a ticket with Backblaze and make sure you mention Nilay sent you there so I can keep my eye on the ticket. If you are experiencing errors in completing the backup jobs OR if restore/recoveries are failing against backups where this error is found, please let us know. My understanding is that this error does not cause a backup job from failing. Backblaze is committed to fix this and the log messages will disappear. As I mentioned previously, the Backblaze B2 functionality differs a bit from the S3 protocol, and that is why you see the NoSuchVersion error. Therefore, the Veeam client will simply try to delete the objects again. And the Veeam client has no way to knowing which were deleted and which were not. Backblaze B2 may have deleted some of the files, but not necessarily all of them. As an example, let's say the Veeam client sends a list of 100 objects to delete and before the delete is complete, the Internet connection breaks. This can happen for a variety of reasons, especially with an endpoint like DeleteMultipleObjects. Then, Veeam will simply try to delete the file again. It is possible that Veeam issues a delete command and the delete was successful, but Veeam didn't have the opportunity to record the successful delete.
If you have Lifecycle Rules setup to "Keep all versions of the file," files will only be removed when Veeam issues a delete command.
When you say one of the "errors" - I assume you mean "DeleteMultipleObjects request failed to delete object error: NoSuchVersion, message: 'Invalid version id specified'", correct? $symlink files, which can be chosen under "Masks & Filters" -> "General Filters".I did check the file path of one of the errors and the file did not exist in Backblaze. retention of symbolic links and junctions
#Does backblaze support folder backup zip#
Permissions on a file level can only be included when using zip or sz compression.
metadata-syncovery files, too, via the settings under Special -> Process Security and Shares, on the Advanced tab sheet. metadata-syncovery files, also via the button "Alternate Data Streams" on the tab sheet Special->More.įolder permissions (Security Settings) can be uploaded in.
#Does backblaze support folder backup archive#
This includes read-only, archive etc.Īlternate Data Streams for files can be stored when files are zipped or Sz-compressed, via the button "Alternate Data Streams" on the tab sheet Special->More.Īlternate Data Streams for folders can be stored in. Not the whole file.īut uploads cannot be resumed if the whole profile has been stopped and is later restarted.Ī file's dwFileAttributes are stored in compressed Sz files. If there are interruptions or errors during a large file upload, only the interrupted chunk needs to be re-uploaded. Many smaller files are uploaded in parallel, and large files can also use multiple threads to increase bandwidth usage. But it does not have to be re-uploaded when this is implemented. A file needs to be copied and then deleted. Will be implemented via B2's b2_copy_file function very soon.
0 kommentar(er)
