Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by gnoelken

  1. Followup: For other reasons I had to recycle the backup set. After the initial full backup of my system, I decided to recreate the "Find Files" restore as outlined previously and test it. It worked as expected and all files were restored. Greg
  2. Thank you again for you help and suggestions. Thank you for the tip. When I search "all files" both folders appear, but no .nef files are found in "2016-04-01 - Watercolor". Another good idea! When I use the duplicate script the entire "2016-04-01 - Watercolor" folder gets backed up. I then search for "Ends with .nef" and the 69 nef files show up: When I just do a simple restore and drill down to the "2016-04-01 - Watercolor" folder and restore it, the entire folder, including all of the.nef files, are restored. So they are getting backed up. And I can restore other folders using the "ends with .nef". The 2 folders that I "modified" with Windows Explorer are the '*Watercolor*" folders in which I copied the files from one folder to the new "*Watercolor*" folder. In both cases only the .nef (and .raf) raw files were copied. All the other files in the (new) folders (.xmp, jpg, .cos,...) were created as I edited the raw files in my image editing software and those all show up in every search. I really appreciate your help. I can and did restore the .nef files using the simple restore. But, for me, it is now a matter of figuring out why the "Find Files" method does not work. Greg
  3. Thank you for you help Nigel. When I start with "filename ends with .nef" the deleted folder "2016-04-Florida" appears and my current folder "2016-04-01 - Watercolor" does not: I am searching the whole set but when I look at the Backup Set I can only browse snapshots within it. Every snapshot has the "2016-04-01 - Watercolor" folder in it and none of them have the "2016-04-Florida" folder: If I search "filename contains florida" both folders appear but no .nef files are found in the "2016-04-01 - Watercolor" folder. Thanks again, Greg
  4. I did another test using a folder under the '2016' folder that contained 'Pickle Springs' (D:\Greg\Pictures\2016\2016-05-05 Pickle Springs): Selecting 'Files Chosen' in the 'Searching and Retrieval' dialog box shows that the 'nef' files are included in the search results: I repeated the same search for folders that contain 'watercolor'. Several folders are found but only two that contain images. What is interesting is that the '2016-04-01 - Watercolor' folder does not show the 'nef' files as I have found. But another folder (2018-05-01 - Watercolor), containing 144 'raf' image files among dng, tif, and jpegs image files, displays all files but the 'raf' files: nef files are raw image files created by Nikon cameras. raf files are raw image files created by Fujifilm cameras. I point this out because they are similar "raw image file" formats. But retrospect backup doesn't care what the file is. This experiment has no 'Exclude' criteria. It seems to me the 'Watercolor' search criteria is the issue. So I took a look at my folders in windows explorer. A while back I migrated from the raw image editing application Adobe Lightroom to another raw image editing application Capture One. Once I started using Capture One I started using a different folder format for storing my digital images. These two 'Watercolor' folders are a case where I first edited the raw files in Lightroom, then after switching to Capture One went back and copied the raw files to new folders in a different directory. In the case of the 2016 folders, I deleted the Lightroom folder after I was happy with my Capture One edits. When I set the search for "Files or Folders" that contain "Florida", several (>13000) files are found. When I drill down to the 2016 image folders, I see the Capture One 'Watercolor' and the (deleted) Lightroom 'Florida' folder. Those 'Florida' folders display the 'nef' raw images files: When I browse the 'Recent Snapshots' in my backup set, none of them have the 2016-04-01-Florida folder displayed in them. The same is true for the raf files in the 2018 Watercolor folder and 2018 Florida folders. Is Retrospect using 'Deduplication' here? Even if so shouldn't my nef files appear in both directories? I can restore the entire 2016 Watercolor folder, including nef files by using the Restore --> Restore dialog. But I really wanted to restore the 'nef' files which should be performed with a simple search in Retrospect. At this point I will try manually grooming the disk and see if that resolves the issue. UPDATE 3 HOURS LATER: Disk grooming did not make any difference. Thanks again for all suggestions and any other thoughts. Greg
  5. I did find that if I put the entire path in as a selector: 'D:\Greg\Pictures\2016\2016-04-01 - Watercolor' The folder is found but the 'nef' files within the folder are not included! Here is a view of the most recent snapshot in the backup set of this folder: I'm really confused as to why my single 'path' selector would not include all files in that path. Any selector I choose so far (such as 'folder name ends with Watercolor') finds the folder but does not list the 'nef' files. There are two folders in the '2016-04-01 - Watercolor' folder that have 'nef' files and both are not showing those files. If I choose a single selector to find all 'nef' files several thousand are found including the folders under '2016-04-01 - Watercolor'! Thanks for any help. Greg
  6. When I use the 'Check Conditions' of my conditions, the nef files are found. It would seem that they are configured correctly. I'll play around with other configurations though. That's the way I built this query. Thanks for the heads up. I've been burned by that before! Thanks for your suggestions and help. Greg
  7. The path I had in in my original post was in error. It was actually "D:\Greg\" I have corrected the post. Sorry for the error but thanks for the quick response. You are right in thinking it was a synonym. For years I had a drive set as a folder named Data on my "D:\" drive like Linux drives could be set. It was natural habit for me to type "D:\Data\..." Also, the label of my current drive is "Data". Greg
  8. Using Retrospect Desktop version on a Windows 10 Pro PC (10.0.18363) with all latest updates installed. I'm trying to restore some images from a particular directory. In particular all images ending in *.nef that are found in two subdirectories. The image below shows my backup set (Archive_Drive) and the path to those 'nef' files from the most recent snapshot (6-27-2020): The system path is 'D:\Data\Greg\Pictures\2016\2016-04-01 - Watercolor'. The system path is 'D:\Greg\Pictures\2016\2016-04-01 - Watercolor'. I used the option 'Restore --> Find Files' to select the 'nef' files in subdirectories within the above path. Here is my search criteria: I have the option to check this selector against my "D:\" drive and I do: This is the same path that is found in the 'Archive' backup set in the first image. It finds 69 'nef' files in 2 folders. I click on 'OK' in my searching and retrieval dialog box. Retrospect searches my Archive_Drive backup set and 0 files are found: I also tested this search by creating the same selector as above and the selector finds the 'nef' files. I've rebuilt the catalog file from disk. I've checked (windows) permissions on my drive and folders. I don't think it would, but would an upgrade to 17 fix this? Are there any other options to 'fix' the backup set? Thanks for any help. Greg
  9. Hello, I am using Retrospect Desktop for Windows, version 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
  10. 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
  11. 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 Greg
  12. 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
  13. 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
  14. 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
  15. 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
  16. I do have it enabled. I've disabled it and will monitor the backup set. Thank you for your suggestion. Greg
  17. 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
  18. 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 Running on Windows Server Standard 2008 SP2 64-bit OS 4 Gb Memory Any suggestions? Greg
  19. 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
  20. 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
  21. 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
  22. 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
  23. Robin, Thank you for your quick response. I've read the FAQ, but please let me explain further. I have 2 Retrospect servers (Multi-Server). On one, call it 'Server A', I have Retrospect 7.6. I have an HP Ultrium 1760 (HP StorageWorks 1/8 G2 LTO-4 Ultrium 1760 SCSI Tape Autoloader) attached to it. On 'Server B' I have Retrospect 7.7 with an HP Ultrium 1760 (HP StorageWorks 1/8 G2 LTO-4 Ultrium 1760 SAS Tape Autoloader) attached to it. Server A has worked flawlessly since being installed in '08. Without any setup or configuration it uses hardware compression to compress the data onto the tapes. On the image below, from Server A, I have highlighted; the drive information, the 'DC' (indicating that the media is utilizing Data Compression), and a Backup Set that does indicate that I am indeed utilizing data compression (1001.1 G) on a 800 Gb/ 1.6 Tb tape: Server A info: I've copied the same info on 'Server B': Server B info: Note the drive info is the same (the revision is different because Server A is SCSI and Server B is SAS). Note the differences; the media is not using data compression (missing the 'DC' flag), and all the tapes fill up at slightly less than 800 Gb. And, just to be sure, the backup sets (all of them) are set to use hardware compression: Hardware compression: So, I am fortunate that I do have Server A. I *know* that an HP Ultrium 1760 does provide hardware data compression *with* retrospect multi-server backup. I also know, after going through HP's tech support, that the new tape drive is working properly. I also observe that, when I manually set data compression 'On' with HP's Library & Tape Tools on Server B, then start Retrospect, data compression is immediately switched 'Off'. I also have the most recent version of Retrospect and Driver Update. The backup file types are very similar on Server A and Server B; Windows OS, Linux, and some Mac. Questions: Why is data compression immediately turned off when Retrospect starts? To the forum members: Is anyone else using the HP Ultrium 1760? Getting hardware data compression? Am I missing a setting somewhere that is disabling the hardware compression? Can you provide technical assistance, perhaps a driver hotfix, that would resolve this issue? I may take the time to attach the drive from Server B onto Server A and test it. Would that help support the compression issue if it did indeed work on Server A? Thank you for the help and regards, Greg
  24. I recently upgraded the tape drive I use with Retrospect 7.7 to an HP Ultrium 1760 SAS Autoloader. This tape drive is identical to one on another Retrospect backup server (version 7.6) I administer (except the new one is SAS, the older one is SCSI). After running the first 'Transfer Snapshots' script on the new tape drive, I discovered that no compression on the tapes was performed. These are 800Gb/1.6Tb, LTO-4 tapes (note the 'Used' portion of the 1st 3 tapes on the image below): When I check the drive status with HP's Online web interface, I see that 'Data Compression' is turned off: I can turn drive compression on with HP's Tape & Library tools, but as soon as I start Retrospect, the drive compression becomes disabled. When I view the properties in Retrospect of the new tape drive, compared to my 'working' system, I see that there is no Data compression under Media ==> Format. My 'working' system's tape drive with compression has 'Format: U-416, DC' (I assume the DC stands for Data Compression), while my new drive only lists 'Format: U-416': New Drive: 'Working' Drive: I also used HP's Library and Tape Tools to test the drive compression. It tested positive with read and write results of 2.61:1 compression. But the test had a warning that the 'hardware algorithm is switched off. This was probably set by your backup software...': Also, all my backup sets are set to use 'Hardware Compression' and none use encryption (which would disable the hardware compression). In addition, I called HP tech support. We insured that the firmware was up-to-date on the new system, confirmed that the drive's data compression worked properly and did a complete drive assessment. All tests passed. System Details: OS: Windows Server 2008 w/Service Pack 2 Retrospect: 7.7.325, + Driver Update and Hot Fix, version (64-bit), Tape Library: HP Library: 1x8 G2 AUTOLDR Tape Drive: HP Ultrium Gen 4 DC Server: Dell Precision T3400 64-bit, 4Gb Memory, 3.16 GHz Core 2 Duo CPU I did purchase a service agreement and opened a ticket, but thought I would check in the forum for any help/thoughts/suggestions. Greg Noelken
  • Create New...