Jump to content

Recommended Posts

I'm getting a heap of errors like the following:

 

19.05.2012 00:06:57: Connected to Vertrieb

* Resolved container Vertrieb to 1 volumes:

Macintosh HD on Vertrieb

Can't access volume Macintosh HD on Vertrieb, error -1101 ( file/directory not found)

 

Everything is running on OS X 10.6.x

 

What exactly is (or is not happening) here and what can I do about it?

 

I'd be very grateful for any help or ideas

Share this post


Link to post
Share on other sites

It applies to about 8 out 10 clients. Each has one source volume selected.

OK, is it still the same (identical) source volume? Or has it been renamed? Or has it been replaced or reformatted and just happens to have the same name?

Share this post


Link to post
Share on other sites

OK, is it still the same (identical) source volume? Or has it been renamed? Or has it been replaced or reformatted and just happens to have the same name?

 

It's the same volume.

 

The Retrospect installation is only a week old. It's the first time in over a year that Retrospect has known anything about any of the volumes. The backup ran once and then I started getting bombarded with error -1101.

Share this post


Link to post
Share on other sites

Strange.

 

I would try to forget the client(s) and add them again.

 

Yesterday afternoon I refreshed all the volumes, and forgot and re-added one client. The proactive script ran all night, and from 11 clients, 1 was backed up, (not the one that was forgotten). Retrospect spent the night logging error -1101 for the other 10 clients.

 

Today I will systematically forget all clients. But I'm not confident it will help, as I've more or less already tried that.

 

I'll let you know.

Share this post


Link to post
Share on other sites

As a last desperate act I did the following:

 

1. remove all client sources and relevant scripts from Retrospect and stop the engine.

2. Uninstall all clients and restart the machines

3. restart the engine

3. Install the latest version of the client and prepare for first access

4. add all clients individually

5. make a new script

 

Having done that, everything has been running smoothly for a couple of days now.

Share this post


Link to post
Share on other sites

Having done that, everything has been running smoothly for a couple of days now.

 

Well, I spoke too soon. As of last night it's back to square one. error -1101 on all clients.

 

This time I'm inclined to just give up on Retrospect (again!) and get my money back.

Share this post


Link to post
Share on other sites

isn`t that the "sitting at the logging window issue"?

in any case, i have a few of this 1101 errors on a few machines as well, they always sit at the loging window and the issue can be solved by restarting the computers via remote desktop or ssh or by walking to the computer

Share this post


Link to post
Share on other sites

Also make sure not to put the hard drives to sleep as I have found the Wake on LAN feature to not work correctly.

 

It doesn't work at all.

 

I'm in the process of looking into this error.

 

The thread has been helpful, thanks!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×