steffi Posted February 15, 2008 Report Share Posted February 15, 2008 Are Volumes unique by name? I have a Source Group for volumes by name on one machine and another Source Group for volumes by name on another machine. Source Groups Everything Source Groups container Users on Drive A (local) Everything on Another Machine Source Groups container Users on Another Machine I have two backup scripts where one defines it's sources for local and another for the source group on Another Machine When I execute the script that uses Source Group "Everything" which should all be local ... it's trying to contact the "Another Machine" Doesn't make any sense. When I run my first Script I don't expect any clients to be involved only the local machine where Retrospect is running. The script shows Sources Everything Destinations Everything when it runs it's showing. Source Users on Another Machine Destination Everything Link to comment Share on other sites More sharing options...
CallMeDave Posted February 15, 2008 Report Share Posted February 15, 2008 Quote: Are Volumes unique by name? No; Retrospect does not consider names when tracking logical volumes or defined subvolumes. > I have a Source Group for volumes by name on one machine and another Source Group for > volumes by name on another machine. Sorry, I've read the post over a few times and cannot understand how you are describing your configuration. Perhaps you were trying to put some leading spaces in front of your list of items to indent stuff (which gets dropped when you submit the post)? Anyway, if you can try and describe things better, we can try and help more. Dave Link to comment Share on other sites More sharing options...
steffi Posted February 15, 2008 Author Report Share Posted February 15, 2008 So I have two scripts Daily Backup - Everything Macbook Backup - Everything on Macbook Everything source group is Users on Macintosh HD, Applications on Macintosh HD etc Everything source groups on Macbook is Users on Macbook, Applications on Macbook etc. (Macbook is a client) For some reason when I execute the Daily Backup Script it wants to see the Macbook client for me Everything as a source group should not contain anything that _isn't_ local to the machine running Retrospect. Link to comment Share on other sites More sharing options...
twickland Posted February 15, 2008 Report Share Posted February 15, 2008 Steffi: Given that you're naming your scripts, source groups, etc. with ordinary words, it would be helpful if you could put the names of these items in quotation marks so we can distinguish them from simple descriptions. I'll try to make sense of what you've written, though. It would appear that you have a source group that you call "Everything" that, perhaps counterintuitively, contains only volumes on the local computer. Then, you seem to have a source group you call "Everything on Macbook" (or perhaps it is called "Everything ," as might be suggested by a literal reading of your 5th line in post #106450 above) that contains a number of volumes on a Macbook client. You seem to indicate that you have a script called "Daily Backup" that has as a source only the source group called "Everything." If I've been following you correctly so far, it would seem either that you have several source groups with similar names that you are confusing in your script, or that you have inadvertently confused several similar volume names when you added them to your source groups. If I were you, I'd start by using some more-explicit nomenclature for your source groups. First, go to Configure> Volumes and rename your source groups in some meaningful way: say, "Local Computer" and "[username's] Macbook." Then, forget all volumes/subvolumes in each source group. Finally, carefully drag the desired volumes/subvolumes from the Local Desktop and Backup Clients groups to the appropriate Source Group. Hope this is helpful. Link to comment Share on other sites More sharing options...
CallMeDave Posted February 15, 2008 Report Share Posted February 15, 2008 Quote: If I were you, I'd start by using some more-explicit nomenclature for your source groups. First, go to Configure> Volumes and rename your source groups in some meaningful way: say, "Local Computer" and "[username's] Macbook." Then, forget all volumes/subvolumes in each source group. Finally, carefully drag the desired volumes/subvolumes from the Local Desktop and Backup Clients groups to the appropriate Source Group. +1 Dave Link to comment Share on other sites More sharing options...
steffi Posted February 15, 2008 Author Report Share Posted February 15, 2008 Thing is I don't believe that I can be mixing things up.... It shows in the "Everything on Macbook" source group clearly that the volumes are remote/client volumes and that world icon isn't present in the "Everything" ie. local source group. It's as if you cannot repeat the volume name b/w local and client and it's getting mixed up as to which one it should use. I'll try and rename things as you suggest and see what happens. Are things ie. volumes in Retrospect matched by name or are they given unique ids? If the later then as a programmer I would find it hard to believe it's doing what I see it's doing. Where it completely uses the wrong volumes in the wrong script. So I clearly show "Everything on Client" as being a remote volume "Everything on local" as being local ie. no world icons on the volumes in the group I've done what you suggested and renamed the scripts and recreating the source groups. I'm willing to be this won't help and it will still use the remote/client volumes for the local source group in the local machines script. Link to comment Share on other sites More sharing options...
rhwalker Posted February 15, 2008 Report Share Posted February 15, 2008 Steffi, if it doesn't work, I suggest that you post a screen shot of the backup client database (Configure > Clients) with all folder groups (if you have any) having their triangles opened, and also screen shots of each of your two scripts showing the sources (Automate > Scripts, double-click on the script so that the sources are shown). Maybe then it will be clear to us what you are doing and how you have things set up. If set up properly, it does work. Has been working for years here, ever since Retrospect 2.0 on ASIP. I will admit, though, it gets much easier to peruse the snapshots in each backup set if each disk on each network client has a different name that is somehow associated with the client's name, than if all of the disk drives on all clients and on the Retrospect server all have the same name. Russ Link to comment Share on other sites More sharing options...
CallMeDave Posted February 15, 2008 Report Share Posted February 15, 2008 > Are things ie. volumes in Retrospect matched by name or are they given unique ids? Retrospect tracks volumes via unique file ID (as assigned by the OS). It's still unclear exactly what you're seeing. My test: Create two new Source Groups: Local bin Client bin Define two subvolumes: /bin/ Retrospect Client Machine (boot volume "Foo HD") /bin/ Populate "Local bin" with the defined subvolume that lives locally at /bin/ Populate "Client bin" with the defined subvolume that lives remotely on the client machine's hard drive (Foo HD) at /bin/ Immediate->Backup Source: Local bin Destination: NewFileBackupSet Click on Files Chosen Click on any item in Browser window Select "Get Info" Note selected item shows as being located at /bin/ Close Immediate Backup Window Immediate->Backup Source: Client bin Destination: NewFileBackupSet Click on Files Chosen Click on any item in Browser window Select "Get Info" Note selected item shows as being located at Foo HD/bin/ Running the backup for using Local bin as the Source does not attempt to connect to any client. What happens when you try a similar test? Link to comment Share on other sites More sharing options...
steffi Posted February 15, 2008 Author Report Share Posted February 15, 2008 I can post my images but do I have to refer to them online? ie. there's no storage here for them right? Backup script for annie Backup script for audrey Running the Audrey script note how it's scanning Annie Volumes Link to comment Share on other sites More sharing options...
rhwalker Posted February 15, 2008 Report Share Posted February 15, 2008 Quote: I can post my images but do I have to refer to them online? ie. there's no storage here for them right? Sadly, you are right. But see Robin Mayoff's post in these forums, indicating a free place to upload them: http://tinyurl.com/yp5oco Russ Link to comment Share on other sites More sharing options...
CallMeDave Posted February 15, 2008 Report Share Posted February 15, 2008 What is the "Source Groups Container" that shows up within both Everything on annie and Everything on audrey? I'm gonna guess that this is the source of your problem. Dave Link to comment Share on other sites More sharing options...
steffi Posted February 15, 2008 Author Report Share Posted February 15, 2008 Doesn't that automatically get created whenever you create new configuration group? I just created a Test Group and under that it immediately creates a Source Groups container Yeah after I deleted that alias it no longer seems to scan the client's volumes like it did before. Link to comment Share on other sites More sharing options...
CallMeDave Posted February 15, 2008 Report Share Posted February 15, 2008 I think this is a bug. If nothing is selected in the Volumes Database list, and you select "Make Group" from the Volumes menu, then you get the naming dialog box and the resulting group is created with nothing inside. If the Source Groups container* is selected when "Make Group" is chosen from the Volumes menu then the resulting group will have a what appears to be a circular referencing Source Group item inside. If there's a reason for this, I can't think of what it is. *to be clear, there are three "containers" in the Volumes Database window. "Local Desktop" "Backup Clients" and Source Groups" Link to comment Share on other sites More sharing options...
rhwalker Posted February 15, 2008 Report Share Posted February 15, 2008 Ah, now I'm beginning to understand the issue. We do it differently here, and don't use "Source Groups". We have a "folder" (created by "Configure > Clients", Client menu, New folder) for each group of clients: Linux Clients, Mac OS 9 Clients, Mac OS X Clients, Wiindows XP Clients The client machines are placed into their appropriate folder, so that a script appropriate for that group of machines is used, with appropriate selectors for that group. And then set up each client's backup volumes separately. For our scripts, we add as sources the "Folders" for groups of clients. Never realized that the Volumes window had a "Source Groups" item at the bottom; don't know when that was added. Dave may be right. It may be a bug. Russ Link to comment Share on other sites More sharing options...
twickland Posted February 18, 2008 Report Share Posted February 18, 2008 Quote: I think this is a bug. If nothing is selected in the Volumes Database list, and you select "Make Group" from the Volumes menu, then you get the naming dialog box and the resulting group is created with nothing inside. If the Source Groups container is selected when "Make Group" is chosen from the Volumes menu then the resulting group will have a what appears to be a circular referencing Source Group item inside. If there's a reason for this, I can't think of what it is. I suppose that might be considered a bug under this particular test, but its purpose is to provide a shortcut when creating a source group. Anything you highlight beforehand will be included in the source group when you create it, so it saves a step; otherwise, you have to drag in the items manually. Of course, as you note, if the Source Groups container is included in, for example, the source group "Everything on annie," it means that everything in every other source group is also in "Everything on annie." Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.