- When doing a test with sftp, the test file is never deleted at the end of the test. Could someone confirm?
- If you cancel a backup task, the partial backup data set is not deleted or marked as "invalid" on the destination (I tested with sftp), and the history does not show anything at all. This could result in lots of partial backup data that you can't use if you cancel tasks frequently for some reason.
- I believe there should be a "cancel task" button to just cancel one of the tasks instead of the whole backup and all tasks.
- There needs to be a option if the destination is a windows network drive share as one of the "types". The reason is because it assumes the network drive uses the username/password as the logged in user. If they are different, this will cause the transfer to fail.
- When using archives, it seems to copy the data over to the temp directory first to build the archive. This causes several issues if the temp directory is on a different drive than the destination. Or if the temp directory is on the same drive as the source. Or if the destination and source drive are the same drive for some reason. The other assumption I think is that the temp directory is on a drive that is both large enough and/or fast enough to hold and build the archive. Because of all of these potential issues, I think it makes sense to allow the user to specify a different temp/archive build directory for each backup task so they can control where the archives are built instead of just one globally used temp directory. This would avoid wasting time/power/drive wear. If the user can control this, they could set the archive build directory to the same as the destination directory on the same drive if their setup allow for it, then a simple rename and move of the archive would be super fast.
Statistics: Posted by SleepySpider — 01 Jan 2023, 01:05 — Replies 1 — Views 45