Search the Community
Showing results for tags 'copy media set'.
Found 2 results
I have been manually copying my media sets that appear to have suffered from the problem described here: http://forums.retrospect.com/index.php?/topic/150511-nasty-bug-scheduled-copy-media-set-only-copies-fraction-of-data/ When I copied the media sets, I found that although the reported number of files and the size of the resultant media set looks correct, when I look at the target copy and "retrieve" the older backups, there is *nothing* there. This may be a more serious bug than that described in the previous report. I am running 18.104.22.168 (console and engine) I plan to try doing the copy via "copy backups" (and copy all backups) and maybe upgrade to 11.5.2, but there is nothing in the release notes that indicates that this has been fixed. This is new, bad, behavior not present in 10.5. I'll report back.
I have a Disk Media Set that causes Retrospect 10 to get stuck when it attempts to groom the set (411.5 Gb, 1,314,824 files). The media set is the one dedicated for the local server machine backup. It always gets stuck on the same file (happens to be a Retrospect catalog file for another media set). Verification of the Media Set shows no problem and I have done numerous Catalog rebuilds cause I have to kill the server to get un-stuck. So this weekend I used "Copy Media Set" to a new media set, using a rule that selected all files except the RS catalog files. I tested this rule first on a regular backup, and confirmed it was indeed working to exclude the catalog files. Problem is, the catalog files still got copied over to the new media set. So my questions to the forum is: Do rules work when doing a "Copy Media Set"? Is there a way to expunge the problem file from the existing media set while saving all the past backup history? Or do I just archive the Media Set and start over with a new one?