cferri Posted August 1, 2009 Report Share Posted August 1, 2009 1) Self destruction of config files. Apart from occuring with the obvious, system crashes etc, this frequently occurs when Retrospect updates itself. There must be a better way to store and access the config data so it is kept safe. 2) Why is there a lower limit on the length of a file name than Windows allows? If a file name is valid in Windows, Retrospect should be able to back it up. 3) Why is Retrospect not capable of using the driver letter supplied by the OS to correctly identify USB media for scripts? Discs on the same port with the same drive letter are treated as different discs and require separate scripts before they can be used as a destination for duplication backups. This should not be necessary. 4) Why can the program not cope gracefully with multiple startup requests? Because of the problems associated with (3), I aqm forced to run jobs from a batch file which has to check which disc is mounted and run the appropriate run document. On some systems, when Retrospect is already running, issuing the run document as a command causes Retrospect to complain that it is already running, instead of adding the job into the queue. Quote Link to comment Share on other sites More sharing options...
blm14 Posted August 1, 2009 Report Share Posted August 1, 2009 To address 1: this is easy enough to correct. Have retrospect back up its own \documents and settings\all users\retrospect directory once a day to a set. Then if you get corruption all you need to is mount that one set, restore you config dir to a new location, close the two retrospect processes, and restore your config folder. Reboot retrospect and you're all set. Quote Link to comment Share on other sites More sharing options...
cferri Posted August 1, 2009 Author Report Share Posted August 1, 2009 I agree that you can work round this problem, but it should not be necessary. New users to Retrospect would not know this and would therefore not be prepared to deal with such a problem. This has been known about for years, yet nothing has been done to prevent it. It is just sloppy programming. Quote Link to comment Share on other sites More sharing options...
cferri Posted August 2, 2009 Author Report Share Posted August 2, 2009 5) Version 7.6 crashes with Microsoft C++ Runtime errors. I could find no information or help on this problem and have had to go back to 7.5 which does not have the same issue. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted August 7, 2009 Report Share Posted August 7, 2009 I've said it before and I'll say it again. When as a sysadmin you have worry about backing up and restoring the very application that is supposed to be protecting your data - you're on to a bad thing. Rich Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.