Jump to content

Richy_Boy

Members
  • Posts

    518
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Richy_Boy

  1. This has been happening for years on my site and it's down to disk speed. Maybe disk fragmenting might help with overall disk performance when being scanned during the snapshot, all our new laptops comes with SSD's and you can't even tell when a backup is taking place with them.
  2. I agree ^ Also, in the selector you can specify to backup folders with the archive bit is set on the file/folder.. if you can write a script to find the names of folders, then you can equally make a script to set the archive bit on them? i.e. FolderA SubFolderA1 SubSubFolderA1a (archive set) SubSubFolderA1b SubFolderA2 SubSubFolderA2a SubSubFolderA2b FolderB SubFolderB1 SubSubFolderB1a (archive set) SubSubFolderB1b SubFolderB2 SubSubFolderB2a SubSubFolderB2b (archive set) Richard
  3. If you never want to back up data on additional drives (i.e. mounted USB sticks or external drives), then you can set the Volumes tab in the client config to "Selected Volumes" and select C: drive (or others if they have multuple partitions). Then, the selector will not scan any disk/partition other than the one (or more) chosen. I use that method to avoid scanning OEM rebuild partitions on some laptops (i.e. HP/Lenovo ones). Hope that helps.. Richard
  4. 8.2 or 8.5.. wouldn't bother with 8.0 or 8.1, they both "had issues" with grooming and other basic functionality. I would go as far to say under 8.5 it "feels" like you can trust Retrospect to do backups again! Richard
  5. Yeah I've upgraded.. looks and behaves much the same really. I think 8.5 just added better VMware features and Exchange 2013 support really. Not really had any crashing problems with 8.2 or 8.5.. though for some weird reason my clients are not seeing the backup history in the tab!? (I have rebuilt the server from scratch and it still doesn't work right!) I even groomed some backup sets today without ANY problems! Richard
  6. Hi - anyone else seeing an error when trying to install the 8.2 Client? I made the mistake of pushing the client update via the RS Server, which broke half the server installs on our network. Now I'm trying to manually get them all working and I'm seeing a "Error 2753. The File 'retfwset.exe' is not marked for installation." This stops the install dead, so now I'm kinda stuck. Installing the 8.1 client also fails.. Has anyone else seen this? Richard
  7. Ah right, maybe a different issue then. For some reason, my RS server complains it can't find the backup set *very* occasionally and no matter what I do it won't accept the location I browse to. Yet (!) I can still look at snapshots and even copy data from it to a new backup set - very weird. Anyway, still rebuilding my server 8 hours later as RS kept crashing when I exported the Selectors, so some corrupted and I'm having to rebuild the most complicated ones by hand (which is painful after several years of maturing). Ah well... it does seem a *little* better at repairing the catalogs now I'll see how 8.2 goes when battered tomorrow. Rich
  8. I had this issue today, yet even when I check 'member is lost/damaged' it wouldn't let me click OK! I'm resigned to the fact, since upgrading to 8.2 the other day, I need to rebuild my config file *yet again* to get things working. If I still have problems, I'm dropping Retrospect. Richard
  9. I see groom failures constantly on my backup server, and my catalog files are on a single, non-RAIDed SSD disk. My backup sets are on a ReadyNAS PRO 6TB device, which has zero issues for sharing files to a fair amount of staff over the same SMB protocol.
  10. You're not running Symantec or another AV tool which has an inbuilt network protection feature are you? Richard
  11. Personally.. start from scratch. Keep your old backups sets safe in case you need to recover old data, but create new backup sets and config under 8.1. Richard
  12. Ah my bad, I must of imagined all the hours of rebuilding my configuration then... Am interested to hear how the user got on too... Rich
  13. Personally, although it's going to involve pain... I'd scrap 7.7 and rebuilt 8.1 from scratch (and I mean clear out all log/configuration folders). I upgraded from 7.7 to 8.0, then had huge problems, so rebuilt my config, then upgraded to 8.1 beta.. had problem and rebuild the configuration again, then upgraded to 8.1 'official' and am still having problems. I've had enough to rebuilding my backup system now and it's about time Retrospect fixed this ongoing config file corruption problem or provided a tool to repair it. I'm now seeing things like clients not being able to see when they were last backed up, can't restore or see logs of previous backups etc. Grooms fails, constantly asking me to rebuild them and I get random network connection errrors making backups fail. Richard
  14. 8.1 is OK.. don't expect grooming or anything else key to work properly. At least, not after a month or so of using a backup set Rich
  15. I see this too in RS 8.1 Multi Server. In fact, my laptop is 'stuck there' right now with another user's. My laptop backup kicked off at 10am today and has been sat at 'Building Snapshot' for several hours now - blocking any other proactive backups for this backup set. My logs show: + Normal backup using All Staff PST Backups at 18/04/2013 10:00 (Execution unit 3) To Backup Set PSTBackups... - 18/04/2013 10:00:08: Copying Local Disk (C:) on Richard Thorrington (T500 W7) ..and that's it. The other user logs says: + Normal backup using General Staff Backups at 17/04/2013 10:52 (Execution unit 2) To Backup Set GenStaffBackups... - 17/04/2013 10:52:22: Copying Local Disk (C:) on Gavin Fisher (T400 W7 64bit) Using Instant Scan ..and that's it. Richard
  16. You need to reinstall the clients so they are running 8.1, yeah. Retrospect have released an updater, so you should be able to push the update via RS Server itself. Richard
  17. Really, is that with 8.1? It's not something I've tested for a while due to it not working under 7.7... it can't be that hard, I'm sure it used to work on an old Mac version! Rich
  18. HI David, a config file repair tool would be a good starting place... I have features 'missing' which apparently are caused by config77 corruption, requiring a full RS Backup server rebuild to resolve (which I have done more times than I care to remember already) Richard
  19. I think RS 8.0 Server requires an 8.0 client on Windows machines, as there are several new features (InstantScan, backup logs, client-side recovery etc). Linux machines still use the 7.6, due to the lack of further development... Rich
  20. How does it work with vCentre? i.e. if you run vCentre and have licenses in place, does Retrospect see that as a single virtual entity to backup, or 2, 3, 4+ vHost servers, each needing their own Retrospect license? Richard
  21. I very much doubt those automatic notifications on crashes go anywhere... if they do, Retrospect Inc must have thousands of them from my server alone! We use Netgear ReadyNAS devices and had good success duplicating Retrospect backup sets across sites using the rSync over SSL feature. Richard
  22. I had the same thing after upgrading to 8.0 from 7.7. I ended up rebuilding the config (again) from scratch.. and then again when I installed the beta release of 8.1 which fixed some terrible grooming crashes. Now I'm on the official 8.1 release, my client GUIs complain they haven't been backed up in 100's of days (even though they have) and users cannot see history info via the client GUI either. Guess what? Support say I need to rebuild my config as it has become corrupt!! If Retrospect paid my company £500 each time I had to spend a couple of days rebuilding their software, I might not mind so much. As it happens they seem to think it's acceptable that their software can do this and we (end users) pick up the pieces. It's about time they created a config export tool, which would allow us to export the config (which would also do a corruption/fix process), then we could wipe and reapply all our settings quickly. Richard
  23. Hold off. 8.1 isn't ready for production, though I'm using it as I had no option as we have Win8 clients and needed to address the huge performance impact of laptop scans. Wait for the next 'official' patch to be released and check back on the forum to see what state it's in. Richard
  24. Make sure you don't upgrade 8.0 clients to 8.1 over the top - you'll get problems still. Each machine one your network needs to be manually uninstalled and reinstalled, ideally with a reboot in the middle and after. Retrospect didn't see this as being a problem, so haven't released an RDC (?) (automated client update file).
×
×
  • Create New...