I need to back up a NAS share of 1.5tb. My TEMP directory (redirected to another, bigger, local drive from C:Win\Temp) drive will fill up before the backup is completed.
I set the .7z to split every 3 GB. As the Task runs, I see .7z.001, .7z.003, .7z.003, etc being created.
I was hoping that it would create a .7z and then copy it to the destination followed by deleting the just archived .7z. This appears to not be the case.
Is there a way to force this behavior (Build, copy, delete, repeat)?
If not, is there a way to have the archive created directly on its destination bypassing the copy stage?
Plan B: Break up the backup task into multiple smaller tasks, but I was hoping to avoid adding this backup management complexity.
Plan C: Any suggestions are welcome.
Thank you
I set the .7z to split every 3 GB. As the Task runs, I see .7z.001, .7z.003, .7z.003, etc being created.
I was hoping that it would create a .7z and then copy it to the destination followed by deleting the just archived .7z. This appears to not be the case.
Is there a way to force this behavior (Build, copy, delete, repeat)?
If not, is there a way to have the archive created directly on its destination bypassing the copy stage?
Plan B: Break up the backup task into multiple smaller tasks, but I was hoping to avoid adding this backup management complexity.
Plan C: Any suggestions are welcome.
Thank you
Statistics: Posted by therzog — 28 Feb 2023, 01:52