You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use oandbackup extensively with scheduling frequent backup. As soon as the backup are done, I upload these with Nextcloud automatically in Android.
The thing is the backup first start with uncompressed files (for data), so I have lots of random name file because it is detected by Nextcloud while oandbackup is still constructing the archive. This generated tons of failed upload in Nextcloud client because they are deleted quickly after the archive is done.
The solution is quite simple in theory: it would require to set in oandbackup a different temporary directory to do all these work and do an atomic move of the archive at the end :) The temporary directory can be a parameter, or it could be /tmp as long as the directory is purged each time the archive is done to avoid space issue.
Is-that possible? Thank you!
The text was updated successfully, but these errors were encountered:
Hi,
I use oandbackup extensively with scheduling frequent backup. As soon as the backup are done, I upload these with Nextcloud automatically in Android.
The thing is the backup first start with uncompressed files (for data), so I have lots of random name file because it is detected by Nextcloud while oandbackup is still constructing the archive. This generated tons of failed upload in Nextcloud client because they are deleted quickly after the archive is done.
The solution is quite simple in theory: it would require to set in oandbackup a different temporary directory to do all these work and do an atomic move of the archive at the end :) The temporary directory can be a parameter, or it could be /tmp as long as the directory is purged each time the archive is done to avoid space issue.
Is-that possible? Thank you!
The text was updated successfully, but these errors were encountered: