I have been using Cobian Gravity 11 for backups for a long time.
I used to Cobian Gravity11, but recently decided to switch Cobian Reflector.
What I noticed is that Reflector eats up all the space on the C: drive.
I can't do anything about it, I searched among the settings and didn't find anything.
I checked the settings of the old and new versions - they seem to be completely the same.
But the Cobian Gravity 11 does not create temporary files on the C: drive.
I tried to backup a 200Gb directory from drive D to drive E.
I make a backup using 7-zip without compression.
But in the process of creating a backup, the space on the C drive is over.
In the previous version of the program, this behavior was not noticed, the size of the C drive does not change during backup process when using Cobian Gravity 11.
It seems that Cobian Reflector 2.3.7 first creates a backup on drive C and then copies it to its destination.
With Cobian Gravity 11, a backup is created immediately at the destination.
Please tell me what is the problem.
What am I doing wrong or missing?
Thank you all in advance.
---------
UPD:
Let me share my observations with you.
My backup scenario is 4 directories with different file types like text, photo video, totaling 205 gigabytes.
I'm using 7-zip with zero compression, incremental backup.
To be able to easily restore with the built-in tool. (for this, you just need to select all backups, full and incremental in the unpacker.)
For example, if you do this without an archiver, then the backup will not be restored in a similar way, the tool cannot restore an incremental backup that was made without an archiver.
Also in this case, the backup will create a bunch of directories, which creates a mess, and it's not possible to easily restore it.
If you use 7-zip and zero compression, then the output of an incremental backup with each iteration is only one file.
In the new version, this is called "monolithic archive". (Perhaps the translation is different because I use a non-English interface)
As a result, I have a normal structure, only one file per day and the ability to restore in one click.
I made a backup comparison (of my backup scenario), old and new version of the program.
As a result:
Cobian Gravity 11
1) Creating a full backup takes approximately 1 hour.
2) Backup is created immediately at the destination.
Cobian Reflector 2.3.7
1) To create a backup, you need twice as much space.
Since the backup is first created in a temporary directory, it is then copied to the destination.
Not always on the disk there is such an amount of space.
In my case, for a backup of 200GB, I need at least 400GB free. (I didn't have much)
2) Creating a backup took twice as long, about 2 hours.
Since the archive was created in a temporary directory for one hour, on the same disk where the backup should have been located. (I checked, the temporary directory took up 200GB)
And then these 200GB were again copied from this disk to the same disk, after which the temporary directory was cleared.
This is a very strange algorithm, isn't it? At least for this scenario.
3) This behavior will also lead to hardware wear.
For example, if I had enough space, every time my SSD system disk would be written and deleted 200GB (just temporary files).
For now I will use the old version of the program.
Perhaps this algorithm needs to be revised, or at least for such a scenario, if monolithic archive is used with zero compression, then do not use intermediate temporary storage, but write the file immediately along the destination path (like it was in Cobian Gravity 11).
I hope that my observation and comments will help Cobian Backup to become better.
I used to Cobian Gravity11, but recently decided to switch Cobian Reflector.
What I noticed is that Reflector eats up all the space on the C: drive.
I can't do anything about it, I searched among the settings and didn't find anything.
I checked the settings of the old and new versions - they seem to be completely the same.
But the Cobian Gravity 11 does not create temporary files on the C: drive.
I tried to backup a 200Gb directory from drive D to drive E.
I make a backup using 7-zip without compression.
But in the process of creating a backup, the space on the C drive is over.
In the previous version of the program, this behavior was not noticed, the size of the C drive does not change during backup process when using Cobian Gravity 11.
It seems that Cobian Reflector 2.3.7 first creates a backup on drive C and then copies it to its destination.
With Cobian Gravity 11, a backup is created immediately at the destination.
Please tell me what is the problem.
What am I doing wrong or missing?
Thank you all in advance.
---------
UPD:
Let me share my observations with you.
My backup scenario is 4 directories with different file types like text, photo video, totaling 205 gigabytes.
I'm using 7-zip with zero compression, incremental backup.
To be able to easily restore with the built-in tool. (for this, you just need to select all backups, full and incremental in the unpacker.)
For example, if you do this without an archiver, then the backup will not be restored in a similar way, the tool cannot restore an incremental backup that was made without an archiver.
Also in this case, the backup will create a bunch of directories, which creates a mess, and it's not possible to easily restore it.
If you use 7-zip and zero compression, then the output of an incremental backup with each iteration is only one file.
In the new version, this is called "monolithic archive". (Perhaps the translation is different because I use a non-English interface)
As a result, I have a normal structure, only one file per day and the ability to restore in one click.
I made a backup comparison (of my backup scenario), old and new version of the program.
As a result:
Cobian Gravity 11
1) Creating a full backup takes approximately 1 hour.
2) Backup is created immediately at the destination.
Cobian Reflector 2.3.7
1) To create a backup, you need twice as much space.
Since the backup is first created in a temporary directory, it is then copied to the destination.
Not always on the disk there is such an amount of space.
In my case, for a backup of 200GB, I need at least 400GB free. (I didn't have much)
2) Creating a backup took twice as long, about 2 hours.
Since the archive was created in a temporary directory for one hour, on the same disk where the backup should have been located. (I checked, the temporary directory took up 200GB)
And then these 200GB were again copied from this disk to the same disk, after which the temporary directory was cleared.
This is a very strange algorithm, isn't it? At least for this scenario.
3) This behavior will also lead to hardware wear.
For example, if I had enough space, every time my SSD system disk would be written and deleted 200GB (just temporary files).
For now I will use the old version of the program.
Perhaps this algorithm needs to be revised, or at least for such a scenario, if monolithic archive is used with zero compression, then do not use intermediate temporary storage, but write the file immediately along the destination path (like it was in Cobian Gravity 11).
I hope that my observation and comments will help Cobian Backup to become better.
Statistics: Posted by subetov — 19 Feb 2023, 15:29