Author Topic: New backup (beta)  (Read 11914 times)

0 Members and 1 Guest are viewing this topic.

New backup (beta)
« on: November 12, 2019, 01:00:16 AM »
Using the "NEW backup (beta)" option seems nice.
except it is defiant on using First a local "tmp" (temporary) directory..
Then, "moving" to the 'path' you choose in the Settings.. which doesn't make good sense. imo.

for example;
I have a separate partition for my backups, so my main system is free from these..
During the CWP (new) backup, it uses my main systems Available Space.. which,
for good reason is usually not enough to hold the system AND a complete backup.

why i (and most) use a separate partition, or entire Disk..

this is a big oversight, imo.. this means that i need to have at Least Double the Available Space Available to do a complete backup.
I have entered already the better chosen path in the backup settings (a seperate partition, which HAS the space for this).. but alas,
The (NEW backup Beta) is using the systems local space as a "temp" first.. smh.

Makes not good sense.

i hope this gets addressed before it leaves 'beta'. :) 
It looks like a nice backup/restore system, but this kind of kills it.

Re: New backup (beta)
« Reply #1 on: November 13, 2019, 07:59:06 AM »
there is another problem
they do change file owner to user id
so after each backup you will get double User Quota
so if you got an account with 1 gb package and files were 800mb , after backup user quota will be 1600mb and it will stop uploading and changing or even opening user panel

oh by the way .. if you chose compressed backup .. you will get incremental backup also

Re: New backup (beta)
« Reply #2 on: November 13, 2019, 08:00:10 AM »
and there is another problem
restore is not working

Re: New backup (beta)
« Reply #3 on: November 13, 2019, 07:27:37 PM »
yes. i agree.. not working as it should..

i preferr manual tar or cp -Rap / for now, unfortunately..

good idea, but no. increment saves incorrectly, etc..

it really shold have been tested (even BEFORE releasing a "beta" version).


i wouldn't recommend using it at this time.