Search the Community
Showing results for tags 'backups'.
Found 4 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 11.5.0.139 (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.
-
can't open the Retro.Config (6.0) file, error -24203 (not a chunk file or badly damaged)
Retro old school 6 posted a topic in Retrospect 6: Desktop, Workgroup and Server for Mac OS X
Hello All, I'm hoping someone can help me out with ye old ver 6 of Retrospect? I was getting this error: Sorry, can't open the Retro.Config (6.0) file, error -24203 (not a chunk file or badly damaged) I was told from Retro tech that the .pref file is corrupt. (I do not have a copy of .pref file either other wise I would just replace) I tossed it out and Retrospect is now working but I lost all my Scripts to my Backups. I still have the Databases (Backup Set Catalog files) I just can't access them. I back up to DVD and have the DVD's The Backups are client Graphic Design files not a backup of a computer or Server. My question is does anyone know how to remake scripts to see my Backups? Thanks Chris- 5 replies
-
- 1
-
-
- error -24203
- Scripts
- (and 2 more)
-
I have run into what I think is a new poblem with 10.2.0 (201) where I can't retrieve backups on a media set. It's a disk media set, and has a bunch of backups. I want to copy off one backup per month for 2012, so I go to the media set and select all the first-of-the-month backups in 2012 to set up for the copy. All the "retrieve" "jobs" fail. I verified the backup set. OK. I finally tried retrieving the backups one at a time, and it worked fine. If I tried to do more than one at a time, i would always fail. Log lof failing jobs ooked like this: + Executing Retrieve Backup at 8/31/13 (Activity Thread 1) From Backup Set v9_vm3_last... !Trouble writing files, error -1101 ( file/directory not found) Can't retrieve Snapshot for session vm3, Local Disk (C:), 12/3/12, error -1101 ( file/directory not found) 8/31/13 11:15:47 PM: Execution incomplete Completed: 1 files, 0 B Performance: 0 MB/minute Duration: 00:00:11
-
Past backups display incorrectly after New Media backup.
twickland posted a topic in Retrospect bug reports
Running 10.1.0 (221), I just performed a new media backup, creating Media_Set [010] in the process. As expected, the previous media set, Media_Set [009] still appeared in the media set listing. However, although the information on the Summary and Members tabs then displayed correctly for both of these media sets, the Backups tab for Media_Set [010] also displayed all of the backups belonging to Media_Set [009]. (Happily, the Backups tab for Media_Set [009] did not display any backups belonging to Media_Set [010].) Furthermore, in the Past Backups window, all of the listed backups, whether they had actually been performed to Media_Set [009] or to Media_Set [010], now all displayed as having been performed to Media_Set [010]. I didn't try anything else at this point, but rather quit and relaunched the console. I was relieved to see that all of the information about past backups in the Past Backups and Media Sets windows now displayed with the correct media set, so it appears that this bug is only cosmetic. With v10.1 (221), you seem to have made some changes in the way the console polls the engine, because the console now seems to populate more quickly with complete information. Perhaps the above bug was introduced at the same time? (I don't recall having encountered it with previous versions.)
