Jump to content

joelande

Members
  • Posts

    72
  • Joined

  • Last visited

joelande's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Could somebody please tell me the reason that files would be left "remaining" during a Copy Media Set operation? Isn't it simply moving the Retrospect media set file to the destination? As, you can see form the screen shot, nearly every Copy Media Set script failed. All of them for the same reason - remaining files, here is one log excerpt: 6/1/2009 5:21:02 AM: Verifying Archive 6/1/2009 5:26:20 AM: Execution completed successfully
  2. Its not the drive, its this crappy software.
  3. While the word "error" is noted in your Log entry, did it in fact fail? What's on the destination Media Set? Can you Restore the data? Perhaps it's the log entry that's trashy, and not the actual operation? Dave Who the $%^& cares? This is backup software. You either trust it or not. I attempted to run a number of Copy Media Scripts all over the weekend to make room on my staging drive. 8 out of 10 failed after repeated attempts. They all fail with a number of "remaining items" Often times the client would crash.
  4. Source: Internal Hard Drive on xServe Destination: Western Digital FireWire 800 2 TB hard drive
  5. Error: + Executing Archive FMP Data at 5/28/2009 1:06 PM (Execution unit 1) To Media Set Archive... 5/28/2009 1:06:25 PM: Transferring from FMP Data 5/28/2009 5:12:00 PM: Execution completed successfully
  6. And of course it fails with an error. And on top of that, while trying to troubleshoot, I tried moving the column headings to make them wide enough to read the names of the script names, and the whole column width goes wacko - the column width went extremely wide. What a piece of trash.
  7. I just don't get this product. I started a Copy media Set action at 1:00 PM. It is set to copy All Files, and Media verification and Match source Media Set to destination Media Set are selected options. The Media Set in question has 6 backups in it. There are 1,930 files, and it is 1.8 GB in size. It is now 3:30, and it still hasn't completed.
  8. OK - I ran a verify on the Archive this morning, but it smells fishy, because it didn't take long, and there is no indication of how many files were "verified". Yesterday it took several hours. + Executing Verify Archive at 4/30/2009 8:45 AM (Execution unit 1) 4/30/2009 8:45:46 AM: Verifying Archive 4/30/2009 8:47:47 AM: Execution completed successfully Duration: 00:02:00 Total duration: 00:02:01 SMTP: opening addr 10.201.0.202
  9. Catalog rebuild done: + Executing Recatalog at 4/29/2009 1:17 PM (Execution unit 1)%s at 4/29/2009 1:17 PM (Execution unit 1)] To Media Set Archive... 4/29/2009 9:03:15 PM: Execution completed successfully Completed: 6822291 files, 991.5 GB Performance: 2244.6 MB/minute Duration: 07:43:22 (00:11:07 idle/loading/preparing) SMTP: opening addr 10.201.0.202 I will begin the verification tomorrow. Nightly backup scripts running now.
  10. I will check. While this is "cooking", when it is complete, do I delete the old .rdc catalog file? Will retrospect know to use the new catalog file moving forwards?
  11. You may have missed my edit - I think you replied before I was done - so can you guide me through what the procedure is for the rebuild, I don't understand what it is doing, and what it is prompting for. - sorry to bug with this, I would read the docs if they were available: I am getting similar failures on most Copy Media Set scripts I have (I have several Copy Media Set scripts, each using a different Media Set source on the same hard drive going to another locally attached drive, but a single Media Set destination). For example: Copy Media Set script A: Media Set HardDrive1:SetA copied to HD2:SetArchive Copy Media Set script B: Media Set HardDrive1:SetB copied to HD2:SetArchive Copy Media Set script C: Media Set HardDrive1:SetC copied to HD2:SetArchive Copy Media Set script D: Media Set HardDrive1:SetD copied to HD2:SetArchive In anticipation, I started to do a Catalog Rebuild on the "Archive" Set, but was thorwn buy the dialog prompts, not understanding what they meant. After being prompted to chose a type (which I thought was strange, because the Media Set was already selected and it was a Disk type), I chose "Disk". It then prompted to Add Member..., at which point I wasn't sure what it was asking. - Do I select the root, the Retrospect folder, the Archive folder, or the 1-Archive folder
  12. Which one? All of them? I am getting similar failures on most Copy Media Set scripts I have (I have several Copy Media Set scripts, each using a different Media Set source on the same hard drive going to another locally attached drive, but a single Media Set destination). For example: Copy Media Set script A: Media Set HardDrive1:SetA copied to HD2:SetArchive Copy Media Set script B: Media Set HardDrive1:SetB copied to HD2:SetArchive Copy Media Set script C: Media Set HardDrive1:SetC copied to HD2:SetArchive Copy Media Set script D: Media Set HardDrive1:SetD copied to HD2:SetArchive In anticipation, I started to do a Catalog Rebuild on the "Archive" Set, but was thorwn buy the dialog prompts, not understanding what they meant. After being prompted to chose a type (which I thought was strange, because the Media Set was already selected and it was a Disk type), I chose "Disk". It then prompted to Add Member..., at which point I wasn't sure what it was asking. - Do I select the root, the Retrospect folder, the Archive folder, or the 1-Archive folder
  13. I am not using any compression. I finally got a verify script to complete. You won't like the results: - It reports: "Execution completed successfully" - Yet has files remaining: Remaining: 87030 files, 4.3 GB + Executing Verify Archive at 4/28/2009 1:21 PM (Execution unit 1) 4/28/2009 1:21:11 PM: Verifying Archive 4/28/2009 9:05:59 PM: Execution completed successfully Remaining: 87030 files, 4.3 GB Completed: 6735261 files, 984.7 GB Performance: 2232.0 MB/minute Duration: 07:44:48 (00:13:03 idle/loading/preparing) Total duration: 07:44:49 (00:13:03 idle/loading/preparing) SMTP: opening addr 10.201.0.202
×
×
  • Create New...