Jump to content

twickland

Members
  • Posts

    1,684
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by twickland

  1. In my situation, the multicast list often does not populate at all until I quit and relaunch the Console. Furthermore, clients that previously were added to the Sources list cannot be accessed until they do appear in the multicast list.
  2. It sounds like that may well be what happened. If so, that doesn't bode well, as I had only logged into Retrospect twice, for less than 2 hours total, and only worked on source configurations--no scripts or rules, to say nothing of no backups as yet.
  3. Well, after many happy (and other) years with Retrospect 1.3 through 6.1, I finally got the courage to try Retrospect 8. First impression: not so good. This is a clean install of Retrospect 8.2 (399) on a brand-new 3.2 GHz quad-core Mac Pro w/6 GB RAM, running 10.6.4. Engine and console are on the same machine. I installed Retrospect end of the day Friday. Just for fun, I added one client and then shut down the computer. Today, I began the slow (compared to 6.1) process of adding back the rest of the clients, defining subvolumes (oops, "Favorite Folders"), and assigning tags. About an hour and a half into the process, I highlighted a Windows client volume in the sources list and clicked "Add Favorite." After a brief period of trying to access the source, the Favorites window closed. I assumed this meant the client was now offline, and so I moved on to the next client, also a Windows machine. This time, the window populated with that client volume's root directory but, as I looked closer, there were two C: drives listed: one for the client volume I was currently accessing, and one for the client I has previously been trying to access. I thought, "Hmm, interesting bug; gotta report that," highlighted and added the correct Favorite Folder, and moved on. Things then seemed to be going well for the few minutes, until I got the "Disconnected" screen, indicating that the engine had crashed. I restarted the engine, but when the console reconnected, all the clients, favorites, and tags I had added this morning were gone from the Sources window. I was back where I had been at the end of the day Friday. Has anybody else seen this? More to the point, how often does data get written to Config80.dat? (I'm assuming that this is where the data on sources, etc., are stored.) Is there any way to force a save so I don't lose everything if/when the engine next crashes? Thanks.
  4. OK. You say you followed all of Russ Walker's suggestions above, to no avail. When you tried suggestion #2, could you please confirm that Retrospect asked you to enter your license code? Also please tell us more about your system hardware, installed Retrospect version, and installed RDU.
  5. Meaning that you are running Retrospect 6.x? If so and if is also true, that's your problem. Retrospect 6.x is not qualified to run under Snow Leopard.
  6. Run the catalog rebuild up to the point of failure, or at least until a few files have been read from tape 6. Stop and save the partial catalog. Then perform an "update existing catalog" operation. Retrospect will ask for tape 6; click on "Choices..." and tell Retrospect that member #6 is missing. Insert tape 7 and you should be on your way.
  7. If you did this just by dragging the client app to the trash, try using the Client Installer to uninstall the client first. (The installer options are "Easy Install" and "Uninstall.") In your case, use the installer for the 6.3 client to uninstall any remaining components from that installation. This may also uninstall everything from the 6.1 client as well, but to be safe, you might want to run another uninstall using the 6.1 installer. Doing this, you should be able to safely reinstall the 6.1 client, after which you should be all set.
  8. We followed your route through DAT 72; then moved to LTO, which we've been very happy with. Drives are more expensive than DDS, but the media is cheaper per GB.
  9. I'm not sure that the Mac client version 6.3.x will work with Retrospect 7.6.x for Windows. The client version that was last distributed for that Windows version was 6.2.234, available here. If downgrading the client doesn't help, you should repost your issue in the Windows section of the Forum, since that's what you're running on your backup computer.
  10. Your post would seem to imply you are archiving to a new backup set; is that correct? Have you ever been able to perform this archiving operation successfully in the past? What happens if you define a subvolume on the source volume and use this subvolume as a source for archiving? While you are at it, perhaps you could give us more info about your setup, including OS version, exact Retrospect version and any installed RDUs, what kind of tape drive, how it's connected to the backup computer, and exactly where the backup set catalog is being stored.
  11. I think speculating here is useless without more input from Anthony. The information about whether a media member is missing or not is included in the backup set's catalog. A recycle backup resets the catalog, so the status of a media member becomes largely irrelevant. However, to avoid having to continually OK the "wrong" media members during the recycle backup, it's best to insert a blank tape in place of the missing member when that missing member's place in the backup sequence arrives.
  12. Yep, that's entirely possible. While it is possible for you to do either of the above, it cannot occur without operator intervention. If neither the correctly named/numbered tape member nor a blank tape is available during a recycle backup, Retrospect stops the backup and puts up a window asking for help. To continue with the wrong tape, the operator would manually have to select the tape in that window and tell Retrospect that that is the tape to use. If you haven't selected "Minimal erase confirmation" in the Preferences, Retrospect will actually ask you twice. A blank tape is as good as the correctly named/numbered tape member when performing a recycle backup.
  13. Daniels, have you ever observed such a tape number change? I doubt it, because your discussion of working with tapes bears no resemblance to how Retrospect actually behaves with tape backup sets. Go back and reread my description of the two different numbering schemes that Retrospect uses to number tape members and to number subsequent backup sets in those cases where a new media backup has been performed. That's how Retrospect works. The only time that Retrospect will erase data without the operator issuing a manual command to do so is during a recycle backup. Even then, Retrospect is picky. If a tape already has data on it, it has to be the correct tape member of the correct backup set. In other words, Retrospect will only reuse tapes with data on them from the backup set being recycled, and will only accept the tape members in the proper order (1-Backup Set A, 2-Backup Set A, etc.). Retrospect will accept blank or erased tapes anytime it wants to create a new backup set member. This would be the only circumstance I know of where the tape member numbering could "change." However, before this could happen, the operator would have needed to erase the tape manually. In this case, it would be the manual erase that changed the tape numbering, and not some action by Retrospect. (When a tape has been erased, Retrospect no longer cares what name the operator may have given the tape during the erase process.)
  14. Your comment doesn't make sense to me, but does raise a potential issue. IGNPRINT/Anthony did not use the standard nomenclature for backup sets/members and I jumped to conclusions about what he meant. Let me back up a bit. When a tape backup set is created (for example, "Backup Set A"), the first member (i.e., physical tape) is named "1-Backup Set A." If other tape members are appended to the backup set, the subsequent members are named "2-Backup Set A," "3-Backup Set A," etc. If the user later performs a New Media backup, Retrospect will generate a new backup set. In my example, the first new backup set will be named "Backup Set A [001]," with the first backup set member being named "1-Backup Set A [001]." However, the old tapes are not reused by Retrospect, and the old backup set catalog is not reset; the old data remains intact. That is in fact the whole purpose of performing a new media backup. On the other hand, if the user performs a Recycle backup, the backup set catalog is reset and Retrospect will reuse the old tapes. However, in this case the backup set name remains the same (in my example, it will still be named "Backup Set A"); there will be no increment to any number at the tail of the backup set's name as you seem to suggest in your comment, Daniels. At this point, it's not clear what Anthony (or someone else at his firm) did, nor what type of a backup structure they have in place. I think we'll need to hear from him with some more details if we're to be of help.
  15. As you note, the asterisk indicates that the files in question are on a tape member that has been marked "missing." Whether you are able to eventually retrieve the files depends on whether the tape is truly missing; if it is, you are out of luck. To check on the status of your tape members, go to Configure> Backup Sets> Configure [your_backup_set]> Members. If any tapes are marked "missing" when you still have them in your possession, you can change their status in this window. Retrospect will not change the name of a tape on its own. In addition to when a tape member becomes full, Retrospect will ask for a new member if the previous member cannot be written to for any reason. However, unless you have an autoloader with an available blank tape, somebody will need to manually respond to Retrospect's request. Note that Retrospect will always want to move on to a new blank tape. Unless someone has subsequently chosen to erase the tape, has thrown it away, or the tape itself is too damaged to read, you should always have your old data. You may have the log size limit set too small. However, unless you changed the size, the default limit of 10MB should allow well over 100,000 lines in the log. Bizarrely, though, the Retrospect app will not be able to display all the lines in this default limit. The "solution" is to first close Retrospect and then open the operations log in an application that can read text files. Unfortunately, that method will make visual hash of the special Retrospect symbols in the log, but you should still be able to make sense out of the rest.
  16. Something is different about those files, causing Retrospect to want to copy them again. I suspect file metadata such as ACLs. Try this: In your script, go to Options> Matching and uncheck the option to use the attribute modification date when matching; see if this solves your issue.
  17. The reason you see this anomaly is that Retrospect does not regularly update the client status in the Backup Clients on Network window. In my experience, if a client was ever responding at some point, it will always annoyingly show as "Responding" in this window until the Retrospect app is relaunched. The status window that pops up when you attempt to access the client is the one you should believe. The first thing to check when you get the "client not installed/not running" error is the status of the client app. You will need to do this at the client computer itself. People have reported instances where the client software does spontaneously turn itself off. You can search this forum for that issue if it turns out to be the problem in your case; however, I'd be inclined simply to uninstall the client software (using the client installer and not by dragging the client app to the trash) and then reinstall it to see if that provides a fix. If, on the other hand, you find that the client is running, I'd suspect that the IP address lease may have expired between the time that Retrospect first connected and the time you got the error message. If the router then reassigned the address where Retrospect was expecting to find your client to some other computer not running Retrospect client, you would get a 541 error. RDU = Retrospect Driver Update. It's always best to have the latest one installed, as it includes bug fixes as well as offering access to newer devices. The RDU version will appear in the log whenever Retrospect is relaunched, and can also be found in the Status tab of the "About Retrospect" window. The last RDU for Retrospect 6.1 can be downloaded here
  18. We need more information. For starters, let us know the version of Retrospect, any installed RDU's, and the OS versions on the backup computer and the client. Have you ever been able to connect with this client in the past? Does the client have more than one connection to the network, such as Ethernet plus WiFi? How are you connecting with the client? Are there any other clients that you can access?
  19. Retrospect 6.x is incompatible with 10.6. You will either need to upgrade to Retrospect 8 or downgrade your OS back to 10.5.
  20. If you want support from Roxio Retrospect, you'll need to call them (and have your credit card ready). This is a peer-to-peer forum, and we users simply try to help one another based on our own knowledge and experience with the product. You don't give us any description of your problem. If your post was more than a rant and you want help from this group, we'll need a bit more information about your setup (software and hardware) and some details about the scripts that work and don't work.
  21. If the copying/moving process retains all of the file attributes Retrospect uses in comparing files (name, size, creation date, modification date, etc.), and if you have chosen the appropriate matching options in your backup script, Retrospect shouldn't back up the file a second time.
  22. There is a bug in Retrospect that can cause the 515 error during media member swaps if Link Encryption is enabled for a Mac client. The workaround is to uncheck this option. Go to Configure> Clients> Configure [your_client]> General to do this.
  23. If your restore is for an entire disk or for replacing corresponding files, Retrospect will recognize the files that are already restored and will not restore them a second time. However, if the files have been changed since they were restored, Retrospect will overwrite all the changed files with the earlier versions from your tapes. If the files you've restored include something other than document files—say, contain logs, preference files, etc.—Retrospect could end up pulling a good number of files from your earlier tapes. To avoid this possibility, perform your subsequent restore by selecting only those files that were backed up later than the date and time that tape 31 was first written to. You can find this information by going to Configure> Backup Sets> Configure [your_backup_set]> Members. If you have already restored from tape 32, you can further limit the restore process by choosing to restore only those files that were backed up between the dates and times that tapes 31 and 32 were first written to. Hope this helps.
  24. If your license code enabled you to back up everything you wanted to under 6.0, you should be able to back up the same volumes running 6.1.
  25. Being able to see the device is not the same as understanding its command set. The information about how Retrospect is to control specific new devices is incorporated in the version updates and subsequent driver updates (RDU's).
×
×
  • Create New...