Jump to content

James Harris

Members
  • Content count

    9
  • Joined

  • Last visited

  • Days Won

    1

James Harris last won the day on May 26 2014

James Harris had the most liked content!

Community Reputation

1 Neutral

About James Harris

  • Rank
    Newbie

Recent Profile Visitors

170 profile views
  1. James Harris

    Chipset Driver update broke Retrospect

    Probably not...Oh well, no resolution anyhow
  2. James Harris

    Chipset Driver update broke Retrospect

    R17 has same problem. Backing up to NAS works without error. That, and due to the fact that it did work before the chipset drivers update, it is definitely an USB problem. I guess I'll just wait for the next chipset driver update & see what happens
  3. James Harris

    Chipset Driver update broke Retrospect

    Latest versions of both...all updates applied As the log says "Trouble writing", I am backing up TO the disks. I have tried different folders. Seems like it goes fine for around the first gig & then errors start popping u,p
  4. I have run Retrospect on this machine using two backup sets on two separate USB drives for about a year and a half without any issues. I installed an update to my motherboard's chipset drivers and since then, I get write errors almost immediately after starting a backup. Tried different ports & different cables. What is even more interesting is I copied a few TB using GoodSync & TeraCopy with verify on & both ran flawlessly, It appears to be some type of conflict between Retrospect & the version of these drivers. At this point, I have stopped running Retrospect after spending many hours trying to find the cause. If anyone has any suggestions, let me know. Since I can't rollback chipset drivers, I think my only options are to wipe/re-install Windows or wait for a new version of the chipset drivers or Retrospect & cross my fingers. Since Retrospect is just one prong of my backup strategy, at this point, I am not willing to redo my entire OS installation. Here is a sample log: + Recycle backup using Data at 3/2/2020 1:21 PM (Execution unit 1) 3/2/2020 1:21:53 PM: Finished scanning backup set data files To Backup Set Backup Set A... 3/2/2020 1:21:08 PM: Recycle backup: The Backup Set was reset - 3/2/2020 1:21:08 PM: Copying data on Data (I:) 3/2/2020 1:23:05 PM: Found: 86,121 files, 8,105 folders, 352.6 GB 3/2/2020 1:23:06 PM: Finished matching 3/2/2020 1:23:06 PM: Selector "All Files" was used to select 86,121 files out of 86,121. 3/2/2020 1:23:07 PM: Copying: 86,121 files (352.6 GB) and 0 hard links [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000000.rdb, osErr 483, error -1001 [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000000.rdb, osErr 483, error -1001 [*] xopFlush: flush failed, error -102 (trouble communicating) [*] xopFlush: flush failed, error -102 (trouble communicating) Trouble writing: "1-Backup Set A" (629145600), error -102 (trouble communicating) Trouble writing media: "1-Backup Set A" error -102 (trouble communicating) [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000001.rdb, osErr 483, error -1001 [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000001.rdb, osErr 483, error -1001 [*] xopFlush: flush failed, error -102 (trouble communicating) [*] xopFlush: flush failed, error -102 (trouble communicating) Trouble writing: "1-Backup Set A" (1258291200), error -102 (trouble communicating) Trouble writing media: "1-Backup Set A" error -102 (trouble communicating) [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000002.rdb, osErr 483, error -1001 [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000002.rdb, osErr 483, error -1001 [*] xopFlush: flush failed, error -102 (trouble communicating) [*] xopFlush: flush failed, error -102 (trouble communicating) Trouble writing: "1-Backup Set A" (1887436800), error -102 (trouble communicating) Trouble writing media: "1-Backup Set A" error -102 (trouble communicating) [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000003.rdb, osErr 483, error -1001 [*] MapError: unknown Windows error 483 [*] TFile::Flush: FlushFileBuffers failed, H:\Retrospect\Backup Set A\I__data\1-I__data\AB000003.rdb, osErr 483, error -1001 [*] xopFlush: flush failed, error -102 (trouble communicating) 3/2/2020 1:23:57 PM: Execution stopped by operator Remaining: 80289 files, 350.7 GB Completed: 5832 files, 1.9 GB Performance: 2274.7 MB/minute Duration: 00:02:49 (00:01:59 idle/loading/preparing) 3/2/2020 1:23:57 PM: Compressing catalog file
  5. James Harris

    Verifying backups on B2

    I have a script that verifies my local backup sets monthly. I have an offsite set stored on B2. I know downloading costs but I also know that sinking feeling of finding out a backup is corrupted only after needing it. Simple question...Do I need to verify backup sets on B2 or am I just wasting time & money?
  6. This may be a stupid question but I'm new to Windows Server.... I purchased Retrospect (Server version) and got on the server thru remote desktop, installed it, set up everything and logged off. Nothing ran without me being logged in thru RDP. So I disabled the timeout on RDP and am just leaving it connected. Works but it just seems like there has to be a way to have it run without being connected. Any help for a server newbie? Thanks
  7. On 10.5, when running a Duplicate job, I would get one e-mail at the end telling me which files didn't copy. On 11, a separate e-mail comes in each time a copy fails so I need to go through a bunch of e-mails instead of one. Is there a setting to give me one complete report by e-mail once the job completes?
  8. James Harris

    Compare Errors

    No, I have Block level turned off. These are just mp3's files, so they are pretty small files. I'm backing up my entire Users directory but it is always mp3's that fail to compare. I am using Win 7 64 bit ultimate fully patched, 8 gig of RAM on dell xps 8300. Retrospect is also latest 9.0.1 (110). And it is happening both in Backups and Duplications Here's an example + Duplicate using Duplicate Brad at 5/27/2014 10:00 PM To volume Duplication of Brad on FantomHD (N:)... - 5/27/2014 10:00:26 PM: Copying Brad on Local Disk (C:) Using Instant Scan File "C:\Users\Brad\AppData\Local\Microsoft\SkyDrive\logs\SkyDrive.exe.reg.2014-05-26-072101.471.log": appears incomplete File "C:\Users\Brad\AppData\Local\Xmarks\xmarks.log": appears incomplete File "C:\Users\Brad\AppData\Roaming\CrashPlan\log\ui.log.0": appears incomplete 5/27/2014 10:22:24 PM: Comparing Duplication of Brad on FantomHD (N:) File "C:\Users\Brad\ITunes\Music\iTunes\iTunes Media\Music\Alabama\1993 - Cheap Seats (320 kbps)\04 - On This Side Of The Moon.mp3": didn't compare File "C:\Users\Brad\ITunes\Music\iTunes\iTunes Media\Music\Bon Jovi\Have A Nice Day\04-bon_jovi_-_who_says_you_cant_go_home-msc.mp3": didn't compare File "C:\Users\Brad\ITunes\Music\iTunes\iTunes Media\Music\Boston\Third Stage\05 My Destination.mp3": didn't compare 5/27/2014 10:38:37 PM: 3 execution errors Completed: 10666 files, 25.8 GB Performance: 1499.7 MB/minute (1395.2 copy, 1624.3 compare) Duration: 00:38:11 (00:02:37 idle/loading/preparing) 5/27/2014 10:38:38 PM: Script "Duplicate Brad" completed with 3 errors I've been using Retrospect for about 6 years. I have seen backup sets get messed up every now and then but never duplications. They have always been rock solid.
  9. James Harris

    Compare Errors

    Since going to 9, I get file compare errors on just about every backup that I do, Any ideas on how to fix this? File "C:\Users\Brad\ITunes\Music\iTunes\iTunes Media\Music\Heart\Dog and Butterfly\7 Nada One.mp3": didn't compare
×