Jump to content

GerryRigney

Members
  • Content count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GerryRigney

  • Rank
    Occasional Forum Poster
  1. GerryRigney

    Intermittent -1121 (unknown file system)

    Mailbox backup only (DB backup works fine) Like I say though, it's not every night but its enough to worry us. Thanks
  2. I see another post regarding 1121 error below but no resolution to it. We have 2 Exchange servers, who from time to time are experiencing this error. Have relicensed many times as users come and go reguluarly, it also cannot be a permissions thing as one day all mailboxes backup fine, the next day some of them don't. Some times once the 1121 error's start during a backup it will just run through the remainder of the users, log a 1121 error and then stop at the end. Other times it will backup some users, 1121 at some more then continue backing up the remainder of users without error. Seems random as to when and what users it happens at. If anyone has any ideas/ suggestions I'd appreciate it, if any more info is needed just ask. Thanks gR Exchange servers are 2003 SP2 Windoess Server 2003 x86 Retrospect 7.6.123
  3. GerryRigney

    Backup time increased by over 100%

    Hi I just foud out what caused this problem yesterday evening and our backup last night was back to normal. We're running VSE 8.5 on our servers, we always had the "scan files open for backup" option turned on but it turns out that up until patch 8 for VirusScan that option was ignored (at least for some backup software) We pushed patch 8 to all machines over the past month or so, never twigged that the increase in backup times coincided with the patch deployment. So we turned that option off yesterday and the backup ran as normal. As the option was previously ignored we're no worse off having it disabled now. Anyway, just posted this in case someone else experiences the same problem, I believe it affects more backup software than just retrospect. gR
  4. Hi I just foud out what caused this problem yesterday evening and our backup last night was back to normal. We're running VSE 8.5 on our servers, we always had the "scan files open for backup" option turned on but it turns out that up until patch 8 for VirusScan that option was ignored (at least for some backup software) We pushed patch 8 to all machines over the past month or so, never twigged that the increase in backup times coincided with the patch deployment. So we turned that option off yesterday and the backup ran as normal. As the option was previously ignored we're no worse off having it disabled now. Anyway, just posted this in case someone else experiences the same problem, I believe it affects more backup software than just retrospect. gR
  5. Just an update on this post in the hopes that the problem might ring a bell with someone . . . . We recently created a new backup set and did a full backup, after a week we had the new backup complete and last night was the 1st incremental backup to this new set. Unfortunatly, 9.30am this morning (starts at 10pm) it's still running. Looking at all the sets, the problem seems to be the creation of the snap shot for our biggest volume. It's the biggest volume (1.1TB of data). About 5GB of data changes and gets backed up and then it starts the snap shot. Snap shot is still running 12 hours later! Can anyone thing of a reason why this would suddenly have jumped 10 hours? Like I say, the amount of actual data being changed is always around the same. Thanks in advance for any thoughts you might have. I didn't want to go down the route of creating new sets but was was willing to if we had to, now seems even that won't solve the problem. Rgds Gerry
  6. GerryRigney

    Backup time increased by over 100%

    Retrospect 7.0 with all updates Windows Server 2003 We run a file backup every night with a different backup set for each night. It usually takes around 8 hours to run but for over a week now it's been more like 18. The same amount of data seems to be getting backed up and the performance also around the same (600MB/ M) The bulk of the extra time is in the idle/loading/preparing stage. From what I can see it's the snapshot part that's taking so long. I thought after a week of this they sets would be back on their normal performance but it's still happening. Is there any way to stop this other than greating new sets? I've tried repairing the cataloge but it's had no effect. Thanks for any help gR
  7. Retrospect 7.0 with all updates Windows Server 2003 We run a file backup every night with a different backup set for each night. It usually takes around 8 hours to run but for over a week now it's been more like 18. The same amount of data seems to be getting backed up and the performance also around the same (600MB/ M) The bulk of the extra time is in the idle/loading/preparing stage. From what I can see it's the snapshot part that's taking so long. I thought after a week of this they sets would be back on their normal performance but it's still happening. Is there any way to stop this other than greating new sets? I've tried repairing the cataloge but it's had no effect. Thanks for any help gR
  8. Just found this while looking into another problem, thanks Mayoff!
  9. GerryRigney

    Not enough application memory

    Hi Mayoff I am just downloading the trial now. Problem is the tapes are 40/80 DLTs and there is over 400GB to be backed up so if I have to start all the sets over (5 sets, mon, tue, wed, etc.) it will take weeks before I have them all set up. Also, if we upgrade and are unable to recover files from the old sets it will be a disaster! Any idea if this will work? Thanks again Gerry
  10. GerryRigney

    Not enough application memory

    If we do upgrade to 7.5, will our existing backup sets still work with it or will we have to start them all over again? Thanks
  11. GerryRigney

    Not enough application memory

    Well its worked fine for us up till now, I don't think there's any shortage of memory as Retrospect doesn't seem to be using too much in task manager. Anyone got any other ideas?
  12. GerryRigney

    Not enough application memory

    Hi All We are suddenly having a problem with one of our backups. Running Retrospect 5.15 on a win2k server. Every night the server backs up 5 volumes (incremental backup). Its gets as far as counting(?) the files its needs to copy for the 1st volume and then stops. The error in the operations log is "Not enough application memory". The machine has 2.5GB of RAM and plenty of free space on the OS drive. At the last attempt, there were 8814 files needed to backup (9.8GB) As a test I tried to backup the whole volume to a new set, again it counted all the files but stopped with the same error in the log (335616 files this time 339.4GB). As another test I tried to backup one of the other volumes on the server to a test set and it began backing up successfully. I have also restarted the server in case that was it. Can anyone shed some light? There seems to be very little reports of this error in the forums. Appreciate any assistance, if you need any more info please let me know. Rgds Gerry
  13. GerryRigney

    Location of operations log

    I was looking under admin/app data!! Thanks for the info and the link Mayoff. rgds
  14. GerryRigney

    Location of operations log

    Hi All I'm trying to get access to the operations log on a remote server. Problem is I could remote into it and start retrospect but then it'll be closed when I log out and the backup won't run. Is the operations log stored anywhere in the file system so I can remote onto it and copy it down? Thanks Gerry
  15. We had a similar problem. Full backup ran but log backup gave us an error for one of the stores. To resolve we switched on circular logging (then restarted the Exchange Info Store Service). Left it like that for an hour then switched off circular logging (andrestarted the Exchange Info Store Service). Then ran a full backup and then the log backups run ok. Not the exact same problem but might be worth a shot
×