Data Recovery and Disk Utilities Forum @R-TT

Hi,
Apparently build 7003 fixes all this. Great, Thanks !
.merle1.

We've been able to reproduce the problem and are fixing it.

We're investigating this problem.

PS : when creating a task, same result. It creates a full backup with an incremented file name (a3.rdr is a2.rdr was the last incremental image).

[quote=Alt post_id=17683 time=1646672997 user_id=59]
Do you run the script and GUI version under the same account?
I guess that the script doesn't see the already existing image and creates a new file. Is that possible?
[/quote]

Yes, same account

No, the script does see the existing files because it respects the naming convention, if the full image is a.rdr, then the first differential (made from the GUI) is a2.rdr. When I use the script (or the GUI), the new file is named a3.rdr, so it does see the existing backup. The only differences are that when run from the GUI or from the script, the time required to build a3.rdr it short from the GUI and long from the script and the size of a3.rdr too (big from the script, small from the GUI)

Sincerely,
.merle1.

[quote=MerleOne post_id=17679 time=1646346930 user_id=266]

Say the destination is D:\Backup\MyFileBackup.rdr, each time I run the same backup from the GUI with the same destination of course, a new .rdr file is created, named MyFileBackup[n].rdr where n=1, 2, ... etc.

If I reuse the script created as described, if the last version is MyFileBackup7.rdr, then MyFileBackup8 is created but this time its size is almost the same as the first full backup. And it take also the same time as for a full image creation.
[/quote]

Do you run the script and GUI version under the same account?
I guess that the script doesn't see the already existing image and creates a new file. Is that possible?

[quote=Alt post_id=17677 time=1646325416 user_id=59]
Did you try to create [url=https://www.drive-image.com/DriveImage_Help/createatask.htm]a task[/url] that can be run manually from the GUI?
Did you create the script manually or from the GUI? [url=https://www.drive-image.com/DriveImage_Help/creatingascriptfromr-drive.htm] Create a Script from R-Drive Image[/url].
Does the script create images at the same place when run from the GUI and the command line?
[/quote]
Hi,

Here is what I did/did not :
- I created no task
- I went into the GUI, defined what I wanted to save and where, then, before starting the backup, I saved the script. Which is supposed to be the equivalent of what I just defined. Then, if I run r-drive 7 from the GUI, it does perform an incremental backup, at least I think so since the size is small and it is rather quick, much quicker than for the first and full backup.

Say the destination is D:\Backup\MyFileBackup.rdr, each time I run the same backup from the GUI with the same destination of course, a new .rdr file is created, named MyFileBackup[n].rdr where n=1, 2, ... etc.

If I reuse the script created as described, if the last version is MyFileBackup7.rdr, then MyFileBackup8 is created but this time its size is almost the same as the first full backup. And it take also the same time as for a full image creation.

Not easy to explain but to sum it up, the same backup definition behaves differently when run from the GUI or from a script generated by the very same GUI.

Sincerely

[quote=MerleOne post_id=17674 time=1646172620 user_id=266]
Hi,
Here it is. When I run it from the GUI, which is cumbersome because I have to select again each folder, set the compression speed, select the full image, etc., it works fine (it is rather quick and the newly created image is a few hundred of MB big. If I run the script, which should lead to the same result, the newly created image is as big as the first image, a few GB. And it takes much more time.
[/quote]
Did you try to create [url=https://www.drive-image.com/DriveImage_Help/createatask.htm]a task[/url] that can be run manually from the GUI?
Did you create the script manually or from the GUI? [url=https://www.drive-image.com/DriveImage_Help/creatingascriptfromr-drive.htm] Create a Script from R-Drive Image[/url].
Does the script create images at the same place when run from the GUI and the command line?

Hi,
Here it is. When I run it from the GUI, which is cumbersome because I have to select again each folder, set the compression speed, select the full image, etc., it works fine (it is rather quick and the newly created image is a few hundred of MB big. If I run the script, which should lead to the same result, the newly created image is as big as the first image, a few GB. And it takes much more time.
Sincerely,
.merle1.

[ REM R-DriveImage script file ]

append /a /o -filelist=""C:\Users\jfdre\AppData\Local\eM Client","C:\Users\jfdre\AppData\Roaming\eM Client","D:\Users\JF\eM Client","D:\Users\JF\eM Client v6"" -bf -backupdir="C:\" -filelist=""C:\Users\jfdre\AppData\Local\eM Client","C:\Users\jfdre\AppData\Roaming\eM Client","D:\Users\JF\eM Client","D:\Users\JF\eM Client v6"" -bf -backupdir="D:\" -a="J:\Backup\Y700\eMClient\eMClient_files_20220205sai.rdr" -p="password" -c=4 -u -check -s-xr

We're unable to reproduce these problems. Can you send us the script to review?