joelande Posted April 27, 2009 Report Share Posted April 27, 2009 (edited) I cannot get a Copy Media Set script to execute without error, and the logs don't indicate what went wrong. What can I do. I have tried this with several Media Sets over several days and I have about a 90% failure rate: + Executing Archive Staff HHS at 4/27/2009 11:11 AM (Execution unit 1) To Media Set Archive... 4/27/2009 11:11:46 AM: Transferring from Staff Data HHS 4/27/2009 12:40:29 PM: Execution completed successfully Completed: 719401 files, 150.5 GB Performance: 1788.3 MB/minute Duration: 01:28:42 (00:02:32 idle/loading/preparing) 4/27/2009 12:40:29 PM: Verifying Archive [color:red]4/27/2009 1:51:22 PM: Execution completed successfully Remaining: 19689 files, 770.0 MB[/color] Completed: 699712 files, 150.0 GB Performance: 2221.2 MB/minute Duration: 01:10:52 (00:01:45 idle/loading/preparing) SMTP: opening addr 10.201.0.202 I don't see the client crash (well, sometimes I do, but even if it doesn't crash, I get the failures). Notice on the log above it says the script "Execution completed successfully" but there are a number of files remaining. I posted about this earlier, but didn't get a response. Edited April 27, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 27, 2009 Report Share Posted April 27, 2009 Is this verify part of a different verify script or is it the verify step included with the copy script? Retrospect does have the ability to not re-verify data already verified when using a verification script. Incremental verification. The log is clearly giving bad information. It should never say successful in this example. I have logged but 22019 for this problem. Does a scripted verify work or report the same thing? Make sure the options are set to verify the entire media set. Quote Link to comment Share on other sites More sharing options...
joelande Posted April 28, 2009 Author Report Share Posted April 28, 2009 It is a single script that (originally) does this: Copy Media SetAll FilesCopy backupsMedia verificationMatch source Media Set to destination Media SetDon't add duplicate files to the Media Set I run it manually during the day when nothing else is happening on the backup server. I also have tried the script, disabling each of these options in turn, on the assumption that it would "simplify" the process, and try to make it go faster (I mean a Finder level copy goes way faster, I realize that there are some error checks going on, but performance was shockingly slow even after disabling nearly every option): Match source Media Set to destination Media Set Don't add Duplicate files to the Media Set I have never disabled the Media verification checkbox, as if I do that, I may as well just use the Finder, right? And with as much as I trust this software, I want to do all the verification I can... The log above comes from my "simplified script", which turns off the "Match source Media Set to destination Media Set" and "Don't add duplicate files to the Media Set" options and has the "Copy backups" and "Media verification" turned on. But I get similar errors and results regardless as to whether those options are on or off. Does a scripted verify work or report the same thing? Make sure the options are set to verify the entire media set. I am not sure what either of those questions are asking. I presume it is regarding creating a script that does nothing other than verify? I don't know anything about that - how or why you would set it up. Hopefully there will be some detailed documentation at some (soon) point in time. Basically now is learning by trial and error, and making assumptions about how things are supposed to work and be used. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 28, 2009 Report Share Posted April 28, 2009 (edited) The log shows that your remaining items are part of the verify operation and not the copy phase. Either a cosmetic bug is making it appear that verify is not finishing all the way, or the verify is finishing but is giving the wrong file count or verify is failing to finish reading your files. By using a verification script, you can do a verification of the media after the copy operation is done. We can then 1) view the log to see if it finishes. 2) See the total file count of the verify. 3) Look for errors. Edited April 28, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
joelande Posted April 28, 2009 Author Report Share Posted April 28, 2009 So in the Copy Media Set script, should I turn off the Media verification option? And then after the copy is done, create a script that verifies the archive? I created a verify script to see what was involved. Looks like you simply select a Media Set to verify. I guess I am confused how that would work, I always assumed a verify would compare one source to another. What is it verifying against? I assume I would point the verify at the destination of the Copy Media Set script? Does it matter if other data (from other Copy Media Set scripts) is stored in the destination? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 28, 2009 Report Share Posted April 28, 2009 You can normally leave verify on. I want to know what happens if you do a verify now, since the prior verify failed. The verify uses the MD5 digest to read your media and check it for errors. It doesn't matter what data is saved to the media. A verify is an extra safety step and it is used for troubleshooting problems like this. Quote Link to comment Share on other sites More sharing options...
joelande Posted April 28, 2009 Author Report Share Posted April 28, 2009 (edited) OK - I had started another copy operation, but apparently the console crashed. There is now no indication of what that script did or didn't do. I am restarting the server, and then I will execute a verify script. Man, I wish there was documentation. There is an option "Verify entire Media Set" Not sure what that does, or what the consequences of not checking it are (it is not checked by default, so I left it unchecked). Edited April 28, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
joelande Posted April 28, 2009 Author Report Share Posted April 28, 2009 Console crashed during verify step. Will restart and try again. THis is getting frustrating. I could do a Finder level copy and be done with, and probably have more confidence in it despite the lack of verification. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 29, 2009 Report Share Posted April 29, 2009 Another thread gave me an idea about this. Have you tried with compression turned off during the copy operation? Quote Link to comment Share on other sites More sharing options...
joelande Posted April 29, 2009 Author Report Share Posted April 29, 2009 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 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 29, 2009 Report Share Posted April 29, 2009 So the verify script is reporting the same thing as the verify after copy. You may be able to clean this up with a catalog rebuild of this media set. Quote Link to comment Share on other sites More sharing options...
joelande Posted April 29, 2009 Author Report Share Posted April 29, 2009 (edited) 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 Edited April 29, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 29, 2009 Report Share Posted April 29, 2009 You get the problem doing a verify of "Archive" so that would be the one to rebuild. Quote Link to comment Share on other sites More sharing options...
joelande Posted April 29, 2009 Author Report Share Posted April 29, 2009 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 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 29, 2009 Report Share Posted April 29, 2009 Have you checked out the training video? http://video.emcinsignia.com/retrospect8/catalog-rebuild-of-disk-media-set.mov Quote Link to comment Share on other sites More sharing options...
joelande Posted April 29, 2009 Author Report Share Posted April 29, 2009 Perfect - thanks! Quote Link to comment Share on other sites More sharing options...
joelande Posted April 29, 2009 Author Report Share Posted April 29, 2009 Then I presume run the verify again? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 29, 2009 Report Share Posted April 29, 2009 Yes. Also look at the total file count after the rebuild does it match the verified amount? Quote Link to comment Share on other sites More sharing options...
joelande Posted April 29, 2009 Author Report Share Posted April 29, 2009 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? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 29, 2009 Report Share Posted April 29, 2009 Yes, Retrospect is pointing to the new catalog file. You can delete the old catalog. Quote Link to comment Share on other sites More sharing options...
joelande Posted April 30, 2009 Author Report Share Posted April 30, 2009 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. Quote Link to comment Share on other sites More sharing options...
joelande Posted April 30, 2009 Author Report Share Posted April 30, 2009 (edited) 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 Edited April 30, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 30, 2009 Report Share Posted April 30, 2009 The verify script contains an option to only verify new items. You may need to change that option. See screenshot Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 5, 2009 Report Share Posted May 5, 2009 about Post#121606 can you take a screenshot of the Media Sets -> Backups. Also, if you can post a screenshot of the Backups listed when you select 'Retrieve..' This will give me a better idea what is going on with problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.