PDA

View Full Version : Drive Backup Pro 8.51 - 8 issues


kazmax
20-10-07, 08:22 PM
I purchased Drive Backup Pro 8.51 last weekend. Since then I have discovered 8 separate issues. I have already mentioned a couple of these in other threads, however I have just spent a couple of hours confirming all of the following and wish to bring these to the attention of the folks at Paragon so that they can be looked into.

I am using Drive Backup Pro 8.51 on a Windows XP Pro 64 bit PC.

1) Cyclic backup: Regardless of the choice of drives, the 'Next' button stays permanently disabled on the 'What to back up' screen. It is impossible for me to do cyclic backups as a result.

2) On the initial cyclic backup screen it is only possible to select one drive. Selecting any other drive causes the previously selected drive to be deselected. This is not very good when wanting to backup more than one drive (I can't use cyclic backups anyway because of the above, but if I could then being able to select only one drive feels like a backward step).

3) Right-click any scheduled job. Select Properties. Clicking 'OK' or 'Apply' causes an error popup - 'Error saving the contents of the page(s)'. It actually saves the detail because if you re-edit that job after clicking 'Cancel' then the previously entered data is what you wanted to save, but it presents this popup to annoy you.

4) Scheduled tasks - it is not possible to re-edit a task using the forms interface, you can only use a notepad editor. This isn't intuitive for a non-technical user.

5) Backup - choose destination - if folder name already exists you get an error message and cannot continue until you choose another new backup name. What's wrong with overwriting an existing backup if that's what you want to do?

6) Edit any *.PWL file. Within this file is a comment which relates to merging archives into one file - 'This function is not implemented yet: Merge archives into one archive'. What's the point of drawing attention to functionality which hasn't been implemented yet?

7) Add any script to the lower script pane of the schedule window. Highlight that script. Right-click and choose 'Schedule script', or click the 'Schedule Script' button. You get a popup advising 'Cannot schedule script ... because it already exists in Scripts'. I'm very confused - what's the point of the script pane if you can't ever schedule the script???? The real purpose of this script pane appears to be for script exclusion - place a script here so that you can never schedule it!

8) I don't understand the need for the 'Cyclic' backup option. I can schedule a job - if I happen to choose the same filename and location as a previous backup job, and don't check the 'Create random filename' option, why isn't Drive Backup Pro intelligent enough to figure that it's okay for it to overwrite a previous backup? Paragon seem to have gone to great lengths to confuse the user by offering straight backups and cyclic backups as two different options (and the fact that I can't actually use Cyclic backup is more than a bit frustrating).

I'm not listing this as an issue because it works as expected, but I've given up on scheduling backup jobs using the internal scheduler. I now use an external software utility to manage my scheduled backups, because at least I feel I have proper control over the backup job. With that external utility I have the ability to automatically delete the previously created backup files before Drive Backup Pro figures that it can't do the backup because the file/directory already exists. It's a pain in the butt having to do this, but at least I've overcome the problem.

Overall I'm feeling a bit disappointed that Drive Backup Pro 8.51 has so many apparent issues. I expect 1 or 2 issues in a new product - but 8 issues which could easily have been discovered with proper testing leaves a lot to be desired. It's a pity because I really like the new user interface and this product appears to be what I need. Because of these discovered issues I'm left wondering whether Drive Backup Pro has other potential issues which I haven't yet found, and whether I can rely upon it - I don't want to find that it cannot restore my hard disk if I experience a future catastrophe.

Andrew

ams
21-10-07, 09:54 PM
Hi Andrew,

I can comment point 8 about Cyclic Backup because I am using it in active way. This is the best procedure I ever used. It controls the size used for backup images. Just imagine that you have special partition, say E: specially created to keep backup archives in. But it is only 40Gb and your backup images are 10GB each. There is a need to keep backup images up to date and still have one image created originally when OS was just installed. You see, when you create 4 images the E: drive will become full and no more image could be stored there. Here Cyclic Backup helps you.
You can manage the size set for backup images and when the folder for backups exceeds the size set for images the second image will be erased automatically and replaced by new one. First one is left untouched, agree that this is a best advantage when you don't need to keep your eye on the space limit.

mla
31-10-07, 06:41 AM
Hi,
if you have a possibility to restore to SATA drive try it.
I tested restore IBM server 2003 to IBM Intellistation (inferior model)
Worked fine. The same image to Higher end IBM server with SAS/SATA controller didn't work. The external USB drive with the image is shown in simple restore but there is no destination drive (local SATA).
Unfortunately I cannot find any option to load SATA driver(like in Windows F6)

Let me know if you can test it with SATA destination.

thx.

ams
31-10-07, 05:09 PM
Sure your SATA controller driver is missing in Linux kernel on which the Recovery CD is built. Bart PE with adding necessary drivers during its creation is the right solution for you.