CR v2.3.10
Windows 10
I've been using Gravity for my backups successfully for years, but recently decided to give Reflector a try. While I've got several items of feedback for development, this morning I ran into an issue that's different from Gravity, and makes Reflector unusable for my environment.
I use 7zip compression and split my backups into 100MB files. Some of my backups are of locations > 100GB, resulting in more than 1000 7z files.
Under Gravity, this isn't a problem. For instance, here's one recent backup directory. When Gravity needs more than 999 7z files, it handles it just fine. However, this morning I found my Reflector backup hung with following log error message. That's odd, I thought. Why is the program attempting to check the archive (and throwing an error because the archive is still locked) when the backup hasn't finished, so it's not ready for checking? When I checked the temp directory to be sure I hadn't filled up the disk, here's what I found. It looks like when Reflector filled 7z.999 and needed to create 7z.1000, it couldn't do it, but instead decided it was time to check the backup.
Please advise. In the meantime, I'm back to Gravity.
Thanks.
Windows 10
I've been using Gravity for my backups successfully for years, but recently decided to give Reflector a try. While I've got several items of feedback for development, this morning I ran into an issue that's different from Gravity, and makes Reflector unusable for my environment.
I use 7zip compression and split my backups into 100MB files. Some of my backups are of locations > 100GB, resulting in more than 1000 7z files.
Under Gravity, this isn't a problem. For instance, here's one recent backup directory. When Gravity needs more than 999 7z files, it handles it just fine. However, this morning I found my Reflector backup hung with following log error message. That's odd, I thought. Why is the program attempting to check the archive (and throwing an error because the archive is still locked) when the backup hasn't finished, so it's not ready for checking? When I checked the temp directory to be sure I hadn't filled up the disk, here's what I found. It looks like when Reflector filled 7z.999 and needed to create 7z.1000, it couldn't do it, but instead decided it was time to check the backup.
Please advise. In the meantime, I'm back to Gravity.
Thanks.
Statistics: Posted by AreteOne — 24 Apr 2023, 13:50 — Replies 3 — Views 29