A co-worker and I have been pulling our hair out trying to get Arcserve 7 to work on two NetWare 6 servers, one acting as the host and another as the remote. There is only one tree. Arcserve is only loaded on one server (the host) and a NetWare agent for arcserve is loaded on the other (the remote.
We have all of the latest Arcserve builds and patches as of 02/04/03. Another odd thing is that after applying the latest build to the manager and the server, the manager still shows it is patched with the old build (218). We also have the latest and greatest NetWare TSAs patched. We've also done a registry hack suggested by tech support to fix the job queue error (30). When trying to submit back-up jobs to the queue we have to enter in the user name three different ways
1) user.context
2) user
3) cn=user.o=context
From the manager on the workstation we're able to backup files on the Host server, but when attempting to backup remotely we get the job queue error (30). It appears the registry hack was only for the host server, but not the remote that has the agent installed. The agent is patched with the latest and greatest 02/04/03.
From the server console we can successfully back-up both the remote and the host. It seems that the problem is with the manager.
What is strange is that we can drill down in the Arcserve application and see all of the servers and data in the manager on the workstation, but not without having to enter the user name three different ways (go figure) we are suspicious that the issue is security-username-context related, or that arcserve is full of bugs. Any suggestions?