Jump to content
Sign in to follow this  
aussant

Drive Not Visible on Client

Recommended Posts

I'm trying to back up a Windows 2000 Server using v6.0.110 of the Retrospect client. This client is currently logged in as admin. The backup server is a Windows NT 4.0 machine running v6.0.206 of the Multi Server Edition, also logged in as admin.

 

 

 

The problem is one of the SCSI drives on the W2K server is not visible from the server. The retrospect client can't seem to identify the drive. The drive is mounted and visible from the W2K server's desktop.

 

 

 

Any suggestions?

 

Dan

Share this post


Link to post
Share on other sites

Go to Configure > Clients. Get Properties on this client and go to the Volumes tab - do you see the "missing" volume? If so, change the drop down box to: 'Selected volumes' and highlight all the volumes you want backed up in the bottom box.

 

 

 

If the drive is not seen on the volumes tab, uninstall the client, reboot the client computer, log in as Administrator and install a fresh copy of the latest client. These issues generally result from not being logged in as Administrator at the time of the actual installation.

Share this post


Link to post
Share on other sites

Uninstalled, rebooted, and reinstalled as suggested. SCSI drive still not visible.

 

 

 

Is there an issue with permissions on the drive? I'm assuming that should be moot since the backup is performed with administrator privileges.

Share this post


Link to post
Share on other sites

I found the problem. It was a permissions related problem.

 

 

 

Initially I had the permissions on the root level of the hard drive set to the local administrator account, and domain admins only. I didn't think this was a problem since I had used the local administrator account to install the client (running at administrator level nothing should be inaccessible).

 

 

 

Once I reset the root level of the hard drive to everyone, the drive is now visible.

 

 

 

Folders within the drive that have administrator access only can be accessed fine. Why is the root level of the drive so critical?

 

 

 

This is not documented in the User's Guide (or did I miss it).

 

 

 

Dan

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
Sign in to follow this  

×