Jump to content

gnoelken

Members
  • Content count

    17
  • Joined

  • Last visited

  • Days Won

    1

gnoelken last won the day on August 21 2017

gnoelken had the most liked content!

Community Reputation

2 Neutral

About gnoelken

  • Rank
    Occasional forum poster

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello, I am using Retrospect Desktop for Windows, version 16.6.0.133. One of my hard drives (not the system drive) failed on my desktop PC so I replaced it and decided to boot from the recovery CD to restore the files to the new drive. Unfortunately my catalog files were on the failed drive, but after every backup I copy the catalog folder to the drive that the retrospect backup files reside on. When I booted to the CD and tried to restore I was prompted to find the catalog file. I drilled down to the file and when trying to open it I received a dialog box "File Not Found". When I tried the other catalog files in the folder I received the same message. My next step was to download a backup from my Backblaze remote backup onto a USB drive. Once again I received the same message. I gave up using the disaster recovery option. I booted the PC and copied the Backblaze Retrospect catalog file onto my C:\ (system) drive. When I opened the file from within Retrospect it loaded fine and I am using it to restore my drive as I write this. I've used the recovery CD in the past with no problems. This is concerning since I would need to use it to recover a system drive. Thanks for any help. Greg Noelken
  2. gnoelken

    Error 1103 After Windows Update 1809

    Lennart_T, Thanks for the link. I'll enable the default administrator account. When unlinking my OneDrive account, the backup completes with no errors. Regards, Greg
  3. The 1103 error with OneDrive folders seems to have returned after Windows Update 1809 (Windows 10 Pro, OS Build 17763.55): Note the backup of the system drive is aborted after the error is encountered. I'm unlinking my OneDrive account now to see if that helps. I'm using Retrospect Desktop 15.5.0.179 Greg
  4. gnoelken

    Strange warning when restoring

    That may be the issue. I did have the Windows 10 anniversary update. I wound up doing a fresh install with the "Refresh Windows Tool" from Microsoft. Thanks for the info on the compatibility with the newer versions. I'll look into getting an upgrade. And thank you Lennart for the prompt reply and assistance. Regards, Greg
  5. gnoelken

    Strange warning when restoring

    Hello, I am using images in this post in hopes that it will clarify what I am doing. I apologize if they don't do that. Please let me know if any further info is required. I'm using Retrospect Version 10.5: I am trying to restore my Windows 10 PC from a backup, because I could no longer boot into Windows 10 when when powering on. I am using the Retrospect Recovery CD. I first tried to restore over the original windows installation, but that failed with the same errors and I still could not boot into Windows. So I deleted the Windows partition and reinstalled Windows from a Windows installation CD. I can now boot into Windows 10. I then used the Retrospect Recovery CD and attempted to restore the Windows drive from my backup set (named "Archive_Drive"). I configure the restore options as the image below shows: Within minutes after starting the restore, I get a dialog box that states "Warning: All data on the following volumes will be lost:" The volume is the drive that contains the backup set used to restore the drive: At this point I cancel the operation. I have tried renaming the Windows drive letter to "C:" but the same dialog box appears. I don't want to click "OK" since I fear that it will wipe out my backup set files! Here is a list of the drive configuration (from the Retrospect Recovery CD "Configure drives" option): I am restoring to the "G:" drive. Any help is appreciated. Greg Noelken
  6. Wow! That works great! Thank you both. Greg
  7. Hi, The Release notes for Retrospect for Windows, version 8 (http://kb.retrospect...&fs=Search&pn=1) state that a static IP address can be configured with the Disaster Recovery CD: Bug Fix 2497: The Retrospect Emergency Recovery Disc now supports both static IP and DHCP networking I just created the CD. When I boot up to the CD, I see no option for configuring the IP address. It only seems to get an IP from DHCP. Is there some method I should follow to use a static IP? Thanks and regards, Greg
  8. Well...It's been 2 weeks since disabling 'Back up file system security information from servers' and no duplicate backups! Let's hope your suggestion solved the problem. Thank you Cygnis! Greg
  9. I do have it enabled. I've disabled it and will monitor the backup set. Thank you for your suggestion. Greg
  10. Lennart, Thank you for your prompt reply. That makes this more perplexing, since neither the creation date or modified date has changed. Maybe I should set the 'match only in same location' option. This is not dual boot -- just the Win Server 2003 OS. That is a good thought. I checked the event logs. Packages were downloaded on October 4, but not installed until October 13 at 1:52PM. It is odd that the duplicate backups occurred within this Oct 4-13 period. Again, thanks for any suggestion you may have. Greg
  11. I'm running a proactive backup to a disk backup set. The backup is incremental and will backup the client every 24 hours. Recently the backup set filled up and was prompting me for new media. Looking closely at the backup set sessions, I noticed that all files on some drives were getting backed up in subsequent sessions. Because these files may add up to 100 Gb, the backup set fills up quickly when the same files are backed up multiple times. To illustrate. A 1.3 Gb file in one folder on the client was originally backed up on July 14, 2010: Note the 'Created' and 'Modified' Dates. Then, for some reason on October 5, 2010, this file, along with the rest of the files on the drive, were backed up again: Note that the 'Created' and 'Modified' date did not change. Then, one week later on October 12, 2010, the drive was backed up again(!): Again, the 'Created' and 'Modified' dates did not change. Notice it does not happen every night. The 'Don't add duplicates to Backup Set' for the backup set is checked. The user of this system did tell me he uses 'Robocopy' to mirror this drive to a USB drive. He's been doing it for several months. The Retrospect client is 7.6.106 running on Windows Server 2003 (NTFS files system) Retrospect Server: 7.7.325 (64-bit) Driver Update and Hot Fix, version 7.7.3.102(64-bit) Running on Windows Server Standard 2008 SP2 64-bit OS 4 Gb Memory Any suggestions? Greg
  12. Hello Johnny Mac, I'm glad that you were able to get compression too. I did open a ticket. I was told that "we have an escalation open" on it, which I assume means they have elevated it to their upper level support. Your posting on the forum helps. It means my problem is not unique to me. I'll certainly post any input/updates I receive from them. Regards, Greg
  13. Johnny Mac, Thanks for replying. At least I know I'm not alone with this problem. From what I see, I think you're backup sets will have data compression. Please post the results. Regards, Greg
  14. I've completed my backup set transfer. The data is compressed after adding media to the backup set as described in my previous post. Before (same backup sets): After: From 3+ tapes down to 1+ tapes. This may not be a bug and just be unique to my system. At least I can get hardware data compression. Any explanations would be appreciated. Regards, Greg
  15. With many more hours of experimenting I have found what causes the tapes to either have data compression (DC) or not. While creating an experimental backup set, I wound up adding a tape to the backup set that had DC. But I wasn't sure how I did it. After many more trials, I found how I can create a backup set with (or without) DC. All of the backup sets as described in my previous posts were created or recycled in the same manner. Since I archive the backup sets every 6 months, it was time to do so on July 1. I just purchased the HP Ultrium 1760 and new tapes to coincide with the archive. I put new tapes in the library and then selected 'New Backup Set' from the 'Action' menu on my backup sets. I added the new tapes in the manner I always do: click the 'Members' tab, then 'Add'. When the 'Add tapes to backup' dialog appears, I click on the member I want to add then click add. I do that for all members, then click 'Done'. After running my 'transfer snapshots' from my disk backups to the tapes I discovered that the tapes did not have DC and posted my first post above. Apparently it was the way I added the members to the backup set that determined whether DC was implemented or not. Here are my tests: I created a new backup set 'A'. I made sure 'hardware compression' was checked and continued until the 'Add new members' dialog box appeared: I'll add members 5, 6, and 7. To add member 5, I click on member 5, then click on the 'Add' button: Once it is added I view the properties. Note that there is no 'DC' flag under the 'Format:' section: I repeat for mediums 6 and 7; click on the medium, then on 'Add'. Again no DC flag appears for the properties for either one. And when I look at the HP remote web interface, it confirms that DC is off: I click 'Done' after adding the media, then look at the properties of 'Backup Set A': 2344.2 Gb for 3 media, or 781.4 Gb/tape. So once again confirming no data compression. (I do realize the available space is theoretical.) But now I create another backup set and this time it has full compression. I go through the 'New Backup Set' dialog boxes until I get to the 'Add new members' dialog box. *This time*, before I click on the member and then on 'Add', I *move* the member into the drive, then click 'Add'. Once it is added, I look at the properties: Wow! DC is now a property of the 'Format:'. I *move* the next media into the drive and click 'Add'. Again, DC!: And the third!: And the properties: Wow, 1562.8 Tb/tape! And the HP remote web interface!: So, the only difference is; when adding members to Backup Set A, I clicked on the medium, then clicked 'Add', for Backup Set B, I moved the medium into the drive, then clicked 'Add'. This action is repeatable... Questions: Is this a bug, or isolated to my environment? I think it is a bug... What will happen when, during a backup, new media is required and Retrospect uses a blank one to automatically add it to the backup set? Will it be flagged for Data Compression? I am running my backup set transfer now. It took 3+ tapes with no compression to complete. I'll post my results of this test after it completes. Greg
×