Guest Posted February 18, 2002 Report Share Posted February 18, 2002 Our architect's office uses a mac platform. We have an ethernet LAN with 12-15 users. Network consists of 100 base T network, G4/500 DP file server, sony DAT 20/40gig backup system with RETROSPECT 4.3 configured to do a compressed backup. Until last week our backups have worked perfectly. See enclosed extract from our log to see/understand our grief. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ? Retrospect version 4.3 autolaunch at 12/2/2002 11:59 PM + Advanced Driver Kit, version 1.8 + Retrospect Driver Update, version 2.1 + Recycle Backup using TAA Tuesday Backup at 12/2/2002 11:59 PM To backup set TAA Tuesday Backup… 12/2/2002 11:59:59 PM: Recycle Backup: the backup set was reset - 12/2/2002 11:59:59 PM: Copying Current Practice Data on Current Data HD 13/2/2002 02:34:20 AM: Comparing Current Practice Data on Current Data HD 13/2/2002 04:56:25 AM: Execution completed successfully Completed: 18192 files, 28.2 GB Performance: 199.2 MB/minute (193.9 copy, 204.8 compare) Duration: 04:56:26 (00:06:42 idle/loading/preparing) Restart at 13/2/2002 04:56 AM ? Retrospect version 4.3 launch at 13/2/2002 08:16 AM + Advanced Driver Kit, version 1.8 + Retrospect Driver Update, version 2.1 Quit at 13/2/2002 08:17 AM ? Retrospect version 4.3 launch at 13/2/2002 08:44 AM + Advanced Driver Kit, version 1.8 + Retrospect Driver Update, version 2.1 Quit at 13/2/2002 08:44 AM ? Retrospect version 4.3 autolaunch at 13/2/2002 11:59 PM + Advanced Driver Kit, version 1.8 + Retrospect Driver Update, version 2.1 + Recycle Backup using TAA Wednesday Backup at 13/2/2002 11:59 PM To backup set TAA Wednesday Backup… 13/2/2002 11:59:50 PM: Recycle Backup: the backup set was reset - 13/2/2002 11:59:50 PM: Copying Current Practice Data on Current Data HD 14/2/2002 07:30:01 AM: Script execution terminated at specified stop time. 14/2/2002 07:30:01 AM: Execution incomplete Remaining: 1554 files, 1.1 GB Completed: 17630 files, 28.8 GB Performance: 192.4 MB/minute Duration: 07:30:11 (04:57:02 idle/loading/preparing) xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx backup worked fine 0n feb13 with 28.2 gigs backed up in just under 5 hrs. which is acceptable. 14Feb. our data grew to 29.9 gig and timed out after 7.5 hrs. Increased time allocation to 8.75 hrs and still no joy. Sent a script manually over the weekend and timed out after 13.25 hrs.!!! Had an error message on screen 'error 24006' , can anyone explain the more than 300% jump in backup time and haw to solve it? Chris Pailthorpe Turner + Associates Architects L1 586 Crown Street, Surry Hills, NSW 2010 T 612 9690 2855 F 612 9690 2411 Link to comment Share on other sites More sharing options...
IrenaS Posted February 25, 2002 Report Share Posted February 25, 2002 There are three places to set schedules for a script in Retrospect. The scheduling options that allow you to set windows of time with options such as Wrap-up time are mainly for use with Backup Server Scripts. If you are running regularly scheduled Backup Scripts, which is what it sounds like, keep these set to "Always Active." 1. Special -> Preferences -> Execution -> Schedule. This is a global schedule that will affect all your scripts. Keep this set to "Always Active." 2. Automate -> Scripts. Select your script, click Edit -> Options -> More Choices -> Execute -> Schedule. This will look identical to the first schedule box, but it is specific to this script only. Again, I recommend setting this to "Always Active." 3. Automate -> Scripts, select your script, click Edit, then click Schedule. This is where you tell it when to execute. Configure this according to whatever schedule you wish. This should eliminate the time-out error. As for the increase in backup time, there are a lot of factorst aht can affect this, including matching and scanning, locating the media, and temporary or permanent performance problems (due to slow or busy network, device problems, etc.). Your log indicates that, of the total performance time, almost 5 hours (04:57:02) was spent idle/loading/preparing. This can indicate that the tape was full and Retrospect was sitting waiting for a new tape untill the script timed out. If you try an incremental backup, does it tell you that you need a new tape? If so, that's likely what caused the increase in backup time that you saw. Irena Solomon Dantz Tech Support Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.