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...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.