Jump to content

jpgillivan

Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jpgillivan

  • Rank
    Newbie
  1. jpgillivan

    Says Media Is Full - It Isn't

    I haven't had any backup set issues after updating Retrospect, rebuilding one specific catalog for a backup set I was having issue with, and spacing out the backup jobs. For me it seemed that the pattern was when there were multiple backup jobs running at the same time. This may be and issue do to the limitations of XP but I am unable to confirm or deny simply because we don't have Retrospect installed on a Server OS also. Since I updated, rebuild and rescheduled all at the same time I cannot say what corrected the issue but If I had to guess it was the overlapping backup job schedules.
  2. jpgillivan

    Says Media Is Full - It Isn't

    I went ahead and installed the Retrospect hot fix and the update to 7.6.2.101. Yes I know this violates my rule of only changing one thing at a time but if the issue gets resolved then I am ok with it at this time.
  3. jpgillivan

    Says Media Is Full - It Isn't

    XP has SP3 installed. Retrospect is version 7.6.111. Only one member in the backup set.
  4. jpgillivan

    Says Media Is Full - It Isn't

    4 drives in a RAID 5 config using highpoint rocketraid card. Partitioned to C and D. OS and retrospect on C. D used for backing up to. (snapshots are later replicated to other locations for redundancy). OS is Windows XP Pro. Retrospect is 7.6. Backup set is set to a max of 25GB. The computer being backed up has less than 10GB on it. I started the job manually last night and it ran without any issues. (note: I am changing the time of day that the scheduled script runs to see if that helps. ) As you can see the scheduled job used Execution unit 3 while the manually run one used unit 1. Maybe I have too much disk activity going on. The scheduled job looks like it ran ok until grooming. Why is it grooming if it is doing a recycle? I am also going to try changing the backup job to 'normal' and set grooming policy to "Groom to retrospect defined policy". Log from scheduled (failed) run: + Recycle backup using CORPAVS01 at 10/9/2011 10:00 AM (Execution unit 3) To Backup Set CORPAVS01... 10/9/2011 10:00:00 AM: Recycle backup: The Backup Set was reset - 10/9/2011 10:00:00 AM: Copying Local Disk (C:) on CORPAVS01 - 10/9/2011 10:26:55 AM: Verifying Local Disk (C:) on CORPAVS01 10/9/2011 10:33:39 AM: Grooming Backup Set CORPAVS01... 10/9/2011 10:33:46 AM: Groomed zero KB from Backup Set CORPAVS01. Media request for "2-CORPAVS01" timed out after waiting 2:00:00 10/9/2011 12:33:49 PM: Execution incomplete Remaining: 26290 files, 4.9 GB Completed: 7015 files, 3.6 GB, with 31% compression Performance: 147.2 MB/minute Duration: 02:27:06 (02:02:18 idle/loading/preparing) Log from manual run last night: + Recycle backup using CORPAVS01 at 10/13/2011 5:15 PM (Execution unit 1) To Backup Set CORPAVS01... 10/13/2011 5:15:27 PM: Recycle backup: The Backup Set was reset - 10/13/2011 5:15:27 PM: Copying Local Disk (C:) on CORPAVS01 10/13/2011 5:56:50 PM: Snapshot stored, 73.3 MB 10/13/2011 5:57:04 PM: Execution completed successfully Completed: 31315 files, 8.4 GB, with 33% compression Performance: 227.8 MB/minute Duration: 00:41:37 (00:04:10 idle/loading/preparing) - 10/13/2011 5:57:09 PM: Verifying CORPAVS01 10/13/2011 6:02:14 PM: Execution completed successfully Completed: 31315 files, 8.4 GB Performance: 1740.6 MB/minute Duration: 00:05:04 (00:00:10 idle/loading/preparing)
  5. jpgillivan

    Says Media Is Full - It Isn't

    I am experiencing the same issue, however my storage space is internal raid drives. My retrospect is checking the box to "skip this member". If I uncheck the box I can re-run the backup job and it works ok. This issue is random, it does not do it all the time. It randomly chooses a backup set to error out on. No rhyme or reason. Any suggestions?
×