H.Pralow

Hello, execution time for backups thru Linux clients is very long. I have noticed this problem for a long time but finally made up my mind to open a topic about it in the forum. These are the simple facts: - 12.07.16 23:03:09: Copying www on dev7 12.07.16 23:03:09: No files need to be copied 13.07.16 01:25:56: Snapshot stored, 772 MB 13.07.16 01:26:11: Comparing www on dev7 13.07.16 01:26:59: Execution completed successfully Duration: 02:23:49 (02:16:46 idle/loading/preparing) As you can see even if no files needed to be copied, the backup with this Linux box takes nearly 2 and a half hours where copying and comparing appearently only take a few minutes. It gets worse when there are actually files to copy. Is there a way to speed the execution up to mopderate speed so that backing up Linux boxes doesn't hog my nightly backup schedule? Linux client is 9.5.0.113 OS of the Linux box is 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Although this paricular client box (dev7) seems somehow extreme other Linux clients in my nightly backup plan are slow as well: - 12.07.16 22:06:17: Copying www on dev5 12.07.16 22:44:12: Snapshot stored, 373 MB 12.07.16 22:44:26: Comparing www on dev5 12.07.16 22:45:17: Execution completed successfully Completed: 22 files, 281,5 MB Performance: 234,6 MB/minute (146,8 copy, 582,4 compare) Duration: 00:39:00 (00:36:36 idle/loading/preparing) Here 36 of 39 minutes are spent idling/load/preparing and I assume, most of the time is needed to store the snapshot. Any idea to speed things up?

Good point. Taken! Thanks

I didn't do a rebuild, since the file, assuming it to be /Libary/Application Support/Retrospect/Catalogs/OKT_DEZ_2015.rbc is about 3.5 GB large and stores the catalag of 5 LTO-tapes. So I would expected a rebuild to run longer than a single night and thus I have delayed it until weekend. However last night's scheduled backup executed fine without an error, so perhaps the catalog file may not be corrupted ? I don't know. What I'm going to do is to keep an eye on that issue and if the error reoccurs, do a rebuild of the catalog.

The catalog is stored on the boot volume (Software RAIDED harddisk)

Have you tried to restart the Retro Engine ?

Hello everybody, this morning last night's backup presented the following error message to me: !Can't save Catalog File, error -644 ( chunk file damaged during access) Googling for that particular error didn't give a result. I only found some references to an error #-645 which might be related or not. However, these errors (-645( seem to refer to Retrospect for Windows whereas here, we have Retrospect Mac Version 11.5.3 (103) running on Mac OS X Server 10.7.5. What does the error mean an how do I salvage it? Thanks in advance Horst

Grroming is off since we are backing up to tape. I don't doubt the display looks normal, my question rather is: What are the rules that cause Retrospect to display certain backups in the panel and omit most others. But as long as I don't know these rules, I'm unable to interpret the displayed information. E.g. one cannot use the panel for a quick check if a certain backup executed successfully or not because most likely it isn't even displayed in the list. Documentation doesn't quite help with this.

Hi, I'm wondering what the "Past Backups" pane actually shows? (Please see the attached Scrennshot for clarification) Obviously there entries for all Sources that where visited by the last executed backup script, but anything older than that seems to be a matter of randomness: Before yesterday (which is Oct, 22) the next entry in the list is Oct, 17th and from that day online particular source gets listed, further back then a single entry for Oct, 9th and few entries from Oct , 02nd … but all without any recognizable sceme. What this panel definitely not does is listing all executions that happened in the past. For me the panel seems pretty useless since becuas of being incomplete, it doesn't allow me to check whether a certain backup run did execute on a particular day. To check for that, I still have to browse the execution log, which is pretty cumbersome due to its sheer size ... So could someone please enlighten me, what this panel is good for at all ? Note: I'm not talking about "Activities -> Past" ! This is Retrospect Mac Version 11.5.1 (104)