Jump to content

MPH

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by MPH

  1. @NigelSmith The selected Preferences->Execution->Security Radio Button is Run Retrospect as the logged-in user. BTW, my usual user for running Retrospect has a Windows administrative account.
  2. I'm running version 18.2.2 of Retrospect Pro for Windows on Windows 10. The Retrospect icon never displays on the Taskbar even though my Startup Preference has Show Taskbar Icon checked. Using the Knowledgebase, I found the following under Getting Started in the User Guide: Retrospect icon Retrospect does not display the icon in the task bar when running in these versions of Windows. Upgrading from a previous version of Retrospect Captain Obvious sez: "No Windows versions are listed!" Is Windows 10 a version that should be listed? TIA
  3. I’m running: Windows Professional SP3 Retrospect Professional 7.6.123 MS Office Professional 2007 I upgraded to this version of Office two days ago and saw that Office installed MS SQL Server 2005 Express on the same PC. Today I noticed that Retrospect’s Configure Volumes singled out SQL Server as a separate volume entitled as “SQL Server (not licensed)â€. I checked most of the “C:\Program Files\Microsoft SQL Server†folder in last night’s backup Snapshot and the folder appears to be backed up. What are the implications of the “not licensed†notice? Won’t SQL databases be backed up? Also, from the online product description, EMC's Microsoft SQL Server Agent apparently isn’t intended for 32-bit Windows XP Pro thus adding to my confusion. BTW, I used the Knowledgebase’s Retrospect Backup Product Finder today to check out the options for Windows Professional. It asked: Will you use any of the following Retrospect server add on products? -Open File Backup -Exchange Backup Agent -SQL Backup Agent -Disaster Recovery -Advanced Tape Support I chose “Do not use add-on products†and it responded with “Back up 0 servers over the networkâ€. Shouldn’t that mean that servers on the same PC should be backed up? -TIA
  4. If the following happens, the backup set would not need recycling.: - The files with errors in the backup set are not cataloged during catalog recreation - The source files are backed up during the next Backup session Only the defective session would be lost rather than the whole backup set. How does the catalog recreation process handle this situation?
  5. When I recreated a catalog for a DVD backup set, the operation reported many “206” errors for a backup session that aborted. A Dantz forum support member said the best option for the backup set was the Recycle action. Obviously, archived files on the media will be lost with this action. To avoid recycling the DVD backup set, the recreate catalog should log damaged files and sessions into the catalog with a damaged status. Obviously, backup and restore must respond to the damaged status. Before performing a Restore with known errors, Restore could warn users with the details of the damage. Backup could determine if a damaged file can be re-recorded. In summary, the damage status preserves access to usable archived files and sessions on media with imperfect recordings while allowing subsequent backups to safely update the backup set.
  6. I use Retrospect 6.0.206 (R6) on Windows 98 SE. Recently, a DVD filled during a backup and R6 requested another DVD. By the time I discovered this situation, I didn’t have time to change media and complete the backup-and-verify so I cancelled the backup. Later, I wanted to rerun the backup. First, I checked the DVD backup set status and saw the partial backup session was listed as a session. When I ran Verify Media on the filled DVD, it logged a large number of “206” errors. I wanted to delete or ignore the partial backup session but didn’t know of a way to do it. Instead, I tried recreating the backup set’s catalog but that process also logged a large number of “206” errors. After the “206” errors, the following was logged: Additional error information for device "Plextor DVD+RW" [2:0], Sense > f0 00 03 00 22 a7 c0 0a 00 00 00 00 11 00 00 00 00 00 (PLEXTOR |DVDR PX-504A |1.01) 1/7/2004 6:10:17 PM: 174 execution errors Completed: 55299 files, 4.4 GB Performance: 109.3 MB/minute Duration: 01:24:07 (00:43:26 idle/loading/preparing) I was unsure if the recreated catalog was free of errors so, to be safe, I recycled the backup set and ran backup. Do errors logged during the recreation of a catalog result in a corrupted catalog? What should I have done differently to avoid recycling the backup set? Thank you
  7. After creating a Disaster Recovery CD iso, the operations log showed the following error: Maperror: unknown Windows error 0 I searched for "maperror" in the pdf of the user's guide, in Dantz's knowledgebase and in the forum. Only the forum had any hits but my error message was not explained. Please explain "maperror", "unknown Windows error 0", and how it affects Disaster Recovery. Thanks
  8. From page 117 of the R6 pro manual: Quote: If you begin backing up a computer to a different Backup Set (other than the one selected in the preparation wizard), you should update its Disaster Recovery preparation. I will be creating 4 DVD backup sets and rotating backups between them. Since the sets will be virtually identical, is there a reason why a single, up-to-date Disaster Recovery CD couldn't be used by any of the four sets. I don't want to keep 4 DR CDs up-to-date if one will suffice.
  9. I have encountered the grayed-out volume problem, too, although the cause was different (I renamed a Windows directory that was defined as a Retrospect subvolume). I use Partition Magic to change partition parameters on a somewhat frequent basis and apparently will have to deal with this problem repeatedly in the future. Please reply on these two concerns: 1) Concern #2 is a suggestion for a future version of Retrospect. Concern #1 is that some company’s support staffs can’t or won’t forward suggestions to the development staff (I am not aware of Dantz’s policy). Companies that ask users to resubmit a forum suggestion to their suggestion webpage lose the context of the forum discussion and the number of people affected. The forum lets multiple users show that this is not an isolated problem and it deserves review. In fact, I hope other forum users review my suggestion below and improve it. 2) Existing scripts that referenced the grayed-out volume will not recognize the proper volume, even if the volume name was not changed. If there are several affected scripts, each script must be found and corrected before it is next used or its backup session will fail. Searching for all scripts and correcting them can be error-prone and time-consuming. Since volume parameter changes and renamed or deleted subvolumes are not uncommon, this problem generates needless work for Retrospect users. If Retrospect detects a change in a volume but the volume remains on the same physical drive with the same volume name, Retrospect should fix the problem automatically and add a message to the Operations Log. Otherwise, Retrospect should report to the user that the volume was not found. Then, it should present the user with a list of volumes on the affected system and allow the user to select the “equivalent volume” or “none of the above”. If an equivalent volume is selected, update the recognition criteria for the volume. Finally, if scripts are linked to volume recognition criteria rather than storing it internally, scripts will automatically recognize the equivalent volume. TIA
  10. Quote: Drives that have similar inquiry strings (or the same inquiry string) as a supported drive can show up in the Device Status... Retrospect 6 supports the Sony DRU-500A DVD burner. According to your quote, the Sony DRU-500AX is likely (but not guaranteed) to show up, correct? Thanks!
  11. Page 28 of the Retrospect 6 User’s Guide refers to “recognized devices” that “have not been put through Dantz’s rigorous qualification tests, but will work fine with the listed driver under most circumstances.” Under what conditions can R6 recognize a device that is not qualified?
  12. I am interested in buying a Sony DRU-500AX DVD burner primarily for backup using Retrospect 6 for Windows (R6). Since it is new, Dantz doesn’t support it but does support the DRU-500A. Unless I find a reason otherwise, I am willing to risk buying an unsupported device because the Dantz forum and knowledgebase speaks well of Sony products. Also, the model number is just an “X” different than the model number of the Sony DRU-500A, which is supported. Page 28 of the R6 User’s Guide refers to “recognized devices” that “have not been put through Dantz’s rigorous qualification tests, but will work fine with the listed driver under most circumstances.” Please explain how R6 tests an unqualified device to decide if it will recognize the device. I haven’t been able to find this information in the forum but it is important for buying a new backup device. I believe many users are forced to choose between buying an older, supported device that may not be supported by the manufacturer much longer, or buying a new device with better specs and hoping it will be either recognized or eventually supported by Dantz. In my case, Dantz supports my 4-year old tape drive but technical support couldn’t help me make it work. During that time, I decided to keep R6 because its backup to disk sets is so fast and convenient and backup to CD-RW sets worked well except for the manual handling involved. I decided to move on to DVD backups because the tape drive is old and R6 has many advantages over other backup programs.
  13. From searching the forums, it appears that the oldest backup member in a backup set can be marked as missing so its media can be reused. If each member of the set is large enough to hold a full backup and the set has more than one member so it can retain many versions of frequently modified files, a member being missing appears more attractive than recycling the entire set. Being missing apparently loses only the oldest member’s files whereas recycling loses every file in the set. Page 158 of the R6 user’s guide says “Select Missing only when you have permanently lost or damaged the requested member. It is not appropriate for other situations.” That makes sense when a backup requests a specific member. Please explain if that also applies to reusing the oldest member. Are there any other special concerns about reusing the oldest member? I’ve noticed that a disk backup set’s properties allow a member to be lost or damaged instead of missing. What are the differences between lost or damaged and missing? Is marking all members in a set as missing the same as forgetting a set except for whether the backup set definition remains? Finally, I am concerned about catalog size because the last backup software I used required the user to compress the catalog periodically. Does R6 rewrite the catalog during each backup so it doesn’t require compressing? If it doesn’t, can the catalog be purged of entries from forgotten members? Thank you.
×
×
  • Create New...