Search the Community
Showing results for tags 'empty'.
Found 2 results
-
I had a couple of old scripts where the source and destinations had been deleted. I tried to copy and modify one of them, to add source and destination to use it. What I saw was really odd. The number of available backups for restore ops should be large (50+?). I saw 7. I looked at other restore scripts, and they all seemed to show just the same 7 restore options. (2 screenshots attached) I then tried to delete the script. The "really delete" dialog came up, but the script would not go away. I tried several times. I restarted the console, and the backups reappeared, and the scripts could be deleted. Bug. Not sure if I could reproduce it.
-
retroclient.state is empty, reoccurring issue
roobieroo posted a topic in Retrospect 9 or higher for Macintosh
I keep having an issue with my clients which seems totally random and usually it's with a different client each time. For some reason, the retroclient.state file ends up completely empty so then Retrospect says that there is no password. I have to delete the empty retroclient.state, run the installer again and set the password. I know how to fix it but the problem is that each time this happens the client stops backing up until I notice it. Is anyone else seeing this? I'm not sure what triggers the empty retroclient.state file to begin with either I'm afraid. Each client that has had this issue so far is running 10.7.4 or 10.7.5 and Retrospect client 10.1.0(221). This is what I see in the retroclient log file. 1372123932: Client version is 10.1.0.221 1372123932: SopsLoad: no public key, return -1.! 1372123932: LogFlush: program exit(-1) called, flushing log file to disk
