Issues with connecting to a Macintosh Server

[dloscalzo]

I am currently attempting to back up data on an Intel Macintosh OS 10.4 Server from a Windows server.

When working from the media server (Windows 2003), I go to create a new backup job, expand the domain tree and locate the Mac server (which is a member of the domain).  I am able to expand the Mac Server and view the shares that are on it, but when I attempt to click the check box next to the shares, I receive a prompt to resubmit the authentication information (which I am sure I am typing correctly).  Regardless of how many times I correctly submit the login information, I am unable to connect to the server.

The remote agent for the Mac server is installed and was done without a problem.  No error messages were reported during the installation and everything was shown as being successful.  I am confused as to what can be causing  the problem, but was unable to contact technical support as this is a pre-sales problem.  We plan on purchasing the product if we can resolve this issue.

[doni_katz]

According to the admin guide, the OS X agent is supported only on PPC architecture. I don't know if this is actually true, though, as the Mac docs have many errors. Can you verify that the service is running:
SystemStarter [start|stop] VRTSrams ?

[dloscalzo]

I tried checking to see if the service was running and I don't believe that it is.  Using your command didn't return a result with either start or stop (using the verbose switch didn't change anything, either), but when I checked for the process via ps aux, there was nothing there.

I was able to confirm with Symantec that BackupExec does run on Intel Macs, which is a good thing, but getting pre-sales support on the product has been extremely difficult.  Symantec has told me that I need to contact the product specialists at our reseller who have sent me back to Symantec.  I'm stuck in the support loop at the moment.

I'm still looking at the issue on my own and attempting to find clues in the manual, but if there is anything else that you can think of, I would appreciate it.  Thank you for your response!

[Hywel_Mallett]

---

doni katz wrote:
According to the admin guide, the OS X agent is supported only on PPC architecture.

---

This is no longer the case. I think the support for Intel architecture may have come in with build 7170.

[doni_katz]

Indeed, you are correct, good to know. (Would be nice if they actually updated the admin guide to reflect this change as well as to fix all the other inaccuracies...)

As for the RAM problem, does the installation log show any errors? See the admin guide for log location. Even if the installation script echoes success at the end, the log may still contain errors. It's pretty ugly installation script, so you have to examine the log to see if it had trouble copying files or what-not (I found that mine originally had errors that I had to manually resolve). If there are errors, please post so we can advise. Thanks

[dloscalzo]

OK, I did find the following interesting lines from the install log:


VxIF::Info:: RALUS is not licensable. - Possibly because I'm using trialware?

VxIF::Info:: No /tmp volume on <servername> - This also occurred for /opt, /usr and /


There could be something else that I'm missing in the log file and I'll be happy to post the entire thing (it's a bit long though).

[doni_katz]

Those results are normal and expected; errors would be labeled as such. Okay...

The process to check for is beremote -- don't see that either?
When you say the SystemStarter command gives no result -- what do you mean exactly?
See anything interesting in your system.log?
Can you check to see if you have VRTSrams folder in /Library/StartupItems?

[dloscalzo]

I don't see beremote running, no.

When I run SystemStarter, nothing happens.  I'm just given another prompt to enter a command.  If I attempt to search for the started process, I can't find anything.

The system.log is nearly empty. 

The folder VTRSrams is in the StartupItems folder, but it's in the StartupItems folder of a drive other than the start-up disk.  Will this have an impact?

[doni_katz]

You're running the full command: "SystemStarter start VTRSrams" correct?

The VTRSrams folder must be in the StartupItems folder of the booting OS so that it can start the process on boot. If it installed into the incorrect OS (on a multi-boot system) that's a problem. Might need to uninstall and reinstall and confirm you are installing to the correct boot volume.

[dloscalzo]

I'm definitely running the full command.  If I replace 'VRTSrams' with complete gibberish, nothing happens there as well.  If I use spotlight to search for VRTSrams, it only finds a file in the StartupItems folder.

As far as being installed on the boot volume, it is.  I apologize for the confusion there.  I was looking at something incorrectly.

I also went through the process of uninstalling and reinstalling again, both of which went off without a hitch.  The log also looks the same as it did before.

As a side note, I've noticed that the only two things that are installed during the installation process are VRTSralus and VRTSvxmsa.

Message Edited by dloscalzo on 07-19-200712:11 PM

Message Edited by dloscalzo on 07-19-200712:13 PM

[dloscalzo]

Eureka!

I don't know how this actually made a difference, but I had a chance to apply updates and restart the server which has the software working now.  Thank you very much for all of your help.  It was greatly appreciated.