Jump to content

5.0 OSX release client turns itself off


Recommended Posts

Hi,

 

We have been running Retrospect 5.0 since last Friday and generally it is working very well, but on my iBook running 10.1.3 the Retrospect client seems to turn itself off just for fun.

 

 

 

I've been keeping an eye on it for the last few days and sometimes it will turn off during a backup, other times it turns off when its not running, but then is not seen by the server when my turn for backup comes round again.

 

 

 

I've managed to get it backed up but it's been a far from slient background operation.

 

 

 

Any help would be gratefully received.

 

 

 

Many thanks

 

 

 

Phil

Link to comment
Share on other sites

I regret to inform you that I don't have a solution but.....I am experiencing the same problem and actually have an open incident with Dantz. They are aware of others having this problem and do seem to be working hard to solve the problem. I know I have performed several tests and run some logs on the client. All my info has been sent to them and they are going to try to gleen some useful info from them. Hopefully a solution will be reached soon.

Link to comment
Share on other sites

Hello,

 

 

 

Try the following. Launch Retrospect. Edit your script and click on Options. Locate the option for Client Execution>Speed Threshold and click "use default". If you were not already at the "default" settings, try the backup again to see if this resolves the problem you are having

Link to comment
Share on other sites

I'm having a similar problem but it's with a fresh install of the Retrospect Client on a OS 10.1.4 machine. When I launch the client I can never switch it to ON. It just jumps back to the OFF position. Also, I can't select the preferences. When I hit the button or select preferences from the menu nothing happens.

Link to comment
Share on other sites

Re: OS X Client 5.0.528. Nate Walker, a Dantz Tech Support person, has emailed me and informed me that Dantz has reproduced the problem inhouse and is actively working on an update.

 

 

 

You need to *completely* remove the Preview client and then reinstall the shipping client.

 

 

 

Instructions for removal of the Preview client are at the end of this post.

 

 

 

bleslie, try some of the troubleshooting steps for the OS X client in the Knowledgebase:

 

 

 

http://www.dantz.com/index.php3?SCREEN=knowledgebase_article&id=806

 

 

 

If you ever had a previous version of the client (beta, preview) installed, be sure that all traces have been removed per the Readme file from that release.

 

 

 

Irena Solomon

 

Dantz Tech Support

 

 

 

To un-install the client, first move the folder "Dantz Beta" to the trash.

 

 

 

When installed, the Retrospect client creates the folder:

 

 

 

/Library/StartupItems/RetroClient

 

 

 

and puts the following two files inside:

 

 

 

RetroClient

 

StartupParamaters.plist

 

 

 

To remove them, you can drag the RetroClient folder to the trash, but you will not be able to empty them from the trash until after you restart your Macintosh.

 

 

 

To empty the trash without restarting you will need to manually quit the "pitond" process:

 

 

 

Step 1 - Open the Terminal application found in /Applications/Utilities/.

 

 

 

Users who are familiar with typing in the UNIX shell may choose to perform these actions as the 'root' user and omit the 'sudo' in each of the commands below.

 

 

 

Please enter Terminal commands carefully and accurately; there are no system warnings when removing files and folders through the command line interface.

 

 

 

Step 2 - Type:

 

 

 

sudo ps -cx | grep pitond

 

 

 

Enter your user password at the "password" prompt (you must be logged in as a user with administrator privileges).

 

 

 

If the Retrospect client process is running you will see something similar to this:

 

 

 

119 ?? Ss 0:03.63 pitond

 

 

 

The first field (119 in this example; your number will be different) is the process number. You will need to enter the process number in the next step.

 

 

 

Step 3 - Now kill the process by typing:

 

 

 

sudo kill [process number]

 

 

 

(Do not type the brackets around the process number)

 

 

 

Re-enter your administrator password if requested

 

 

 

Step 4 -The following files contain client state information. They do not need to be removed if you plan on either reinstalling the client or upgrading the client (note: the client password resides in the retroclient.state file). Should you wish to remove them, type the following commands:

 

 

 

sudo rm /var/log/retroclient.history

 

sudo rm /var/log/retroclient.log

 

sudo rm /var/root/Library/Preferences/retroclient.state

 

 

 

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...