I don't think I'm going to solve this one in a hurry. The contents of the command line includes lots of garbage (to me) and the word 'panic' (truth!) features a number of times, adding to my discomfort. Retrospect successfully scans the contents of the server, but when it attempts to backup, I experience something rather strange.Ī UNIX command line 'debugger' begins printing over the top of my desktop where upon my system crashes. Is your setup similar, and did you have any issues initiating a Novell server backup?īy disconnecting from the server and then forcing a reconnect by instructing Retrospect to perform an immediate backup (where a login screen appears and I enter my Novell username and login). I am running Retrospect 6 and Novell 6 with Native File Access (meaning I connect to the server via TCP/IP and do not use the Novell client). I successfully login to the Novell server via TCP/IP (via the OS) although when trying to specify the Novell Server as the volume for the backup Retrospect tells me that it cannot be accessed. I'm having a problem where I can't specify the Novell server's files to backup because of what seems like a priviliges issue.
I was beginning to think I was the only one backing up a Novell server using Retrospect from OX10.1.5, at least, that's what I'm trying to do. 2 SUSE Linux Enterprise Server 11 SP1 Novell Open Enterprise Server 2 SP3.
Previously added this to pnord's thread (was technically changing the subject, started seperate thread) Mac OS X Network Proxy Settings in Terminal.