Jump to content

Richy_Boy

Members
  • Posts

    518
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Richy_Boy

  1. This is a members forum, very rarely do Retrospect staff grace us with their presence and knowledge.
  2. Ah yes, forgot about those options - I don't think I've every used them? Saying that, in 8.1 there are options arouns shutting down clients, sleeping and WoL - I wonder if these work now?! Rich
  3. Hi all; I wonder if any of you see this error? I see this quite often in my logs.. The backup server and clients are on the latest drivers and I can't find any network switch errors. I had been assuming it was proactive laptop users getting fed up with the disk thrashing and unplugging their laptops form the network but after seeing it happening on static desktop machines too I have checked a few users and they haven't unplugged for the full working day. It does seem to be only happening with proactive backups though...! + Normal backup using Services Dev Clients at 07/02/2013 09:24 (Execution unit 2) To Backup Set ServicesDevBackups... - 07/02/2013 09:24:16: Copying Local Disk (C:) on Suresh ********** (R61 W7 64bit) Trouble reading files, error -519 ( network communication failed) 07/02/2013 10:22:27: Snapshot stored, 415.5 MB 07/02/2013 10:23:12: 1 execution errors Completed: 6359 files, 1.5 GB, with 46% compression Performance: 126.8 MB/minute Duration: 00:58:56 (00:46:56 idle/loading/preparing) + Normal backup using All Staff PST Backups at 05/02/2013 11:58 (Execution unit 1) To Backup Set PSTBackups... - 05/02/2013 11:58:06: Copying Local Disk (C:) on Gavin ********* (T400 W7 64bit) Using Instant Scan Trouble reading files, error -519 ( network communication failed) 05/02/2013 12:22:49: Execution incomplete Remaining: 1 files, 3.8 GB Completed: 0 files, zero KB, with 0% compression Performance: 0.0 MB/minute Duration: 00:24:43 (00:01:05 idle/loading/preparing) Richard
  4. Yeah, I see strange things with ISA too, one day it will work, the next it will not and the third day it will work again. Are you using 8.1 server and clients? I seem to be suffering from "Network Communication Failed" errors, even though I'm not seeing any network problems. Richard
  5. Does it actually require a minimum bandwidth? I would have thought it would use whatever you have and backup jobs will just take longer over lower bandwidth? We used to duplicate backup sets across NAS devices through rSync over SSH and it worked well through a 2Mb link unless a large file changed! Rich
  6. If it helps, it doesn't happen in 8.1.. sure, there are other bugs to replace this one though Rich
  7. I pretty sure from memory the catalog file is about half the size when compressed. This might not mean much to a small backup set with large files, but when it's a huge backup set with millions of small files, it can get pretty huge. We use SSD disks for OS/catalog files, so space is at a premium, so compress.
  8. I've seen this too, so will be interested to hear what you hear back. Rich
  9. Was told by support by backup history might be caused by.... a corrupt config.dat file and I need to test a clean RS 8.1 install to confirm it. I AM NOT rebuilding this flippin' server from scratch again.. Richard
  10. That's probably a Retrospect bug.. we get the same thing under RS 8.0 Server and was mostly fixed under 8.1 (pre release). It's where the Instant Scan feature seems to index files which are deleted before the backup can copy the file, i.e. mostly temp files. Richard
  11. Yeah, I was going to say, to make upgrading from 8.0 to 8.1 even more painful, you have to uninstall 8.0 first, you can't install over the top as it won't work afterwards. Of course, this means the client is removed from RS Server, so you then need to put it into the correct folder again and potentially update scripts too. Retrospect didn't see this as being an unnecessary overhead for a company of 50-100 users!? (as they could/should have released an upgrade RCU package to save us the hassle as a small token of apology for releasing 8.0 is such a mess) Richard
  12. No, I'm with you Fulco... this product shouldn't have been released with all of these bugs. If I can find them in a working day after upgrading, then I would expect the Retrospect test team to be able to do the same thing. So, I guess they either released 8.0 KNOWING full well about the bugs and needed the money, or their test team needs to be fired. The amount of hours I've wasted baby-sitting this software, our company could have bought something more robust like BackupExec etc, which on paper at least looks costly... I seem to be getting "Can't use open file - maximum number of snapshots already stored" right now. Instant scan bombs out, like you say or just doesn't seem to be mentioned in the logs even with an 8.1 client installed. When I click on the Backup history tab I can't see anything, even after allowing access for 'all needs' in the backup set permissions. Richard
  13. You just need to delete or move the config77.bak and config77.dat files form the following location: c:\ProgramData\Retrospect\ Next time you launch RS, it'll be like a clean install. Richard
  14. http://kb.retrospect.com/articles/en_US/Retrospect_Article/grx-assert/?l=en_US&fs=Search&pn=1 Rich
  15. I know this worked with 7.7 to 8.0, but I'd recommend you skip 8.0 and go to 8.1 which is a pre-release patched version which stops a load of errors/groom issues. I had so many problems after upgrading to 8.0 with crashing/freezing then I rebuilt all my backup sets and config from scratch, and THEN upgraded to 8.1 - so I can't say for sure if it was an upgrade issue or just buggy v8 software. It's probably best to ask the support guys, as this is a user forum with the odd fleeting visit from Retrospect staff. Richard
  16. Hi RS... Ok, so we have two Proactive Backups for our client machines, one for usual development data and another for PST files (only). This was split as staff were seeing huge daily backups where the entire 1-10GB PST file was copied every day, when in fact nothing had changed in the PST/archive file at all. I backup PST's weekly and have normal backups every other day - again, to reduce the impact on our productivity as RS hammers the disks with snapshots (and scanning before Instant Scan) So, it would be great if RS could be more intelligent about syncing proactive backups, so when it sees a client free, it looks to see what proactive backups are scheduled and does them both at the same time, meaning it only needs to go through the Instant Scan phase once and the snapshot building at the end also. This would save a whole load of time... I've seen machine sit in the building snapshot phase for ages due to the large complicated file/folder structure often used in software development (i.e. CVS data) Richard
  17. Get 8.1 installed, it's WAY better at removing those temp file errors you're seeing and fixes a grooming issue too - and it's actually a free 'upgrade'. You can get it from the knowledge base pages (not sure why it's not on the main download page as paying customers installing RS 8.0 will simply walk away from the product. Eric (big cheese at Retrospect Inc) talked about an end of Q1 release for the official release - way too slow in my opinion! I don't think the update link has ever worked properly in retrospect, much like the WoL stuff.. Richard
  18. I've not seen a problem backing up Windows client VMs within VMware, using the 8.1 client. Something to note, when upgrading a client from 8.0 to 8.1, make sure you uninstall the client and blitz the remaining Retrospect folder before installing 8.1, else you'll see Instant Scan backups. Richard
  19. I should add, when I raised this with support back in the early v8.0 days they told me about a drop down in the Backup Set allowing password access "for any use" - which I have set on all backup sets. When I click on the hisotry tab from a client, I get a "test client" box come up on my server, which times out and closes after a while (not returning any data to the client). Is this another feature that wasn't quite ready for prime time? I'm *sure* I've seen this working when testing the v8.0 BETA1? Also note the number of errors I'm getting (in screenshot) from seemingly successful backups due to Instant Scan not being able to handle temp files (or files that change on an hours/nightly basis by the looks of it)
  20. HI Eric, have you got any details on up coming features? I'm assuming the official RS 8.1 release which fixed a number of show stopping bugs in RS 8.0 (windows) will be released before Spring? I've been using the pre-release of 8.1 for two weeks now and it's much more stable. Thanks, Richard
  21. HI, is anyone else seeing broken 'features' in RS 8.0 and 8.1 clients, or is it just me? i.e. 1) My last laptop backup has a " - " where it should have a time stamp. I know my laptop backed up yesterday under two different proactive backups... on servers, which have a nightly scripted backup, I seem to have a time/date stamp in place. 2) The history tab has nothing in it on both laptops and servers When I click on the History tab I get a swirling icon suggesting it's thinking, but nothing comes back? Added screen shots so people can see what screens I'm on about... Cheers, RIchard
  22. Hi Mayoff, I understand that. I don't think Retrospect Inc appreciates the time and internal cost it takes to manually upgrade a small network with just 50 users and around 30 servers. When is the final release due? Richard
  23. Would be great with home workers to have compression of backed up data to save on bandwidth... of course, it would also be great as requested before to have clients pinging the server, as quite often in remote networks there's a NAT between internal and remote networks. Symantec give you the choice with Endpoint... Richard
  24. The Client config on RS 8.1 Server is getting messy and there seems to be a mix of information, security and client permission tick boxes now which I think need tidying up. Richard
  25. Yes to both. You need the 8.0 clients to work with RS 8.0 Server. You can install over the top, but make sure you rebuild your catalog files on all backup sets before trying to use them in anger. Also, I'd HIGHLY recommend you get the 8.1 update for both server and client, else it'll crash every time you try and groom a backup set! NOTE: The 8.1 client (which fixes some bugs doesn't NOT have an upgrade file, so you will need to manually install all clients on your network - rather than pushing an update to all connected clients) Useful link: http://kb.retrospect.com/articles/en_US/Retrospect_Article/grx-assert/?l=en_US&fs=Search&pn=1 I hope that helps... Richard
×
×
  • Create New...