Hi, Cobian,
I'm studying the Cobian Reflector to see if it serves my purposes.
I intend to make backups like “File History” type of windows 10, in which the first full backup is created and only increments of changed files are made in the following backups. In the case of a problem with the original disk or partition, where it needs to be replaced and all the data needs to be restored on the new disk, it's easy, just choose a date and have all the data restored. The application restores all existing files to the chosen date, those from the first backup that were never changed and all the others that were changed, in their latest version. The routine will fetch each file in its last version regardless of the date/version of the backup. It also lets you eliminate, for example, all versions of backups prior to a certain date, keeping the last updated version of each document.
From what I understand about Cobian, in the case of increments (and differentials in a way) it creates dated folders at each backup with only the files changed since the last backup. The result is a bunch of folders with different dates and changed files, some in some folders and others in others. If after “x” number of backups if we have the problem mentioned above and it is necessary to replace the original disk and restore all the data on the new disk, we have a jumble of folders, some empty others with some files changed and we don't know how we can restore all updated data.
The solution of always making full backups also doesn't make any sense when we have one or more Tb of data. We would be burning TBW from the backup disk unnecessarily. In this case it would be preferable to create a script with Robocopy and the /mir parameter. This way we keep all files up to date without duplication and without burning TBW.
Am I wrong in the way I understood Cobian to work? If so, please clarify for me, as I found the software structurally very well designed and I would like it to really serve my purposes.
Thanks.
I'm studying the Cobian Reflector to see if it serves my purposes.
I intend to make backups like “File History” type of windows 10, in which the first full backup is created and only increments of changed files are made in the following backups. In the case of a problem with the original disk or partition, where it needs to be replaced and all the data needs to be restored on the new disk, it's easy, just choose a date and have all the data restored. The application restores all existing files to the chosen date, those from the first backup that were never changed and all the others that were changed, in their latest version. The routine will fetch each file in its last version regardless of the date/version of the backup. It also lets you eliminate, for example, all versions of backups prior to a certain date, keeping the last updated version of each document.
From what I understand about Cobian, in the case of increments (and differentials in a way) it creates dated folders at each backup with only the files changed since the last backup. The result is a bunch of folders with different dates and changed files, some in some folders and others in others. If after “x” number of backups if we have the problem mentioned above and it is necessary to replace the original disk and restore all the data on the new disk, we have a jumble of folders, some empty others with some files changed and we don't know how we can restore all updated data.
The solution of always making full backups also doesn't make any sense when we have one or more Tb of data. We would be burning TBW from the backup disk unnecessarily. In this case it would be preferable to create a script with Robocopy and the /mir parameter. This way we keep all files up to date without duplication and without burning TBW.
Am I wrong in the way I understood Cobian to work? If so, please clarify for me, as I found the software structurally very well designed and I would like it to really serve my purposes.
Thanks.
Statistics: Posted by LUISSM — 20 Mar 2023, 04:31