Jump to content

Problems checking appleshare volumes larger than 1 TB


Recommended Posts

Hi,

I'm using Retrospect since the old days of version 2, i guess (when you still could create a template with all the file info).

For the most part I still work on a os9 machine running Retrospect 4.3 doing backups of a appleschare volume that is around 1,1TB. I'm archiving folders from this volumes that has a size of about 40Gb.

Now I've upgrade to a osX 10.3.9 machine with Retrospect 5.1 and suddenly I can no longer assign the folder on that large volume as a volume! Why is this?

Somewhere I saw a 'readme'-file for Retrospect 6 stating that there was no longer a limitation on the volume size, so I downloaded a trial version, prior to ordering, received a trial license key from customer service that was already expired, but with a small workaround (I will not mention, but is not illegal), I could try to check the volume in the new version: again with the same result, could not view contents of large volume!

 

Can somebody confirm this problem, or give me some advice! I really need it urgently!

 

regards,

Link to comment
Share on other sites

Quote:

 

>I can no longer assign the folder on that large volume as a volume!

 

 

 

then

 

 

 

> again with the same result, could not view contents of large volume!

 

 

 

 

 

 

 


 

 

 

Are you unable to define the volume, or are you unable to view its contents?

 

 

 

- What exactly are you doing, and what exactly happens when you do it?

 

 

 

 

 

Dave

Link to comment
Share on other sites

I'm unable to do both.

 

When trying to define a subfolder as a subvolume in the volumes database I don't get a listing of the folders. I also have a another volume residing on the same server on which I can view and select subfolders.

 

After your mail I tried some other things i will try to describe:

In the volumes database I click subvolume... and this window I try to define a new folder on the selected volume. This doesn't work and gives me an error stating I don't have enough privileges. OK you will say but why can I then create, in the Finder, on that same volume folders and view it's content.

 

So there must be a difference in reading the privileges of a mounted volume between the Finder in osX 10.3.9 and reading them in Retrospect that causes this error.

 

Can you please confirm?

Link to comment
Share on other sites

Quote:

So there must be a difference in reading the privileges of a mounted volume between the Finder in osX 10.3.9 and reading them in Retrospect that causes this error

 


 

Indeed there is. And it's covered in the Retrospect User's Guide, and has been discussed here on the Forum for the last three years.

 

You need to have Retrospect mount the remote AFP volume; if you mount it via the Finder, Retrospect won't be able to view its contents.

 

It's a user ID conflict due to Retrospect running as UID 0 (root).

 

Dave

Link to comment
Share on other sites

OK, say I'm stupid :-?

 

How do you select a volume in the volumes database for the local desktop when it wasn't mounted at the time Retrospect is running? Tell me!

 

Second try, I mount the volume on the desktop as user x without a password. Now I see the volume in de volumes database in the local desktop, when I get info, it states user x, password is empty.

 

I'm doing this since 1992! OK the world has changed :-! but tell me why this works on all volumes except a very large (?) Helios Ethershare volume, that otherwise works as expected!

 

Next week I will take it up with my Helios-supplier to check the privileges of that particular server and maybe they can solve/view the problem. It doesn't seems you want to understand that the problem may lie with your product.

 

Regards,

Link to comment
Share on other sites

Quote:

It doesn't seems you want to understand that the problem may lie with your product.

 


 

Uh, it's not _my_ product!

 

This is a community support bulletin board, not Dantz technical support. And as a fellow Retrospect user, what _I_ don't understand (although I really do want to) is exactly what you're doing, and why you're blaming the program before you've done the research suggested in the thread.

 

Although your tenses are mixed ( wasn't mounted at the time Retrospect is running) the answer is still waiting for you in the Read Me file. Retrospect needs to mount the volume prior to executing the backup.

 

>I mount the volume on the desktop as user x without a password. Now I see the volume in the

>volumes database in the local desktop, when I get info, it states user x, password is empty

 

What is the "it" in "it states?"

 

The "Get Info" command of the Retrospect Volumes Database displays a window that does not contain user name or password fields (it contains Kind, Used, Free, Total, Where, Created, Modified and Backup information fields). So I'm back to not knowing what you're doing.

 

The menu you'll need to use is the Volumes menu; the selection you'll need to choose is Configure. Page 172 of the Retrospect User's Guide has specific instructions, and the Read Me puts those instructions in context of OS X. The reason for that context is contained in my first reply.

 

Dave

Link to comment
Share on other sites

Sorry Dave,

I thought you were 1 of the support guys!

I use Retrospect for really a long time now, as mentioned above since 1992, so I really know how to work with it on the mac. So I will again try to explain what I'm trying to do.

 

Step 1

In the Retrospect Directory I choose tab Configure -> Volumes.

 

In the 'Local Desktop'-item I don't see the volume I need (normal, because it's still not assigned to a script).

 

When I now go to the Volumes menu Configure is grayed out.

 

Step 2

I now go the the Finder and mount the Volume from our Helios Ethershare Volume with name x and no password. Double clicking it in the Finder shows me the content of the folder.

 

Now I go back to Retrospect's Volumes Database. The Volume has shown up in the 'Local desktop'. I select it and choose configure from the Volumes-menu. The window is now showing the correct user and an empty password (as you would expect, seeing the login sequence).

 

Step 3

In the Volumes Database I again select the Volume and click Subvolume... and now I get the window 'Defining a folder as a volume...' with an empty overview (no content) and of course all buttons grayed out, even the Use:-button on the right.

 

When I try to create a new folder on the volume by clicking 'New' in this window I get a dialog stating 'Can't create folder, error -5000 (server: no privileges).

 

So it can also see it has something to do with the privileges, but it's only happening from within Retrospect. Even when I mount the volume as administrator ( then I have all the privileges on this volume) I don't see the content of the volume from within Retrospect.

 

Other Volumes on different servers don't give a problem in Retrospect.

 

Now I've done a check on the privileges of the mounted volumes and the difference lies in the fact that the volume on which I have problems don't have guest access on. When I put this on, by changing the privilege from the sun-server on which the volume resides. I can view the contents.

It seems that Retrospect does not respect the user settings with which the volume was mounted but always needs full guest access.

 

OK Dave case closed, thank you for your help and motivation to keep searching to a solution.

But I still think that Retrospect is ... :-)

Link to comment
Share on other sites

Change Step 1 to: Read the ReadMe that comes with Retrospect; it will provide step by step instructions in how you have Retrospect mount the server.

 

Once you configure Retrospect with the password (I've never tried this with a remote volume that has no password), you unmount the server (since you mounted it as the Finder user, and if you have read the earlier posts you know that Retrospect will not be able to use a volume that was mounted by a different user). Then you have Retrospect mount the server, either by running a script, or by clicking either "Browse" or "Subvolume" in the Volumes Database.

 

When Retrospect can see the files, the Finder can't. No way around that.

 

Dave

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...