philcebutv Posted July 18, 2009 Report Share Posted July 18, 2009 Hi we have a retrospect server 6.0 that is running fine under Intel Mac OS X server 10.5.7 for more than a month. Just this week all the duplicate scripts where unsuccessful due to retrospect server just quit when its scanning files and folders or while in the middle of copying files. I have search the forum on how to solve retrospect quitting or crashing and have found two tips/suggestions 1. Disable ACL copy when copying/duplicating 2. re-create Retro.config by deleting or dragging it to another location. However I have done this two tricks but still Retrospect Server Quits by itself and leaving the duplicate backup unsuccessful I have recently installed a REV drive device on the server running on FW but I do not think that would cause the quitting of Retro App (I maybe wrong here). Also after the installation of REV drive the Retrospect was able to succesfully perform a duplicate backup. The files are around 342,150 and 52,146 folders to be exact. Are these files and folders too many already? What number of files that Retrospect can handle? Anyone have ideas on how to solve this? I am stuck already and the worst thing is that we do not have complete backup as the duplicate will delete first the backup then performs the copy and sadly Retrospect quits in the middle while duplicating. I have not restarted the server yet and have not disconnected the REV drive but will do tomorrow if the server is free of users connecting. Help Please... 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.