Jump to content

Richy_Boy

Members
  • Content count

    518
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Richy_Boy

  1. I've been using 7.7.562 for a while now after migrating to a new HP server using SSD disks for application and catalog files. The server is running sweet as a nut. However! I'm forever getting Retrospect problems - 1) Grooming just doesn't work. I have rebuilt the catalog several times and have even binned the backup set and setup a new one, only for that to start failing. This results in the backup set growing bigger and bigger, which impacts offsite duplication times. The only way I can reduce the size of the backup set is to manually delete backups one by one, which is unmanagable. The 'repair catalog' option takes about 10 seconds and seems to do very little in the way of fixing the catalog... + Executing Groom DR at 08/01/2012 19:00 (Execution unit 1) Grooming Backup Set DR (Non CORE)... Groomed 31.9 GB from Backup Set DR (Non CORE). Grooming Backup Set DisasterRecovery1... Groomed zero KB from Backup Set DisasterRecovery1. Grooming Backup Set DisasterRecovery1 failed, error -1101 ( file/directory not found) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. Can't compress Catalog File for Backup Set DisasterRecovery1, error -1 ( unknown) 08/01/2012 19:40:55: 2 execution errors Duration: 00:05:14 (00:00:01 idle/loading/preparing) + Executing Groom DR at 06/01/2012 19:00 (Execution unit 2) Grooming Backup Set DR (Non CORE)... Groomed zero KB from Backup Set DR (Non CORE). Grooming Backup Set DisasterRecovery1... Grooming Backup Set DisasterRecovery1 failed, error -2241 ( Catalog File invalid/damaged) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. Can't compress Catalog File for Backup Set DisasterRecovery1, error -1 ( unknown) 06/01/2012 19:25:16: 2 execution errors Duration: 00:17:56 (00:03:26 idle/loading/preparing) + Executing Groom CORE servers > NAS at 07/01/2012 14:00 (Execution unit 2) Grooming Backup Set DomainCont... Groomed 4.7 GB from Backup Set DomainCont. Grooming Backup Set FileserversBackups... Groomed zero KB from Backup Set FileserversBackups. Grooming Backup Set FileserversBackups failed, error -1101 ( file/directory not found) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. Can't compress Catalog File for Backup Set FileserversBackups, error -1 ( unknown) Grooming Backup Set CVSServers2011... Groomed zero KB from Backup Set CVSServers2011. Grooming Backup Set DatabaseOnly... Groomed zero KB from Backup Set DatabaseOnly. Grooming Backup Set DatabaseServ... Groomed 9.9 GB from Backup Set DatabaseServ. 07/01/2012 17:05:14: 2 execution errors Duration: 00:24:25 (00:12:13 idle/loading/preparing) 2) Occasionally I get a 'building snapshot' hang, where it'll be right at the end of the proactive backup process and it'll stop dead. Retrospect cannot backup any further users and I cannot manually stop the snapshot/backup by using the 'stop' button in the GUI. The only way I can get backups moving again is by crashing the application and launching it again, where it'll carry on OK again. It's not the same client that it happens on... Is anyone else seeing these issues? Richard
  2. Richy_Boy

    inplace upgrade problem

    There's a file called Config77.dat which contains all those settings. There is also Config77.bak which is a copy of that file, which I guess was a work-around put in place to recover when the config file corrupted (which it used to do often!). If you have a backup of that file, copy it into the All Users or ProgramData/Retrospect folder and restart Retrospect and everything should be back as it was. If you don't have a copy of that file, then you need to rebuild everything from scratch... Richard ps. I should add.. most people who have been using Retrospect for a while back this 'Retrospect settings' directory up religiously.
  3. Richy_Boy

    Any Upgrades In The Offing?

    There was a Retrospect roadmap knocking about somewhere last year, but I don't know how the Roxio > Retrospect Inc thing has impacted those plans. It would be good to have a clear roadmap and reassurance that Retrospect for Windows is still a product going forward and it's not returning to its Mac-only roots? 7.7 has been out ages and there are so many bugs and usability/design problems it can be quite frustrating at time. Rich
  4. Although I don't run the Mac version of Retrospect, I agree that when backing up a Windows machine (Proactive, for example) it will be brought to its knees when the disk scan takes place before and after the actual backup. Pushing the encryption/compression to the client would be great in a desktop/server environment where there is an 'out of hours' window where the users are not impacted. Rich
  5. Richy_Boy

    A few issues on 7.7.562

    Same error: + Executing Grooming at 17/01/2012 12:03 (Execution unit 4) Grooming Backup Set DR (Non CORE)... Groomed 8.6 GB from Backup Set DR (Non CORE). Grooming Backup Set DR (Non CORE) failed, error -1116 ( can't access network volume) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. 17/01/2012 12:49:16: Execution incomplete Duration: 00:46:07 (00:06:37 idle/loading/preparing) Freshly rebuild catalog file which was groomed today. The RS Server is backing up other laptops and moving snapshots at the same time, so the NAS target isn't dropping offline or anything - just seems a generic error. Rich
  6. Richy_Boy

    A few issues on 7.7.562

    Hi MasterCam, thanks for your reply. The Grooming fails even after a rebuild and I have the catalogs on the OS SSD disk and the backups sets on a SMB NAS box. I might have to slice up my Backup Sets more, although even that's a huge manual effort in Retrospect! Rich
  7. Ah, it's cleared now: Apparently, an engineer put the settings in by accident as the code behind this is already in place. However, the two aren't linked, so the tick box does nothing... it's remained in place for several releases now - quality control anyone?! Rich
  8. Yup, not supported in RS, even though there are options in the settings to do so. I would take a screen shot, but RS has hung as I've tried to look at a Backup Set which has a lot of data in it. *sigh*. Funnily enough this used to be supported 'back in the day', but it was removed. Users have been calling for it's return for years, but I guess they have more serious problems to deal with first. Power Management is important to businesses now... Rich
  9. Richy_Boy

    Config77.dat File Getting Corrupted

    I agree, we used to get this A LOT. However, since moving to a new backup server, running soley on SSD disks I haven't seen it once. I do religiously backup the RS config files every night, as having been through the pain of starting from scratch a few times now, I'd rather not do it again! There's lots of stuff that RS does which is 'old school', years of under resourcing has lead to that.. Rich
  10. Richy_Boy

    How To Monitor Grooming

    Fred, just be gratful you groom actually completed successfully! I constantly get these: + Executing Groom DR at 26/09/2011 11:58 (Execution unit 3) Grooming Backup Set DR (Non CORE)... Groomed zero KB from Backup Set DR (Non CORE). Grooming Backup Set DR (Non CORE) failed, error -1101 ( file/directory not found) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. Can't compress Catalog File for Backup Set DR (Non CORE), error -1 ( unknown) Grooming Backup Set DisasterRecovery2010... Groomed 276.3 MB from Backup Set DisasterRecovery2010. Grooming Backup Set DisasterRecovery2010 failed, error -1116 ( can't access network volume) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. Can't compress Catalog File for Backup Set DisasterRecovery2010, error -1 ( unknown) 26/09/2011 12:28:31: 4 execution errors Duration: 00:23:46 (00:01:03 idle/loading/preparing) I recreate the catalog from scratch, it'll groom once then throw this same error. What spec server and disks are you using for Retrospect and your catalog files? I switched to using an SSD disk to hold the catalogs and it's muuuuch faster now. Rich
  11. Richy_Boy

    Uir On Win 2008 Server?

    Ah, I got it working in the end. Needed to install the SP1 and security patch into .NET 1.1 before it would work it seems. Come on ROXIO, time to update some of this software! (including the client count down pop-up in Vista/Win7!) Rich
  12. Hi, I'm trying to setup UIR on our new backup server and whenever I try and install UIR it seems to want .net 1.1 installed - which is a touch out of date! Are there any instructions around explaining how to force it to install with .net 2.0 or 4.0 on IIS7? Cheers, Richard
  13. Richy_Boy

    Uir On Win 2008 Server?

    Thanks Phil, however, I have that installed that and have downloaded and installed .NET 1.1 (and enabled it). I still can't get the URL to work. Does anyone (Retrospect maybe??) have step-by-step instructions on how to get this working on Windows 2008 R2 Server? I currently get a blank screen when I hit the specified URL When I click around the Application options I get errors due to using .Net 1.1. I have tried reinstalling .net 1.1. If I set to .Net 3/4 I don't get these errors, but of course the user recovery doesn't work. It's about time this was updated to support a modern server..! Thanks, Rich
  14. Hi Roxio; I'm trying to perform a task where I'd like to break out SOME of the laptop snapshots into a new backup set to reduce the size of the catalog file. There are some features which help with this, but I'd like to use the 'client folder tree' to control which groups of laptops are migrated, rather than a list of ALL clients within the original backup set. Can this be a feature that's added at some point? Thanks, Richard
  15. Ah, I think I found the problem and it was selector based - running a backup now to see if the problem is resolved. Basically, I told it to not backup the folder called 'temp', however, this seemed to match with the folder 'document templates' as I only had 'match pattern' selected, rather than 'match exactly'. I was assuming if I wanted to ignore any folders called templates, temp, temporary etc I'd use 'temp*' as the folder name, so this option seems overly complicated. Fingers crossed my backup is complete! I had best go through all my other Selectors to make sure I haven't made the same mistake! Live and learn... Rich
  16. Well, I thought it was all going well. Haven't changed my backup selectors for ages as frankly our fileserver one is basically *copy all* except folders called 'temp'. I had a call form our HR team today as someone deleted a file by accident. When I looked to restore the file a number of files were not backed up that were present in the folder. It had, however, backed up two of the 15-20 files. These files are a mixture of .dot and .doc template files, so I'm confused why their not backed up and more worried about what else isn't being copied that I have assumed has been for ages. So, any ideas what has gone on? I don't have any erors backing up this server, the selector is straight forward and the backup set seems healthy. I'm running a backup set integrity check now and will rebuild the catalog as I'm assuming RS 'thinks' it has the files. Ugh... For tonight, I might backup to a new Backup Set, just to try and work around a few potential culprits, but it terrifies me to think what else isn't actually being copied! Rich
  17. So, I migrated RS to a new beefy server and copied across all the configuration which was working perfectly well. As part of the migration I upgraded to the latest version, but have since had endless grooming problems on our larger Disaster Recovery and Client weekly grooms. This is causing havoc with my offsite storage as I only have 2TB disks to take the backup sets out of office, without grooming the duplication script fails (outside of RS). Has anyone else seen this in 7.7.562? Has there been a fix or a work around at all, as this is really causing me problems. After the error RS tells me to rebuild the catalog files, which works fine, then on the next groom I get exactly the same error. i.e. + Executing Groom Clients > NAS at 03/08/2011 10:17 (Execution unit 1) Grooming Backup Set Desktops... Grooming Backup Set Desktops failed, error -2241 ( Catalog File invalid/damaged) You must recreate the Backup Set's Catalog File. Or sometimes: + Executing Groom DR at 29/07/2011 19:00 (Execution unit 2) Grooming Backup Set DR (Non CORE)... Groomed 13.9 GB from Backup Set DR (Non CORE). Grooming Backup Set DR (Non CORE) failed, error -1116 ( can't access network volume) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. Can't compress Catalog File for Backup Set DR (Non CORE), error -1 ( unknown) I have also changed the backup sets to use the IP of the central NAS storage box in case of a DNS issue.. so I'm not sure why all of a sudden if can't access the volume!? (note: only when grooming do I see this error, it can run an entire DR backup of out network without a single error of this type) Help! Richard
  18. Richy_Boy

    A Moment Of Praise

    Ok, the moment of praise is slowly slipping away - sorry Roxio. Since upgrading to the latest RS Multi Server build I keep getting 'can't access network volume' when backing up some servers or (even more annoyingly) when grooming large backup sets. + Executing Grooming at 11/07/2011 09:47 (Execution unit 1) Grooming Backup Set DisasterRecovery... Groomed 30.3 GB from Backup Set DisasterRecovery. Grooming Backup Set DisasterRecovery failed, error -1116 ( can't access network volume) You must recreate the Backup Set's Catalog File. See the Retrospect User's Guide or online help for details on recreating Catalog Files. 11/07/2011 10:44:07: Execution incomplete Duration: 00:55:49 (00:03:09 idle/loading/preparing) This is odd and will be a pain to diagnose as I have migrated both RS build and physical server at the same time, although the network and backup NAS destination haven't changed. I've removed hostnames and replaced with static IPs and it's still throwing this error. I'd expect this error on laptops when users get fed up with RS Client thrashing the disk to death during a scan, but not with servers that are backing up overnight. Ugh.. I should point out I didn't get ANY of these errors under the old build/physical server. I'll take a look at Ethernet drivers next, although I'm on the latest HP supported versions as it is. Has anyone else seen this? Rich
  19. So, I usually ask about problems or rant on about crashes and backup failures, but it's time for a change. I recently migrated from an old P4 based server to a DL120 with plenty of RAM and CPU grunt. I installed the very latest build of RS Multi Server and put in my license codes for the value add-on pack I bought. I'm running the OS/Application and catlog files off an SSD disk, which is soooo much faster. Hopefully I don't hit any reliability problems... The experience thus far has been a breath of fresh air. I can now repair catalog files (!) which used to always fail, requiring a full rebuild which took hours, if not days at times. Nothing has failed or crashed, although I still get those odd 'pauses' where the application seems to freeze, but then comes back to life after a minute or so. I've had a few servers failing to backup with 'backup client reserved' issues, but hopefully that'll iron itself out (it's probably due to there being two RS servers running at the same time - see below!) So Roxio/Dantz, whoever - I see progress, thank you! The only small snag, which was (duh!) user error was to leave the old physical RS server running and just shutdown the RS Server application. This was fine during testing, but when the first script kicked off the 'auto launcher' fired up the old version and I started getting catalog sync errors from the new server. All has been fine after stopping the auto-launcher service and repairing (yes, repairing) the catalogs files. I know this is tempting fate... Richard
  20. Richy_Boy

    Questions Re. Initial Install: Location Of Catalogs

    No problem.. I've edited my post to make it clearer.. If they don't get swapped, then expected BackupSet'x' will not be available, so the backups will not take place. So you could set BOTH week scripts to run every week and set the script to timeout after a hour if it can't find the NAS box online. So, in the scenareo of a NAS device not being swapped, whatever NAS box is available will be backed up to. Hope that makes sense...? Make sure you set the script to time out after a set time though, otherwise the scripts will be queued up and it'll be mayhem when it finally becomes available! Rich
  21. Richy_Boy

    Questions Re. Initial Install: Location Of Catalogs

    I think you're looking at this wrong. If you run two NAS boxes and rotate, you ideally want two backups sets (one per week) and schedule/script them to run alternatley. i.e. Script1 > BackupSet1 = week 1 = NAS1... Script2 > BackupSet2 = week 2 = NAS2. Script1 > BackupSet1 = week 3 = NAS1 Script2 > BackupSet2 = week 4 = NAS2. That way, each will have their own catalog file so nothing will get out of sync. Personally, I have my catalogs on a SSD disk in my server (for brute speed) and only take the backup sets offsite via External USB disks. In a DR scenareo, a few ours rebuilding the catalogs is more than acceptable. I backup to a NAS box, like you, but use the build-in rsync copying process to duplicate the changes to all my backup sets to external USB disks (which are taken offsite and rotated). Anyway, if you're rotating NAS devices on a weekly basis, you need a backup set for each week/NAS. Hope that helps, Rich
  22. Richy_Boy

    Questions Re. Initial Install: Location Of Catalogs

    You can just stop the RS Server, move the catlog file and then start it up again. When you access a backup set it'll ask for the location of the catalog files I think. I agree with Support though, building catalog files is a disk-intensive task which if you keep your backup sets on a NAS box (for example) will kill performance. Depending on what physical server you have, a better option would be to either slot in more disks just for calalogs or even hang off an external ESATA or USB2/3 drive. Also, for you info - if you have a backup set and no catalogs at all (i.e. a corrupt disk/failure) when you rebuild the catalog the RS Server asks you where you want to save them - which can be local disks or network storage. HOpe that helps? Rich
  23. Also.. being able to select multiple snapshots to delete them is also a must. Users have been asking for this feature for years now as it'll save hours of Selecting > Forget.... wait... Selecting > Forget.... wait... Rich
  24. Richy_Boy

    Debian Linux Client-Installer

    Mayoff, considering Ubuntu is now the most popularly downloaded Disto, maybe it's time to formally support it and have a 'Roxio' built and supported client available on your site. There's insructions on the Dantz forum if you guys need help (sorry, that was cheeky!) It does seem odd that people have been aksing for this for years now, it reletively easy to do, yet EMC/Roxio seem to make life difficult for the end-users rather than release a ready made .deb file. wf10 - I have uploaded my version of te client (7.6.100) here -> http://www.thefozreport.co.uk/Downloads/tabid/195/Default.aspx PLEASE NOTE: THis is not supported in any way by me.. but I use it at work without problems. Rich
  25. Richy_Boy

    A Moment Of Praise

    OK, so it crashed during a huge snapshot transfer when trying to sort out the Disaster Recovery backup set grooming problem - this is going from bad to worse. Maybe this is the Retrospect of old and the hardware it was sitting on was making it feel a bit more snappy? Rich
×