Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by dthede

  1. Yes. Here is something similar trying to rebuild a catalog from a disk-resident backup. "[ ]" contains my input. Tools > Repair Catalog > Recreate from disks [OK] All Disks > [My Computer] > [DiskXYZ (N:)] > Select a Backup Set to recatalog [users_Backup_Set][OK] Several Notes about the preceding line: (1) that "Users_Backup_Set" is a defunct backup set that hasn't been used in 10 years (?), has no scripts using it, etc., has been "forgotten" AND, (2) that the actual backup whose catalog I'm trying to rebuild, has a name totally different name; AND (3) no other name besides "Users_Backup_Set" appears anywhere in the various dialog boxes from Retrospect. Apparently I am forced to use that name, no matter what. Continuing with procedure, then: Are there any more disks in this Backup Set? [NO] Backup Set Users_Backup_Set appears to be encrypted. Please enter the password: [Password] Saving Backup Set Catalog File Retrospect Catalog Files (No items match your search.) File name: Users_Backup_Set.rbs (autofilled by Retrospect) [click SAVE] Message: "The Backup Set data file name is invalid, cannot recatalog the set using these files." Note also, the surprising History entry: History Tab > Rebuild Operations Log + Executing Rebuild at 6/18/2012 11:34 AM To Backup Set Users_Backup_Set 6/18/2012 11:34:14 AM: Execution completed successfully I'd like some help on this, too.
  2. dthede

    Can I run Retrospect Professional in safe mode?

    You might try using msconfig.exe to disable startup items, and then systematically renable them in groups, "binary search style."
  3. Re: Additional Problem. I don't know how to fill the gaps you are referring to. (That's something I'd like to know!) However, Retrospect will allow you to control whether duplicates are added to the resulting Backup Set. In the Transfer script you create look for OPTIONS button, then go to MORE CHOICES. Click on MATCHING and figure out which of the 3 boxes (or combo thereof) meet your requirements. Use the HELP to understand the implications of "a match."
  4. From time to time, perhaps all too frequently, I get messages that a particular chunk of a backup set is either corrupt or from another backup set. Accordingly I have to declare the chunk missing; as other users will know, sometimes it requires declaring several chunks missing. (1) Is there a reader which can directly read the chunks as they exist, (corruptions and all) whether they be compressed or uncompressed? 600MB of unusable data in compressed format represents a significant loss. (2) In some cases I would be willing to sift through the file to attempt to do partial recovery. Are there any File Recovery softwares which others have tried to use with Retrospect backup sets? Didrik
  5. dthede

    Backup set password

    posting moved
  6. dthede

    Backup set password

    Is there a way to change a password on a backup set? SOP requires changing the password on a regular basis. It appears uncertain how to change a password on a backup set.
  7. No subtle reason; simply a mistake.
  8. I have a backup script (back to disk) which specified Backup Set compression. When looking at the Op Log History Tab, however, it shows zero percent compression. I've gone back and checked the script to verify that my SOP of using compression was indeed selected. The target Volume being backed up is spongy so I would expect about 30% compression, as on other backups for this volume under a different script, not zero. Any helpful thoughts regarding software compression under Retrospect version in the Win XP Pro SP2 environment?
  9. dthede

    Software Compression Not Happening

    As others have stated, I also have a backup script (back to disk) which specified Backup Set compression. When looking at the Op Log History Tab, however, it shows zero percent compression. I've gone back and checked the script to verify that my SOP of using compression was indeed selected. The target Volume being backed up is spongy so I would expect about 30% compression, as on other backups for this volume under a different script, not zero. Any helpful thoughts regarding software compression under Retrospect version in the Win XP Pro SP2 environment? (The response that there is simply 0% compression on average is not helpful, since the same target files typically report back 29% compression under the original script.) Since this is a first backup under a new script, (All Files selected) it's easy to compare bytes backed up in the Backup Set to the bytes in the source Volume.
  10. It would be helpful if in the ACTIVITY MONITOR we could see where in the Backup Set Transfer Source the transfer operation was currently. Currently it shows simply the source Set and the Destination Set and file. It would be helpful to know the Snapshot and the Session from which the file is currently being pulled, so projected space requirements can be made more accurate.
  11. Same problem(s). No solutions yet. Except that my .iso image is 723.6 MB ...
  12. I have exactly the same problem(s), using the same patched version. It does not seem to be a permissions thing. Could it be because the .iso image file is larger than 700MB? That is, does Retrospect "think" it's actually writing a CD-R and has exceeded the media capacity, hence "cannot write" even though I have told it to "continue."?
  13. dthede

    Can't restore from rdb files

    Assuming that the rdb file is actually not corrupt, the entire Retrospect use of file list box and the way it points to a backup set member is non-standard by any understanding of Windows. What it's actually asking for is the folder enclosing the folder named "Retrospect" not the backup set. Misunderstanding this on an occasional basis -- say incorrectly pointing to the set after receiving a notice that the backup set cannot be found -- has led my installation to have some infuriatingly goofy hierarchical structures. For example, J:\Retrospect\Main_Backup_Set\1-Main_Backup_Set and J:\Retrospect\Retrospect\Main_Backup_Set\2-Main_Backup_Set as well as J:\Retrospect\Main_Backup_Set\Retrospect\Main_Backup_Set\3-Main_Backup_Set These can be properly sorted out but it takes time and patience and complete understanding of where that dialog points and where Retrospect "thinks" it points. Ultimately one simply asks "What was development thinking when they set it up this way?" They simply decided to make words mean what they wanted them to mean. (Every software I've used has such peculiarities.)
  14. dthede

    Retrospect Optimal Use

    It would help to have an authoritative document or other authoritative posting on the optimal deployment of Retrospect 7.5. Here's why: There are 34 issues returned on a search of "backup time" under the Professional forum, and 15 or so topics referring to "optimiz" (the root). In my case, the actual backup time is much less than the building snapshot time and the closing time. There must be more experienced users than I, who know the best balance among: backup size, catalog size, backup time, closing time, building snapshot time, and comparing time. For example: A typical backup that requires 10 minutes for building a snapshot, and 4 minutes for closing time, but only 3 minutes for backup, might indicate that the catalog has simply grown too big relative to the file "churn" for the backup period under consideration. Maybe it indicates that a new catalog should be started. Or, from a strategic point of view, perhaps it indicates that the backup set is itself too broad in scope; i.e., the actual churn is typically in a small region of the catalog, but the it still necessitates Retrospect manipulating the entire 800MB catalog. One would think that EMC / Dantz, etc. would have some typical "phase diagrams" for optimizing performance. Perhaps a rule of thumb guide that speaks to the percentage of a backup set (&/or catalog) that is updated during a typical backup, would be helpful. Naturally, it would be completely unhelpful and would really duck the issue to say that every installation is different and performance would vary so much that generalizations are not possible. It would be as silly (and unhelpful) as saying that there are so many different file types that no one software can back all of them up. We will recognize that "our mileage will vary."
  15. Another characteristic may be that I went from build .285 to .370, skipping the .324 build linked by Robin Mayoff in one of his posts. Could it be that something in .370 relies upon a change made in .324, such that the Catalogs are perceived as corrupt if one skips the .324 update?
  16. I have received this error for 8 backup sets today, in the non Multi-swerver environment. The only change which has occurred which is signifiicant regarding those Backup Sets, is that I've installed the .370 build, and this is the first backup since upgrading. My sympathy for problems voiced elsewhere on these forums, has just increased by a factor of 10.
  17. dthede

    MultiServer 7.5.370 upgrade

    Is it pointless to ask in this discussion, why someone would be _adding_ NT 4.0 Workstation clients? Wouldn't the proper action be to get rid of them?
  18. dthede

    I am getting tired...

    I will try to educate myself on this "well-known fact" of Retrospect's leaking memory. Thus far, I have not experienced it on three separate workstation installations, nor on one SBS installation over the course of several years.
  19. dthede

    I am getting tired...

    I hear you! Based on your problem description, however, it sounds like you're using Microsoft Small Business Server 2003. It is pitiful, perhaps especially when configured by an Authorized Microsoft SBS VAR. The SQL component has a memory leak, and does bring down the server periodically. The default, our 2nd service person pointed out, was for SQL to use all memory except the last 10MB. It was commonplace for the SQL services to be using 1.4, 1.8, 1.9, 1.95 GB (gigabytes) of RAM on a 2GB system. There was a glitch in our installation such that it required a password to change the upper bound on SQL memory usage, and our service providers could provide no password. I should point out -- worst of all -- that only Webroot's Spysweeper used SQL, and it could have used the simple SQL Express or the MSDE. We ended up junking the "all-Intel SBS" server after three years of this insanity. For our situation, Retrospect and Norton Antivirus softwares were the ONLY two softwares which worked properly from start to finish. EACH and EVERY other piece of software on that box had sustained and major problems from day #1 to the day the box was taken off line.
  20. Similar question with proposed answer. I had two PICnnnnn.jpg files which produced this type of error for quite a while. Eventually, I noticed the distinctive names of the two files when I happened to be running through the quarantined files area. I was able to simply delete the files, and subsequent verify error messages (of course!) disappeared. Have you considered that the reported files are infected in some way?
  21. Don't know version 6, Express. Sorry. Under Retrospect 7.5, one could delete the catalog information (what I assume you refer to as "back up info") on the HD, C:, and regenerate the catalog information elsewhere by having Retrospect re-read through the Backup Set(s) stored on the Maxtor drive(s). Perhaps one could simply move the Catalog files to external media (or to a different internal drive) and try a Repair Catalog scenario, but I think that ends up simply re-reading the externally stored Backup Set(s) anyway.
  22. Speaking strategically, isn't the preferred approach here to use Exchange Server for Outlook? I'm not an Outlook user, but I believe that the concept and intention of the extra-option backup capabilities for both Retrospect and Veritas (and probably other backup softwares) is precisely to enable users to effectively backup the changes in database-type files, such as Oracle, Exchange, MS-SQL, etc. So the answer, conceptually, is that of course there's a way to achieve what you want....just not from where you are. I'd expect that it is precisely this data management headache you're facing that is the motivating force for moving to a proper email system, databased in a standard way and offering slick backup protection.
  23. I don't have an answer for you, yet, but I hope so, because the same thing has happened to me, in spades. We rotate external HDs onsite and offsite for backup, and as you'd expect, each filled up and spilled to another drive. But, our case may not apply to you. We changed (retired) our PDC and also changed the domain name when the new PDC was commissioned. Retrospect interpreted the existing backup scripts in a protective way, I think, but in an unintended way: it began with full backups of the media under its control. So instead of a routine 2.7 GB backup, suddenly, we had a 508GB backup -- for BOTH onsite & offsite media. Naturally the spillover was huge, times 2. I'll be trying some strategies later this weekend and post positive developments.
  24. dthede

    Client Setup Files

    I have purchased two client licenses for the Retrospect 7.5, although not until today have I needed even one of them. (The licenses section of Config menu also affirms this as "0 used, 2 available.") I have read the various installation directions for Client installation. I cannot find the Client Setup files referenced in the various Help files nor on the original Express CD, by the way. Following may be why, but does not provide the solution. Anyone help, please? The Retrospect I am using was a download purchased online as an upgrade to the Express verison. No CD. The various intermediate updates have likewise been downloads. No CD. The directions refer to locating the Client Setup files on the CD (no CD). Is there an alternate location where these Client Setup files might be found? It's annoying to have the various Client Updaters files, which (apparently) are to update something I don't have in the first place.
  25. dthede

    Newbie Q's about scheduling

    It's hard to grasp the significance of Retrospect being "hacked to run on windows," even supposing it was. I suspect the the SBS 2K issues you probably experienced were a contributing factor to your conclusion of "lot of cash for nothing." SBS is a fairly specialized environment, contrary to what one might conclude from the marketed concept of "a little bit of everything for a small business." Essentially a lttle bit of each of several products have been aggregated or force-fit or boxed-together to help special environments get a significant taste and tangible productivity from a variety of puzzle pieces that big companies typically have integrated and maintained by on site staff. (We use SBS and have used other Server bases instead, and as well, including older Macintoshes.) The fallacy implicit in using SBS may come to light if it is not chosen as a perfect match for the firm's needs or expected needs in the immediate future. I think it needs to be a perfect match to work effectively. One fallacy may be that because it's a little of several things only a little staff knowledge of several things is necessary. False. Another fallacy may be that because it's a small business, it probably only has "small" needs, and the SBS has commensurately "small" support demands. It requires an extensive appreciation of the integrated workflows that are possible and deep understanding of the underlying mechanisms that make that flow possible. I think our experience shows, too, that SBS requires a very high-powered machine & disk system rather than a moderately powered one because it _is_ running a variety of integrated apps at or near the OS level. One cannot add anything new to such a machine with full confidence that there won't be an unforseen (bad) interaction between the new thing, and, not one or two major apps, but among the new thing and 5 majors apps. 30% of one 3.2 GHz processor is consumed simply by the defensive anti-virus and anti-spyware measures now required especially in the small firm. SQL server sucks up 900MB RAM just in the course of housekeeping details (no SQL users beyond the OS). IIS doesn't let the disks rest. Exchange server is frequently busy. And this is on the current Premium version of SBS, which fixes a host of previous deficiencies. I can _almost_ feel your pain if you used a previous version where every application's weakness appears unbidden.