Jump to content

tbr00

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tbr00

  • Rank
    Newbie
  1. I figured it out - and it's a little embarrassing. When I came to transfer manually the additional snapshots I discovered that the Snapshot Transfer window somehow had a selector set, presumably from some long past activity. That selector said to exclude files with "volume name matches c". Now at first sight I though that was harmless because nothing had originally come from C:, but of course it's not a complete match, but matches anything containing the string "c". Sure enough all the sources which transferred zero files contained the letter c in the volume name. With that selector deleted, things are looking up. Thanks Lennart_T for the help.
  2. As mentioned in the original post I was transferring 34 snapshots. I am now pretty much doing as you suggest, except starting with a full backup from disk of those partitions that are still online. Now that's complete I am about to manually add the remaining snapshots I need. Given there was no error reported in the original attempt, there has to be a bug. Either an error did happen, but it was not reported, or, it simply didn't function as advertised. My money is on the latter.
  3. Transfer was from LTO-3 tape to LTO-4 tape.
  4. Retrospect 12.6.1.101, Windows 7 Professional. I have a tape backup set that I wished to transfer to new media. However, the source tapes contain one particularly large snapshot which is no longer relevant. So, instead of copying the entire backup set with the Backup Set Transfer function I used the Snapshot Transfer function. I added all the snapshots except for the one I did not require to the source set catalog file, selected them all, and initiated the Snapshot Transfer operation. The operation completed without errors. 34 snapshots were selected and transferred. However, I noticed in the logfile that for some sources. while I had selected all available snapshots on the source tapes for that source, Retrospect decided that for each of these snapshots "No files need to be transferred". Since there is no overlap in the files in these snapshots and those from the other sources on the source set, and since the destination was new media, something had to be wrong. Here is an extract from the log: Pictures (10/26/2017 9:40 AM) No files need to be transferred 5/8/2018 8:33:05 PM: Execution completed successfully Duration: 00:00:19 (00:00:11 idle/loading/preparing) Pictures (9/16/2016 9:14 AM) No files need to be transferred 5/8/2018 8:35:43 PM: Execution completed successfully Duration: 00:02:38 (00:02:30 idle/loading/preparing) Pictures (7/28/2016 11:36 AM) No files need to be transferred 5/8/2018 8:36:33 PM: Execution completed successfully Duration: 00:00:50 (00:00:42 idle/loading/preparing) If I look at the destination set there are no "sessions" recorded for these transfers but there are snapshots. However, if I try a restore, I can select any one of these snapshots, but it contains zero files. The files are most definitely there on the source backup set and I can restore from them as expected, so they should have been transferred. Clearly something is seriously wrong here.
  5. I cannot do a tape verify in 7.7 build 325. Windows XP, IBM Ultrium 2, SCSI I have two failing scenarios. The backup set I want to verify is missing member 2. When I run the verify it completes the first tape OK, but does not eject it. It then asks for member 2, even though that is marked missing in the backup set. I click choices, tell it is missing again, then it asks for the third member. But, as soon as I touch the eject button on the drive to switch tapes Retrospect exits. No message, nothing in the log, just gone. This is repeatable. Then I tried a run ejecting the tape before telling it member 2 is missing. This time, when I press the eject button Retrospect crashes with Assertion failure at: "elem.cpp-1098". I submitted the error report it created.
  6. tbr00

    Disk to tape problem

    Thank you! If I define it as a subvolume and just backup that subvolume it works. Backing up the whole volume still behaves as before though, ignoring the Retrospect directory. At least this gives me a way to get what I need.
  7. tbr00

    Disk to tape problem

    I have 7.7.203 with driver 7.7.1.102 I have a number of client machines backed up automatically to disk backup sets stored on a share on a NAS device. I backup the whole NAS to tape. For some reason Retrospect is not backing up to tape anything in the "Retrospect" directory where the disk backup sets are stored. I have tried a separate immediate tape backup in which I set the source to the share containing the Retrospect directory and I made sure the filters said to include "everything" and exclude "nothing" yet still it does not copy them. If I use the check function to see what files have been selected by the selectors, the Retrospect directory is shown, but the box is not checked, and I cannot check it by hand. Why will Retrospect not treat these files as just files and back them up? How can I be sure these are the only files it is arbitrarily choosing to ignore?
  8. tbr00

    Sudden loss of performance on LTO II tape

    Problem solved. I removed and reinstalled the device driver for the Adaptec 39160 SCSI card and now performance is back to normal. Still baffled as to the cause of the corruption, especially as it was "working" without reported errors in the highly degraded state.
  9. I have 7.7.203 with driver update 7.7.1.102. The system is Windows XP 32 bit with an IBM Ultrium II on SCSI. Last week I was able to do a full backup of about 1.5TB and then restore this to a different server. Absolutely no problem and performance was normal. Since then the only thing I am aware of that I have changed in the configuration is the location of the catalog files (which were part of the data I was moving to a new server). Now all of a sudden performance has dropped to a crawl. The best I can get for either a backup, restore, or media verify (the same backup set that read fine last week) is about 170MB/min, (about a tenth of what it was/should be). I am using new media, I have run diagnostics on the drive with no problems. I have tape alert turned on, but I have no errors or warnings of any kind in the logs. Nothing in the system event logs. Both backup and restore work in the sense that data is recorded and can be restored OK, but with unusable performance. Rebooted, cycled power, nothing helps. I have tried both optical and hard drive backup sets and these both work fine with no apparent loss of performance in those cases compared to what I have seen in the past. I went back to 7.6, but performance is equally bad on the tapes. The tape moves for about 2 seconds then stops for about 20 seconds and then this cycle repeats. During the time when the tape is not moving, I see the activity monitor steadily clocking up the number of files and the amount of data transferred, and showing different filenames going by, so it's as if data transfer from the drive's buffer is in slow motion. There is nothing else running on the system, CPU usage is about 2%. I'm tearing out what little hair I have left, and have no idea what to try next. Any suggestions appreciated.
  10. tbr00

    Selectors in Windows 7

    I recently upgraded to version 7.7 and added a Windows 7 client. The backup is running on a Win XP machine. It appears that Microsoft have arbitrarily rearranged where user's Application Data is saved in Windows 7. I used a script the same as I have used previously for an XP client and found that the selection "Windows is Application Data" puts nothing in the backup. Poking round the Client machine I see the "Application Data" folder is empty and there is a new folder named "AppData" which contains what I would have expected to find under Application Data, but Retrospect did not recognize it. There may well be other gratuitous changes of this kind which break the built in selectors. Is there any plan to update the selectors? For now I'm going to do a full backup just to be on the safe side. Increadibly, the super stripped down "Windows 7 Non-starter Edition" still seems to need nearly 100K files!
  11. Taking my life in my hands I ran the 7.6 installer over the top of the 7.7. Running 7.6 again I can configure the device and I ran it for both DVD+R and DVD-R. Then I reinstalled 7.7. Lo and behold with 7.7 I can now use the drive with both DVD+R and DVD-R media. I still cannot run another configuration though as it is still greyed out. So bottom line is: 7.6 will configure the device OK, but will not recognize the drive after it is configured. 7.7 will not configure the device, but it will work just fine if you give it the configuration files created by 7.6. Seems pretty clear there is a bug here!
  12. Thanks for that clue. I have upgraded. When I start 7.7 with the driver file in place that I created in 7.6 the drive is recognized and I am able to backup and restore from it. However there is still a problem. The driver file I have left over from my experiments in 7.6 is not for the type of media I actually want to use. In 7.7 the option to configure the drive is greyed out. If I remove the driver file the drive is of course not recognized, but the configure button is still greyed out, so I cannot make a new custom configuration file for the other media type. Of course having installed the 7.7 update I no longer have version 7.6 available to make a new driver for the other media type. Grr!
  13. Thanks for the response, but it does not address my question. The logfile says configuration was successful (see below). The dis it writes, when loaded into another drive is reported as "Custom Configuration Test Disc". I have a plausible RDI file (also see below), but I cannot test it as you suggest, because from some reason the drive is still not showing up in status, and the driver does not appear to be getting loaded (the field is blank in the environment tab). So what could be preventing it from being loaded, so that I can actually do the test? From the logfile: + Running Custom Configuration tests on PIONEER BD-RW BDR-205 at 12/14/2009 9:31 PM 12/14/2009 9:31:49 PM: Setup test: Successful 12/14/2009 9:31:49 PM: Default setup test: Successful 12/14/2009 9:31:49 PM: Drive type test: Successful 12/14/2009 9:31:49 PM: Drive initialization test: Successful 12/14/2009 9:32:21 PM: Disc information test: Successful Testing DVD-R media type 12/14/2009 9:32:21 PM: Write method 1 tests start 12/14/2009 9:33:13 PM: Write method 1 test: Successful 12/14/2009 9:33:56 PM: Read test: Successful 12/14/2009 9:34:14 PM: Append test: Successful 12/14/2009 9:34:45 PM: Read test: Successful 12/14/2009 9:34:45 PM: Write method 1 tests final result: Successful DVD-R media type is ready to be used with the drive - This drive has been successfully configured to use DVD-R media. Contents of RDI file: [Default] Retrospect=7.6.123 RDU=7.6.3.102 GenRDU=0.0.000 RDI=0x64 User=0x1 Vendor=PIONEER Product=BD-RW BDR-205 Revision=1.03 ShowType=0x41633034 DriverFlags1=0x70b94f02 DriverFlags2=0x3 DriverFlags3=0x883 DriverFlags4=0x0 DriverFlags5=0x0 Date=12/14/2009 Stamp=0xc74c5ffa Formatter=0x2 Media=0x2 TestResult=0x1
  14. I am having the same problem with a Pioneer BDR-205. I have the same windows and retrospect version though I have driver hotfix 7.6.2.101 which is reported as the latest version when I update. I can successfully run the device configuration and it creates an RDI file that is almost identical to the one I have for an HP 640c which works fine. The Pioneer drive never shows up in the Status tab, and in the Environment tab no driver is listed. I can accept the possibility that an unqualified drive may not work properly, but since Retrospect thinks it has successfully completed a custom configuration why is no driver showing up in the Environment tab once the RDI file has been created?
×