Jump to content

jez

Members
  • Content count

    15
  • Joined

  • Last visited

Everything posted by jez

  1. I could also write my own backup package... 1. There are several folders, no matter what. For example a users folder, a settings folder, an htdocs folder, an inetpub folder as well as my own half dozen top level folders. 2. I am not going to restructure my entire world into one folder and rebuild everything around the new locations, to work around a limitation in a backup suite - I would switch backup system first. 3. As I said, I also want a system backup, and that is huge because of the poor compression of snapshots. This part of the forum is for suggestions for improvements to Retrospect. I have made several very good suggestions and they would benefit lots of users - indeed they would benefit just about every user. They are not difficult improvements to make either, and would increase the robustness of peoples backups (primarily by using less media). Maybe Retrospect will ignore my suggestions, maybe not. I see they have been working on the compression of meta data, so hopefully they will consider the suggestion to compress all parts of snapshots. There have been other people asking why the snapshots are so big, and indeed making a similar suggestion to mine, that you only snapshot the needed folders. I have managed a huge variety of software, successfully out competing other companies - and a part of that is listening to customers, and the problems they face. I know what happens when engineers stop listening to the customers that have a clue - those companies eventually die because other people will one day make better products.
  2. Hi, I have been using Retrospect for about 8 years now and have a variety of disk backups. The problem is they are huge, and, it turns out, unnecessarily so, because of how Retrospect works. Here is what is happening, and suggestions for how it could easily be improved and also give users a reason to pay for an upgrade. I (and probably most users backing up to disk) will back up from one or two volumes (C and D drives e.g.), to a disk set on an external drive. I know that historically backup was more to tape, but these days it isn't, and Retrospect has not really been adapted to this world, even though it is bundled with endless disk drive solutions. Snapshots are currently 400 MB on my Windows machine. That is huge. But without a snapshot, Retrospect is essentially useless right now. I have analysed what is happening and: - There are 450,000 files on the computer. 250,000 of these are part of Windows and Program Files, so I can not get rid of them. - When I turn off all the snapshot 'additions', such as system state, folder security info, the backup drops to 125 MB - still huge (and sadly I only just discovered this and turned it off, so I have been unnecessarily chewing up even more storage space) - My daily backup is about 60 MB of changed stuff, so the snapshots are still about 2/3 of my backup storage requirement. However, a snapshot contains ALL the files on the computer, even though I am only backing up a small number of folders, representing about a third of the files on the computer, and I have no use for the bulk of the snapshot. That indicates that the snapshots only need to be about 40MB in size, for the backups I am doing. That would more than HALVE the size of the backups, and also make them considerably quicker. The reason the snapshots are there is so you can restore the whole system - but this is not something that I want to be able to do, to any day in the last umpteen. However I DO want to access my own files to greater granularity (I currently have the last 8 years of them, daily, and pruning out the snapshots is something I do not want to do. There is a very simple solution - instead of storing a snapshot of ALL the files, simply store a snapshot of what TOP LEVEL FOLDERS are backed up in each session, and all the tree under those folders. That would reduce the size of snapshots drastically (assuming users also turned off the System state and other unneeded options). Clearly this is already technically possible, because it is essentially what happens when you create subvolumes. But the subvolume approach is NOT what I want to do, because I want to back up EVERYTHING except the things I do not want to. That way it is safe, for example if I make a new top level directory, as that would be included. Also the subvolume thing, e.g. with 10 top level directories, is very unmanageable with tons of 'snapshots', and you would have to make subvolumes of things like Users and so on, and who knows where Windows will put things in the future. The only practical way to operate is to backup everything except things you definitely do not want. There is a secondary thing, which is that the snapshots (with just the file listings, not the system state etc.) will compress 5x - so my 125MB .rdb file with the snapshot in will compress down to 18MB. That is 6x compression. End result is that my snapshots could be 18MB and my data 60MB, compared to the current minimum of 125MB and 60MB. So overall less than half the storage space would be required. I suspect that for most users the gains would be larger, as most of them will not be backing up over 200,000 files... The huge snapshots created by the default settings are disastrous these days. Even with the system state off, they are still hugely bigger than they need to be. The solutions are simple and would improve the product drastically. Please consider them. To add - this sort of improvement would be a major reason to upgrade. I finally upgraded from v7 to v11 and found no advantages at all - very sad - I hoped things would be smaller and quicker. Also, to give an additional reason to upgrade, you could provide a 'Shrink Snapshots' option. This would: - have options to remove system state and file / folder security information from existing snapshots - Have options just to compress existing snapshots (my 400mb snapshots zip down to 70mb, even with system state etc. in there - note that I am using software compression in Retrospect) - Convert the current file listings in the snapshots into much smaller ones per my suggestion earlier That would give someone an easy way to recover huge amounts of disk space - more than half, in my case, and judging by comments on various forums, lots of other people would also benefit from these improvements. Final thing, as an aside - having a way to select multiple snapshots, either to 'forget' or to 'retrieve' is such a simple thing to do, but we have to deal with them one by one - exceedingly tedious. I tried using NTFS file compression, but that would only work for my USB attached drive, not for my NAS. Also the performance takes a hit, especially as it would be trying to compress other files that would be largely incompressible - it needs to be built into Retrospect to do it optimally. Regards, Jeremy Kenyon
  3. I explored this before, and as I said in the original post, subvolumes are not practical, for two reasons: - You need one for each top level folder, which very quickly becomes unmanageable (I would need about 10), and you end up with a sea of clutter. It is also a pain to do restores and such like then, as you have to do it snapshot at a time. - If you add a new top level folder it won't be backed up unless you remember, so it is not 'fail safe'. What subvolumes do is prove how easy it would be for Retrospect to implement a proper snapshot that only has the top level folders you were backing up. The list of files and folders to backup is already calculated early in the backup process, just extract the top level folders from it. There is already a mechanism to snapshot a folder, as used by subvolumes. Just put the two together... Then apply a decent compression to every part of a snapshot. These are pretty basic things for a backup system really - compressing data as much as possible and not backing up unnecessary things. Of course I am not saying the alternative products are better - there are a lot of rubbish ones - but Retrospect could dominate if they improved some things.
  4. Hi Robin, I have been testing the new 11.5 version today. However, while it has reduced the size of the snapshot without any system data or meta data, it has not made a significant difference to the snapshot including all the system data (the various snapshot options turned on). The last snapshot was 441mb with 11.5, and the one before (with 11.0.1.106) was 437mb, so it has grown slightly in fact. Both can be zipped by a factor of 6. It is as if somehow the new compression does not kick in in some circumstances? Jeremy
  5. The backup I was describing is my 'work files' backup. In addition I have a system backup, which I do not keep as long a history for, which is much larger per day (over 1gb). Here are 7 reasons the problem is very real. 1. You can not rely on a single external disk for backups. You need at least two, which doubles the cost. The bigger the disks, the more the cost. 2. You are assuming the software is perfect. It is not. It has had a variety of problems over the years that can result in a corrupt backup. To counter this I run two independent backups, identical settings, to two different disks, on alternate days. I have learnt over the years how to recover from failed backups, by deleting the most recent rdb files, but it is not a satisfactory solution. 3. You are also assuming you can incrementally back up forever. However Retrospect has had bugs over the years that result in it not noticing some files have changed. I was astonished at this, but I have recovered from backups only to find that some of the files are different in the backup, but retrospect has not noticed so the backup has become incorrect (and does not self-correct). It is quite specific what can be different and is not due to disk faults in the backup. The end result is that I restart my backup chain every couple of years or so, which means an initial huge backup again. This also protects against the problem of an rdb file going corrupt, invalidating all subsequent backups. 4. You are assuming 10 years is a long time. I currently have 8 years backups, and for a variety of reasons I want to keep that history going. It can be for IP protection reasons, to have appropriate evidence, or just because I may have accidentally deleted a folder of photos and didn't notice - who knows - the point is we don't know, which is why we back up. 5. You are ignoring the performance aspect - backing up to a network drive not only hammers the network, but it is slow. Backing up 100mb instead of 500mb would make a substantial difference. Even to a local disk, writing less is a good idea. 6. Your vulnerability to a media error is largely proportional to the amount of media you use. If you halve the media used, you halve the chance of losing data due to a bad block (crudely speaking of course). 7. A typical home user who invests in a large external disk will use it for more than just backups. I am sure most people use them for temporary space, or other storage they may not need backing up. Retrospect 11.5 has introduced a small change to compression, but it has left my system snapshots the same size. It has shrunk the file listing component significantly, maybe to a third of what it was (40mb instead of 125mb) - not as good as it being zipped, but I guess it is performance vs size - though cpu speed these days probably means it should put more effort into compression.
  6. There are two different needs with backups. The first is to restore a system to a previous state. This is actually not the most important thing for a lot of people. It is also hugely space consuming if you keep a long history (I currently have 8 years of daily backups). The second is to back up your 'work' - and this is both to prevent loss, and allow you to see the previous versions of things. That is where I want fine granularity for a long time. What you are both talking about is the former, not the latter. I run two daily backups to disk - a system one with one set of rules, and a work one with other rules. In particular the work one filters out a lot of things, including windows, programs and so on, but it does it by exclusion, so any new folders are automatically included. You also have to remember there are two very different markets for Retrospect - the home user (or indeed the small company) have different requirements to people backing up dozens of systems.
  7. Your logic is incorrect. I want to back up particular folders on a daily granularity. I know those folders do not and never will include Windows or Program Files etc. So I do not want to waste what amounts to a third of my total backup space storing snapshots of the folder contents of those folders. Moving files around makes no difference to what I need in a snapshot. I want to back up what I want to back up, and nothing else. If I move files to a different top level folder, then the next snapshot would include that new top level folder and its tree. At no point do I need a snapshot of a tree I do NOT want to back up. If you could give a realistic scenario where my suggestion would not work, please do so, because I can not see one for my needs.
  8. jez

    Usb Drives & Retrospect

    I had the same thing with a 2TB USB drive (Western Digital 2TB - My Book Studio II Edition ). I tried rebuilding the catalog etc, checked the disk for errors (it checked out fine), kept getting the -206 problem. However, I didn't trust the disk check as I had previously had a bad file that couldn't be read, but disk check said all was OK. In the end I tried copying the whole backup set to another drive. It turned out there WAS another bad file in the disk set - an unreadabe block or something. As it turns out I actually had a copy of the file, on another drive, so I replaced the broken file with a good one. Then rebuilt the catalog, and I got a different error: "Backup Set format inconsistency (5 at 91390759, during the catalog rebuild". This time though, it appears to have built a valid catalog and I can access my backups again. Probably there are some files that may not be backed up, shortly after the backups that were a part of the broken file, but it is unlikely to be a problem in my own case as most of the files change every day so would soon ne back in sync with the backup date.
  9. Hi Folks, I'm getting desperate here, so I hope you can help please! I am trying to groom a disk backup. I have Retrospect 7.7 with the latest updates, running Windows Vista. I have a 2TB drive, the backup is about 1.2TB, and there is 0.8TB free. There are about 300 snapshots, and I have locked about 100 of them and am trying to groom the rest out. Every time I try, it fails with Assertion failure at "elem.cpp-1091" In the log it also says LmGet: ndex = 3014705 > nsp->count = 92455 When it starts the grooming, it happily starts going through something - not sure what - but it repeatedly opens the restorepoint, scans for a while, and then seems to start on another. Presumably it is checking either snapshots or sessions or something. 30 minutes later it asserts and thats it. No disk space is groomed. I have rebuilt the catalog from scratch several times, and its a new install of the software. Unless I can get this working, I obviously don't have a long term backup solution. The assert log is below: OS: Windows Vista version 6.0 (build 6002), Service Pack 2, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.7\Retrospect.exe, version 7.7.325 Driver Update and Hot Fix version 7.7.3.102 Exception occurred on 11/05/2010 at 03:26:53 Error info: Assertion failure at "elem.cpp-1091" Exception code: E0000000 ASSERTION Fault address: 76FAFBAE 0001:0003EBAE kernel32.dll Thread ID: 0000150C, Name: Immediate execution thread EAX:0344F7A8 CS:001B EIP:76FAFBAE EFlags:00000212 EBX:00000002 SS:0023 ESP:0344F7A8 EBP: 0344F7F8 ECX:00000003 DS:0023 ESI:06EE4680 FS: 003B EDX:00000000 ES:0023 EDI:002E0031 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= kernel32.dll 0001:0003ebae E06D7363 1 3 344F824 E06D7363 1 0 0 MSVCR80.dll 0001:00027e89 0 0 2E0031 6EE4680 2 600CD9AC 344F840 344F3C8 bdrock20.dll DebugHandler::Throw +67 E0000000 1 1 344F894 344F994 60070E83 E0000000 1 bdrock20.dll assertLog +2A E0000000 1 344F894 'essA' 'oitr' 'af n' 'ruli' 'ta e' bdrock20.dll Debug +63 600948B4 443 3450710 0 60003429 2E0031 2E0031 2E0031 bdrock20.dll ElementSpace::LmGet +89 2E0031 73111E4 1C94DCC 3450380 EA4F3E8 2E0031 14072CB 345073C PCVOL.DLL PCTree::TMakePath +1DC 72BAE40 344FAD4 1000 54444 6002D51D 344FAD4 72BAE40 1000 bdrock20.dll BlockMove +15 344FAD4 72BAE40 1000 72BAE40 3450AD4 72BBE23 'Lms.' 1000100 bdrock20.dll TCompStat::unpackByte +12D 72BAE40 1000 72BAE40 3450AD4 72BBE23 'Lms.' 1000100 0 0001:0344fad4 1000 72BAE40 3450AD4 72BBE23 'Lms.' 1000100 0 0 0001:072bae40 0 0 1E9C 54444 40 4 0 0 pcvoldriver.dll TPCFolderLoc::SetToTemp +A0 0 1E9C 54444 40 4 0 0 0 Thread ID: 00000B24, Name: DAG Selector Thread EAX:68203F38 CS:001B EIP:77945E74 EFlags:00000246 EBX:0212B4F8 SS:0023 ESP:0639E3E0 EBP: 0639E450 ECX:050E8E88 DS:0023 ESI:00000000 FS: 003B EDX:050E8B30 ES:0023 EDI:00000000 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 404 -1 0 639E478 681AFED4 404 -1 50E8E90 kernel32.dll 0001:000487f2 404 -1 50E8E90 639F82C 681B2495 50E8E88 639FBDC 639FEA0 RETROAPI.DLL WinCondition::Wait +54 50E8E88 639FBDC 639FEA0 3 0 0 0 0 RETROAPI.DLL WinSelector::selectorRoot +75 50E8B30 639FBDC 639FEA0 212B4F8 619F184 0 37F430 50A0800 RETROAPI.DLL WinThread::spawnRoot +6C 50A0800 681AF9B0 50A0800 639FE4C BAE336 619F4D4 0 0 RETROAPI.DLL rapiForkStub +3B 619F4D4 0 0 619F29C 50EEE48 13 0 0 meson.dll doTask +246 'Task' 6806DD30 0 0 619F4D4 0 0 619F29C meson.dll TThread::TaskCall +85 50EFA88 'Task' 6806DD30 619F4D4 0 0 619F29C 50EEE48 meson.dll modThreadRoot +FA 619F1B4 D9010828 0 0 212B4F8 639FF54 639FF54 639FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 212B4F8 639FFD4 779219BB 212B4F8 71B2537E 0 MSVCR80.dll 0001:00001a47 212B4F8 71B2537E 0 0 212B4F8 0 0 0 ntdll.dll 0001:000409bb ntdll.dll 0001:0004098e Thread ID: 00000594, Name: DAG Listener Thread EAX:0619F588 CS:001B EIP:77945E74 EFlags:00000297 EBX:0407F6E0 SS:0023 ESP:0619F378 EBP: 0619F3B8 ECX:00000594 DS:0023 ESI:7FFFFFFF FS: 003B EDX:00000004 ES:0023 EDI:FFFFFFFF GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 3F8 3E4 2 4 D9D06431 0 13A06C8 212B4F8 mswsock.dll 0001:0001604e 3E4 619F658 619F650 0 0 619F60C 619FBDC 619FEA0 WS2_32.dll 0001:0001abdb 3E4 619F658 619F650 0 0 619F674 681B0B8F 3E4 WS2_32.dll 0001:0001ae0d 3E4 619F658 619F650 0 3D7380 0 50C20E8 10 RETROAPI.DLL WinTCPlistener::Accept +4F 619FBDC 619FEA0 212B4F8 50A0898 367B18 619F638 BAD6E3 619F740 RETROAPI.DLL DAGlistenerWin::listenRoot +2C3 3C6E10 619FBDC 619FEA0 212B4F8 5F9F12C 0 37F430 50A0788 RETROAPI.DLL WinThread::spawnRoot +6C 50A0788 681AF9B0 50A0788 619FE4C BAE336 5F9F47C 600652C8 19 RETROAPI.DLL rapiForkStub +3B 5F9F47C 600652C8 19 3AA558 37F430 13 0 0 meson.dll doTask +246 'Task' 6806DD30 0 0 5F9F47C 600652C8 19 3AA558 meson.dll TThread::TaskCall +85 50EEE00 'Task' 6806DD30 5F9F47C 600652C8 19 3AA558 37F430 meson.dll modThreadRoot +FA 5F9F15C D9210828 0 0 212B4F8 619FF54 619FF54 619FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 212B4F8 619FFD4 779219BB 212B4F8 7192537E 0 MSVCR80.dll 0001:00001a47 212B4F8 7192537E 0 0 212B4F8 0 0 0 ntdll.dll 0001:000409bb ntdll.dll 0001:0004098e Thread ID: 000005F8, Name: RAPI server thread EAX:05F9DE60 CS:001B EIP:77945E74 EFlags:00000246 EBX:0212B4F8 SS:0023 ESP:05F9E120 EBP: 05F9E13C ECX:00000006 DS:0023 ESI:05F9E18C FS: 003B EDX:00000018 ES:0023 EDI:05F9E530 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 5F9E18C 0 0 0 50EE178 5F9E1A8 BBA3AF 5F9E18C bdrock20.dll UGetMessage +25 5F9E18C 0 0 0 42C2B0 5F9E180 BB17BC 50EE5F0 meson.dll WinMsgBlocker::BlockForMsg +2F 5F9E7F4 5F9E4C4 0 0 0 0 0 5F9E7A0 meson.dll msgHelper +1EB 50EE178 1 5F9EBBC 5F9EE80 212B4F8 0 0 50EE178 meson.dll doTask +246 'Msg ' B98270 0 0 50EE178 1 5F9EBBC 5F9EE80 meson.dll TThread::TaskCall +85 50EE178 'Msg ' B98270 50EE178 1 5F9EBBC 5F9EE80 212B4F8 meson.dll TThread::MsgBlock +96 'Msg ' 5F9EE2C BAE336 5F9F470 BAE336 'LopT' 50EE178 0 meson.dll msgInTask +11 5F9F470 BAE336 'LopT' 50EE178 0 0 5F9F86C BE101C meson.dll doTask +246 'MsgT' B99410 0 0 5F9F470 BAE336 'LopT' 50EE178 meson.dll TThread::TaskCall +85 50EE178 'MsgT' B99410 5F9F470 BAE336 'LopT' 50EE178 0 meson.dll loopInTask +27 'LopT' 50EE178 0 0 5F9F86C BE101C 0 5F9F878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 50EE178 0 0 meson.dll TThread::TaskCall +85 50EE178 'LopT' B993E0 'LopT' 50EE178 0 0 5F9F86C meson.dll TThread::MsgLoop +45 'LopT' 5608 681D912C '.0.0' 302E30 76FB9A26 360000 0 RETROAPI.DLL Class::rapiServerThread +18D 40F7238 22D654 22D654 A 12 0 0 0 meson.dll doTask +246 'Task' 6806D9E0 0 0 40F7238 22D654 22D654 A meson.dll TThread::TaskCall +85 50EE178 'Task' 6806D9E0 40F7238 22D654 22D654 A 12 meson.dll modThreadRoot +FA 22D588 DAC10828 0 0 212B4F8 5F9FF54 5F9FF54 5F9FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 212B4F8 5F9FFD4 779219BB 212B4F8 'rrS~' 0 MSVCR80.dll 0001:00001a47 212B4F8 'rrS~' 0 0 212B4F8 0 0 0 ntdll.dll 0001:000409bb ntdll.dll 0001:0004098e Thread ID: 000015F0, Name: C_ClientListener EAX:059BE1C0 CS:001B EIP:77945E74 EFlags:00000246 EBX:02127FB8 SS:0023 ESP:059BE488 EBP: 059BE4A4 ECX:00000006 DS:0023 ESI:059BE4F4 FS: 003B EDX:00000020 ES:0023 EDI:059BE898 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 59BE4F4 0 0 0 50ED4F0 59BE510 BBA3AF 59BE4F4 bdrock20.dll UGetMessage +25 59BE4F4 0 0 0 5023110 59BE4E8 BB17BC 50ED968 meson.dll WinMsgBlocker::BlockForMsg +2F 59BEB5C 59BE82C 0 0 -2 0 0 59BEB08 meson.dll msgHelper +1EB 50ED4F0 1 59BEF24 59BF1E8 2127FB8 59BEE24 778E99FA 50ED4F0 meson.dll doTask +246 'Msg ' B98270 0 0 50ED4F0 1 59BEF24 59BF1E8 meson.dll TThread::TaskCall +85 50ED4F0 'Msg ' B98270 50ED4F0 1 59BEF24 59BF1E8 2127FB8 meson.dll TThread::MsgBlock +96 'Msg ' 59BF194 BAE336 59BF7D8 BAE336 'LopT' 50ED4F0 0 meson.dll msgInTask +11 59BF7D8 BAE336 'LopT' 50ED4F0 0 0 59BFE40 BE101C meson.dll doTask +246 'MsgT' B99410 0 0 59BF7D8 BAE336 'LopT' 50ED4F0 meson.dll TThread::TaskCall +85 50ED4F0 'MsgT' B99410 59BF7D8 BAE336 'LopT' 50ED4F0 0 meson.dll loopInTask +27 'LopT' 50ED4F0 0 0 59BFE40 BE101C 0 59BF878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 50ED4F0 0 0 meson.dll TThread::TaskCall +85 50ED4F0 'LopT' B993E0 'LopT' 50ED4F0 0 0 59BFE40 meson.dll TThread::MsgLoop +45 'LopT' 0 5104910 59BFE4C BAE336 508C390 22BB8C 22BB8C network.dll nclThreadTop +4A 508C390 22BB8C 22BB8C 0 C 0 0 0 meson.dll doTask +246 'Task' 60701BD0 0 0 508C390 22BB8C 22BB8C 0 meson.dll TThread::TaskCall +85 50ED4F0 'Task' 60701BD0 508C390 22BB8C 22BB8C 0 C meson.dll modThreadRoot +FA 22BAA8 DAA30828 0 0 2127FB8 59BFF54 59BFF54 59BFFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 2127FB8 59BFFD4 779219BB 2127FB8 7210537E 0 MSVCR80.dll 0001:00001a47 2127FB8 7210537E 0 0 2127FB8 0 0 0 ntdll.dll 0001:000409bb 752529E1 2127FB8 0 0 0 0 752529E1 2127FB8 ntdll.dll 0001:0004098e 752529E1 2127FB8 0 6DB0000 7CB00A0 0 0 AE000 Thread ID: 00000FBC, Name: RetroFrameThread EAX:770A7000 CS:001B EIP:77945E74 EFlags:00000246 EBX:021281D8 SS:0023 ESP:056BE48C EBP: 056BE4A8 ECX:00000006 DS:0023 ESI:056BE4F8 FS: 003B EDX:00000004 ES:0023 EDI:056BE89C GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 56BE4F8 0 0 0 4F60FE0 56BE514 BBA3AF 56BE4F8 bdrock20.dll UGetMessage +25 56BE4F8 0 0 0 40A5A68 56BE4EC 60064A15 4F61B18 meson.dll WinMsgBlocker::BlockForMsg +2F 56BEB60 56BE830 0 0 0 6D 0 56BEB0C meson.dll msgHelper +1EB 4F60FE0 1 56BEF28 56BF1EC 21281D8 -1 56BECFC 4F60FE0 meson.dll doTask +246 'Msg ' B98270 0 0 4F60FE0 1 56BEF28 56BF1EC meson.dll TThread::TaskCall +85 4F60FE0 'Msg ' B98270 4F60FE0 1 56BEF28 56BF1EC 21281D8 meson.dll TThread::MsgBlock +96 'Msg ' 56BF198 BAE336 56BF7DC BAE336 'LopT' 4F60FE0 0 meson.dll msgInTask +11 56BF7DC BAE336 'LopT' 4F60FE0 0 37F430 56BFE40 BE101C meson.dll doTask +246 'MsgT' B99410 0 0 56BF7DC BAE336 'LopT' 4F60FE0 meson.dll TThread::TaskCall +85 4F60FE0 'MsgT' B99410 56BF7DC BAE336 'LopT' 4F60FE0 0 meson.dll loopInTask +27 'LopT' 4F60FE0 0 37F430 56BFE40 BE101C 0 56BF878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 4F60FE0 0 37F430 meson.dll TThread::TaskCall +85 4F60FE0 'LopT' B993E0 'LopT' 4F60FE0 0 37F430 56BFE40 meson.dll TThread::MsgLoop +45 'LopT' 3C74C0 56BFE4C BAE336 40A95F0 22D874 4166B00 22D61C UIPROD.DLL rfThread +FC 40A95F0 22D874 4166B00 22D61C 22D61C 0 10 0 meson.dll doTask +246 'Task' 4708B20 0 0 40A95F0 22D874 4166B00 22D61C meson.dll TThread::TaskCall +85 4F60FE0 'Task' 4708B20 40A95F0 22D874 4166B00 22D61C 22D61C meson.dll modThreadRoot +FA 22D550 DA530828 0 0 21281D8 56BFF54 56BFF54 56BFFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 21281D8 56BFFD4 779219BB 21281D8 72E0537E 0 MSVCR80.dll 0001:00001a47 21281D8 72E0537E 0 0 21281D8 0 0 0 ntdll.dll 0001:000409bb 752529E1 21281D8 0 0 0 0 752529E1 21281D8 ntdll.dll 0001:0004098e 752529E1 21281D8 0 729CB26F 10130B8 FFEEFFEE 0 21500A8 Thread ID: 00000D64, Name: Volume tracker thread EAX:054BDF80 CS:001B EIP:77945E74 EFlags:00000246 EBX:021281D8 SS:0023 ESP:054BE23C EBP: 054BE258 ECX:00000006 DS:0023 ESI:054BE2A8 FS: 003B EDX:00000014 ES:0023 EDI:054BE64C GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 54BE2A8 0 0 0 41E4F90 54BE2C4 BBA3AF 54BE2A8 bdrock20.dll UGetMessage +25 54BE2A8 0 0 0 40A58C8 54BE29C BB17BC 41E5408 meson.dll WinMsgBlocker::BlockForMsg +2F 54BE910 54BE5E0 0 0 -1 0 0 54BE8BC meson.dll msgHelper +1EB 41E4F90 1 54BECD8 54BEF9C 21281D8 0 76FBD24F 41E4F90 meson.dll doTask +246 'Msg ' B98270 0 0 41E4F90 1 54BECD8 54BEF9C meson.dll TThread::TaskCall +85 41E4F90 'Msg ' B98270 41E4F90 1 54BECD8 54BEF9C 21281D8 meson.dll TThread::MsgBlock +96 'Msg ' 54BEF48 BAE336 54BF58C BAE336 'LopT' 41E4F90 0 meson.dll msgInTask +11 54BF58C BAE336 'LopT' 41E4F90 0 0 54BF86C BE101C meson.dll doTask +246 'MsgT' B99410 0 0 54BF58C BAE336 'LopT' 41E4F90 meson.dll TThread::TaskCall +85 41E4F90 'MsgT' B99410 54BF58C BAE336 'LopT' 41E4F90 0 meson.dll loopInTask +27 'LopT' 41E4F90 0 0 54BF86C BE101C 0 54BF878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 41E4F90 0 0 meson.dll TThread::TaskCall +85 41E4F90 'LopT' B993E0 'LopT' 41E4F90 0 0 54BF86C meson.dll TThread::MsgLoop +45 'LopT' 0 0 0 4E4 0 72000000 0 PCVOL.DLL vtloVolTrakThread +97 4A1B968 4A1B968 40A5828 BAF2EE 360000 0 363A84 4A1B908 meson.dll doTask +246 'Task' 60995160 0 0 4A1B968 4A1B968 40A5828 BAF2EE meson.dll TThread::TaskCall +85 41E4F90 'Task' 60995160 4A1B968 4A1B968 40A5828 BAF2EE 360000 meson.dll modThreadRoot +FA 4A1B888 DA730828 0 0 21281D8 54BFF54 54BFF54 54BFFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 21281D8 54BFFD4 779219BB 21281D8 72C0537E 0 MSVCR80.dll 0001:00001a47 21281D8 72C0537E 0 0 21281D8 0 0 0 ntdll.dll 0001:000409bb ntdll.dll 0001:0004098e Thread ID: 00000D48, Name: Adding clients EAX:04D1E1D0 CS:001B EIP:77945E74 EFlags:00000246 EBX:021281D8 SS:0023 ESP:04D1E490 EBP: 04D1E4AC ECX:00000006 DS:0023 ESI:04D1E4FC FS: 003B EDX:00000018 ES:0023 EDI:04D1E8A0 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 4D1E4FC 0 0 0 41C7CC8 4D1E518 BBA3AF 4D1E4FC bdrock20.dll UGetMessage +25 4D1E4FC 0 0 0 3BCFC0 4D1E4F0 BB17BC 41C8140 meson.dll WinMsgBlocker::BlockForMsg +2F 4D1EB64 4D1E834 0 0 0 6D 0 4D1EB10 meson.dll msgHelper +1EB 41C7CC8 1 4D1EF2C 4D1F1F0 21281D8 4D1F570 4D1EC40 41C7CC8 meson.dll doTask +246 'Msg ' B98270 0 0 41C7CC8 1 4D1EF2C 4D1F1F0 meson.dll TThread::TaskCall +85 41C7CC8 'Msg ' B98270 41C7CC8 1 4D1EF2C 4D1F1F0 21281D8 meson.dll TThread::MsgBlock +96 'Msg ' 4D1F19C BAE336 4D1F7E0 BAE336 'LopT' 41C7CC8 0 meson.dll msgInTask +11 4D1F7E0 BAE336 'LopT' 41C7CC8 0 258 4D1FE40 BE101C meson.dll doTask +246 'MsgT' B99410 0 0 4D1F7E0 BAE336 'LopT' 41C7CC8 meson.dll TThread::TaskCall +85 41C7CC8 'MsgT' B99410 4D1F7E0 BAE336 'LopT' 41C7CC8 0 meson.dll loopInTask +27 'LopT' 41C7CC8 0 258 4D1FE40 BE101C 0 4D1F878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 41C7CC8 0 258 meson.dll TThread::TaskCall +85 41C7CC8 'LopT' B993E0 'LopT' 41C7CC8 0 258 4D1FE40 meson.dll TThread::MsgLoop +45 'LopT' 4D1FE4C BAE336 41C770C 4166B00 4034560 4A1DBB0 4A1DBB0 network.dll pronAddClientsThread +71 41C770C 4166B00 4034560 4A1DBB0 4A1DBB0 35F 6148C6B8 4A1DDC0 meson.dll doTask +246 'Task' '`ul0' 0 0 41C770C 4166B00 4034560 4A1DBB0 meson.dll TThread::TaskCall +85 41C7CC8 'Task' '`ul0' 41C770C 4166B00 4034560 4A1DBB0 4A1DBB0 meson.dll modThreadRoot +FA 4A1DAC8 DBE90828 0 0 21281D8 4D1FF54 4D1FF54 4D1FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 21281D8 4D1FFD4 779219BB 21281D8 'sZS~' 0 MSVCR80.dll 0001:00001a47 21281D8 'sZS~' 0 0 21281D8 0 0 0 ntdll.dll 0001:000409bb 752529E1 21281D8 0 0 0 0 752529E1 21281D8 ntdll.dll 0001:0004098e 752529E1 21281D8 0 905A4D 3 4 FFFF B8 Thread ID: 00000D60, Name: Controller thread EAX:04A1DF40 CS:001B EIP:77945E74 EFlags:00000246 EBX:021281D8 SS:0023 ESP:04A1E208 EBP: 04A1E224 ECX:00000006 DS:0023 ESI:04A1E274 FS: 003B EDX:00000020 ES:0023 EDI:04A1E618 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 4A1E274 0 0 0 418F120 4A1E290 BBA3AF 4A1E274 bdrock20.dll UGetMessage +25 4A1E274 0 0 0 3BCE40 3451360 BA4A00 418F598 meson.dll WinMsgBlocker::BlockForMsg +2F 4A1E8DC 4A1E5AC 0 0 0 1F 0 4A1E888 meson.dll msgHelper +1EB 418F120 1 4A1ECA4 4A1EF68 21281D8 0 0 418F120 meson.dll doTask +246 'Msg ' B98270 0 0 418F120 1 4A1ECA4 4A1EF68 meson.dll TThread::TaskCall +85 418F120 'Msg ' B98270 418F120 1 4A1ECA4 4A1EF68 21281D8 meson.dll TThread::MsgBlock +96 'Msg ' 4A1EF14 BAE336 4A1F558 BAE336 'LopT' 418F120 0 meson.dll msgInTask +11 4A1F558 BAE336 'LopT' 418F120 0 37F430 4A1F86C BE101C meson.dll doTask +246 'MsgT' B99410 0 0 4A1F558 BAE336 'LopT' 418F120 meson.dll TThread::TaskCall +85 418F120 'MsgT' B99410 4A1F558 BAE336 'LopT' 418F120 0 meson.dll loopInTask +27 'LopT' 418F120 0 37F430 4A1F86C BE101C 0 4A1F878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 418F120 0 37F430 meson.dll TThread::TaskCall +85 418F120 'LopT' B993E0 'LopT' 418F120 0 37F430 4A1F86C meson.dll TThread::MsgLoop +45 'LopT' 40A5988 3C1978 0 61134E88 40A5988 40A5988 21281D8 Retrospect.exe controllerThread +42C 414AB0 22E3C8 22D874 22D624 22D624 11 0 0 meson.dll doTask +246 'Task' 61108C20 0 0 414AB0 22E3C8 22D874 22D624 meson.dll TThread::TaskCall +85 418F120 'Task' 61108C20 414AB0 22E3C8 22D874 22D624 22D624 meson.dll modThreadRoot +FA 22D554 DB990828 0 0 21281D8 4A1FF54 4A1FF54 4A1FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 21281D8 4A1FFD4 779219BB 21281D8 's*S~' 0 MSVCR80.dll 0001:00001a47 21281D8 's*S~' 0 0 21281D8 0 0 0 ntdll.dll 0001:000409bb 752529E1 21281D8 0 0 0 0 752529E1 21281D8 ntdll.dll 0001:0004098e 752529E1 21281D8 0 'Lms.' 1000100 0 C0A8 39618 Thread ID: 00001620, Name: TS Quit request thread EAX:0400EBA0 CS:001B EIP:77945E74 EFlags:00000246 EBX:021281D8 SS:0023 ESP:0400EE5C EBP: 0400EE78 ECX:00000006 DS:0023 ESI:0400EEC8 FS: 003B EDX:00000014 ES:0023 EDI:0400F26C GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 400EEC8 0 0 0 3184358 400EEE4 BBA3AF 400EEC8 bdrock20.dll UGetMessage +25 400EEC8 0 0 0 3BC880 400EEBC BB17BC 31847D0 meson.dll WinMsgBlocker::BlockForMsg +2F 400F530 400F200 0 0 60097F34 6D 0 400F4DC meson.dll msgHelper +1EB 3184358 1 400FBDC 400FEA0 21281D8 60068695 400F5DC 3184358 meson.dll doTask +246 'Msg ' B98270 0 0 3184358 1 400FBDC 400FEA0 meson.dll TThread::TaskCall +85 3184358 'Msg ' B98270 3184358 1 400FBDC 400FEA0 21281D8 meson.dll TThread::MsgBlock +96 'Msg ' 400FBDC 400FEA0 21281D8 400FEA0 21281D8 24 1 meson.dll TThread::MsgDelay +119 3E8 0 26C 20 0 0 0 0 meson.dll QuitFromTSThread +D4 22E328 22E328 22E570 22E570 22E7B8 22E7B8 16 0 meson.dll doTask +246 'Task' BBB9A0 0 0 22E328 22E328 22E570 22E570 meson.dll TThread::TaskCall +85 3184358 'Task' BBB9A0 22E328 22E328 22E570 22E570 22E7B8 meson.dll modThreadRoot +FA 22E254 DB380828 0 0 21281D8 400FF54 400FF54 400FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 21281D8 400FFD4 779219BB 21281D8 738B537E 0 MSVCR80.dll 0001:00001a47 21281D8 738B537E 0 0 21281D8 0 0 0 ntdll.dll 0001:000409bb 752529E1 21281D8 0 0 0 0 752529E1 21281D8 ntdll.dll 0001:0004098e 752529E1 21281D8 0 1854BD98 101AACF FFEEFFEE 0 4EC0010 Thread ID: 00000B2C, Name: Quit handler thread EAX:03E0DAC0 CS:001B EIP:77945E74 EFlags:00000246 EBX:021281D8 SS:0023 ESP:03E0DD7C EBP: 03E0DD98 ECX:00000006 DS:0023 ESI:03E0DDE8 FS: 003B EDX:00000014 ES:0023 EDI:03E0E18C GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 3E0DDE8 0 0 0 31752D8 3E0DE04 BBA3AF 3E0DDE8 bdrock20.dll UGetMessage +25 3E0DDE8 0 0 0 42C770 3E0DDDC BB17BC 3175750 meson.dll WinMsgBlocker::BlockForMsg +2F 3E0E450 3E0E120 0 0 0 6D 0 3E0E3FC meson.dll msgHelper +1EB 31752D8 1 3E0E818 3E0EADC 21281D8 14 3E0E4B4 31752D8 meson.dll doTask +246 'Msg ' B98270 0 0 31752D8 1 3E0E818 3E0EADC meson.dll TThread::TaskCall +85 31752D8 'Msg ' B98270 31752D8 1 3E0E818 3E0EADC 21281D8 meson.dll TThread::MsgBlock +96 'Msg ' 3E0EA88 BAE336 3E0F0CC BAE336 'LopT' 31752D8 0 meson.dll msgInTask +11 3E0F0CC BAE336 'LopT' 31752D8 0 0 3E0F86C BE101C meson.dll doTask +246 'MsgT' B99410 0 0 3E0F0CC BAE336 'LopT' 31752D8 meson.dll TThread::TaskCall +85 31752D8 'MsgT' B99410 3E0F0CC BAE336 'LopT' 31752D8 0 meson.dll loopInTask +27 'LopT' 31752D8 0 0 3E0F86C BE101C 0 3E0F878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 31752D8 0 0 meson.dll TThread::TaskCall +85 31752D8 'LopT' B993E0 'LopT' 31752D8 0 0 3E0F86C meson.dll TThread::MsgLoop +45 'LopT' 3E0F16C 3E0F16C 11 0 0 0 0 meson.dll QuitWindowStart +176 0 0 22E570 22E570 22E7B8 22E7B8 720070 620065 meson.dll doTask +246 'Task' BBB740 0 0 0 0 22E570 22E570 meson.dll TThread::TaskCall +85 31752D8 'Task' BBB740 0 0 22E570 22E570 22E7B8 meson.dll modThreadRoot +FA 22E254 DCD80828 0 0 21281D8 3E0FF54 3E0FF54 3E0FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 21281D8 3E0FFD4 779219BB 21281D8 'tkS~' 0 MSVCR80.dll 0001:00001a47 21281D8 'tkS~' 0 0 21281D8 0 0 0 ntdll.dll 0001:000409bb ntdll.dll 0001:0004098e Thread ID: 00000D5C, Name: Server thread EAX:03C0E1D0 CS:001B EIP:77945E74 EFlags:00000246 EBX:021281D8 SS:0023 ESP:03C0E48C EBP: 03C0E4A8 ECX:00000006 DS:0023 ESI:03C0E4F8 FS: 003B EDX:00000014 ES:0023 EDI:03C0E89C GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 3C0E4F8 0 0 0 3BF828 3C0E514 BBA3AF 3C0E4F8 bdrock20.dll UGetMessage +25 3C0E4F8 0 0 0 42C610 76FAFD89 A9DD2801 3BFCA0 meson.dll WinMsgBlocker::BlockForMsg +2F 3C0EB60 3C0E830 0 0 0 6D 0 3C0EB0C meson.dll msgHelper +1EB 3BF828 1 3C0EF28 3C0F1EC 21281D8 3155A98 2B8 3BF828 meson.dll doTask +246 'Msg ' B98270 0 0 3BF828 1 3C0EF28 3C0F1EC meson.dll TThread::TaskCall +85 3BF828 'Msg ' B98270 3BF828 1 3C0EF28 3C0F1EC 21281D8 meson.dll TThread::MsgBlock +96 'Msg ' 3C0F198 BAE336 3C0F7DC BAE336 'LopT' 3BF828 0 meson.dll msgInTask +11 3C0F7DC BAE336 'LopT' 3BF828 0 0 3C0FE40 BE101C meson.dll doTask +246 'MsgT' B99410 0 0 3C0F7DC BAE336 'LopT' 3BF828 meson.dll TThread::TaskCall +85 3BF828 'MsgT' B99410 3C0F7DC BAE336 'LopT' 3BF828 0 meson.dll loopInTask +27 'LopT' 3BF828 0 0 3C0FE40 BE101C 0 3C0F878 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 3BF828 0 0 meson.dll TThread::TaskCall +85 3BF828 'LopT' B993E0 'LopT' 3BF828 0 0 3C0FE40 meson.dll TThread::MsgLoop +45 'LopT' 3BF108 3C0FE4C BAE336 0 0 60097F34 0 meson.dll serverThread +6E 0 0 60097F34 0 22E7B8 22E7B8 720070 620065 meson.dll doTask +246 'Task' B8F100 0 0 0 0 60097F34 0 meson.dll TThread::TaskCall +85 3BF828 'Task' B8F100 0 0 60097F34 0 22E7B8 meson.dll modThreadRoot +FA 22E254 DCF80828 0 0 21281D8 3C0FF54 3C0FF54 3C0FFC4 MSVCR80.dll 0001:000019bb 0 76FBD0E9 21281D8 3C0FFD4 779219BB 21281D8 'tKS~' 0 MSVCR80.dll 0001:00001a47 21281D8 'tKS~' 0 0 21281D8 0 0 0 ntdll.dll 0001:000409bb ntdll.dll 0001:0004098e Thread ID: 00000D6C, Name: Main thread EAX:0022C6D0 CS:001B EIP:77945E74 EFlags:00000246 EBX:00000000 SS:0023 ESP:0022C998 EBP: 0022C9B4 ECX:00000006 DS:0023 ESI:0022CA04 FS: 003B EDX:00000020 ES:0023 EDI:0022CDA8 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00064e74 22CA04 0 0 0 3A5C80 22CA20 BBA3AF 22CA04 bdrock20.dll UGetMessage +25 22CA04 0 0 0 3A7220 0 0 3A60F8 meson.dll WinMsgBlocker::BlockForMsg +2F 22D06C 22CD3C 0 0 0 5E 0 22D018 meson.dll msgHelper +1EB 3A5C80 1 22D434 22D6F8 0 50EE178 22D0BC 3A5C80 meson.dll doTask +246 'Msg ' B98270 0 0 3A5C80 1 22D434 22D6F8 meson.dll TThread::TaskCall +85 3A5C80 'Msg ' B98270 3A5C80 1 22D434 22D6F8 0 meson.dll TThread::MsgBlock +96 'Msg ' 22D6A4 BAE336 22DCE8 BAE336 'LopT' 3A5C80 0 meson.dll msgInTask +11 22DCE8 BAE336 'LopT' 3A5C80 0 0 22E348 BE101C meson.dll doTask +246 'MsgT' B99410 0 0 22DCE8 BAE336 'LopT' 3A5C80 meson.dll TThread::TaskCall +85 3A5C80 'MsgT' B99410 22DCE8 BAE336 'LopT' 3A5C80 0 meson.dll loopInTask +27 'LopT' 3A5C80 0 0 22E348 BE101C 0 22DD80 meson.dll doTask +246 'LopT' B993E0 0 0 'LopT' 3A5C80 0 0 meson.dll TThread::TaskCall +85 3A5C80 'LopT' B993E0 'LopT' 3A5C80 0 0 22E348 meson.dll TThread::MsgLoop +45 'LopT' 22E354 BAE336 B974A0 0 B 22E9A4 BAE336 meson.dll mesonGoLoop +14 B974A0 0 B 22E9A4 BAE336 0 22FEF8 6112C806 meson.dll doTask +246 'Task' B8F2C0 0 0 B974A0 0 B 22E9A4 meson.dll TThread::TaskCall +85 3A5C80 'Task' B8F2C0 B974A0 0 B 22E9A4 BAE336 meson.dll mesonGo +135 0 22FEF8 6112C806 0 0 0 0 77924AA2 meson.dll doTask +246 'Prog' B8F180 0 0 0 22FEF8 6112C806 0 meson.dll TThread::TaskCall +85 3A5C80 'Prog' B8F180 0 22FEF8 6112C806 0 0 meson.dll Meson +2C 0 0 0 0 77924AA2 77A946CE 22EABC 9 Retrospect.exe _WinMain +646 61100000 0 361DC4 1 DF192127 0 0 7FFDF000 Retrospect.exe ___tmainCRTStartup +140 7FFDF000 22FFD4 779219BB 7FFDF000 77A9537E 0 0 7FFDF000 kernel32.dll 0001:0004c0e9 7FFDF000 77A9537E 0 0 7FFDF000 0 0 0 ntdll.dll 0001:000409bb ntdll.dll 0001:0004098e [aside - the forum is broken - when you search, if you click on a topic it finds, it always goes to a bad page - the URL it generates is invalid]
  10. Hi I have a 2TB drive, the backups take up about 1TB and there are 800GB free. I'm running Vista and Retrospect Express HD 2.5.113. There are about 300 restore points. Whenever it tries to reclaim disk space it asserts at elem.cpp-993. I have seen this referenced in the release logs for Retrospect version 7, as a bug to do with pruning. To try to get mine working, I have removed and rebuilt the catalogue (which takes about 12 hours) and it still asserts at the same place. I have tried this twice, with suitable reboots to make sure it rebuilt it correctly. I have re-installed the software and that also didn't help. I am doing the pruning because I know from past experience that if I don't prune it now, it will die horribly when the disk gets too full. Is there any way to get my backup system working correctly again? Does the full retrospect work with the backup files from Express HD? Thanks Jeremy
  11. Do you mean the tutorial with title "Excluding Files or folders with Retrospect" I cannot find anything else relevant to excluding some folders, and in my post, I already had found what is relevant in the tutorial. 1. Such a basic behaviour should be implemented the same way in Professional as in Express HD - its bread and butter functionality, not sdomet 2. The tutorial forgets to say that you will then be backing up EVERYTHING except what you exclude, including temporary internet files etc. You have to also exclude these (as I said). This is a really messy unpleasant piece of interface to implement something very simple. 3. The 'private files' option is useless - I have my folders already, and I do not want to rename the things I do not want to back up, and change the things that depend on those folder names. 4. The 'easy' option in the tutorial is Mac specific and I am on PC. And the whole reason for trying Professional turns out to be useless anyway (to get functioning grooming) - I tried using the Grooming feature and it failed, also in elem.cpp, just at line 1091. And yes, I have rebuilt the catalogue in 7.7 as well, twice now - and I ave plenty of disk space free. I used to think Retrospect was the bees knees, but it turns out its long lost that accolade - maybe something to do with EMC, which I now know stands for 'Everything Made Complicated'...
  12. jez

    Grooming manually

    Hi I am trying to use the grooming facility in Retrospect 7.7 Windows to manually groom. I do not want to use the built in policy because it only keeps a few daily backups. The keep last x is no good as it only allows 99 - which is only 3 months of daily backups. I couldn't find any way to specify my own grooming policy? So I assume I will have to manually make it forget the backups I don't want - but this seems impossible. To get the option to Groom, you HAVE to choose one of the built in grooming policies (last x (1-99) or the other which keeps a few daily weekly and monthly). My first question is - if there is enough free space (backing up to disk) then will it only groom the snapshots I have told it to forget? Or will it use the policy, regardless of available space, and groom the snapshots I don't want to groom. Yes, I have found that I could lock them - but that is a pain because, for some reason, it only shows me about 3 snapshots. To get to the rest, I have to 'retrieve' them, which is painfully slow. Also I don't even get the 'lock' option unless I enable one of the grooming options. Aside - any way to actually make it retrieve all the snapshots without having to do them one by one? [update] Hmm - I just forgot to disable the grooming, so its set to keep last 99, and when I closed the window, it said it was retrieving old snapshots to stop them being groomed... Its now retrieving them, and I have turned off the grooming option again, so at least I will have all the snapshots back. Looks like I have to enable grooming, it retrieves the snapshots, I lock them, then set it to groom older than 99, and then periodically I go through and lock all the snapshots, so it doesn't actually groom them ??? Maybe I can make it always lock new snapshots, in the script? Sigh - this has to be the most bizarre program I have used in a long time.
  13. Well, I have gone ahead and bought the full Retrospect 7.7... I have to say - its a really _extremely_ unnecessarily confusing product - talk about making an easy task into something impossible. So in my old setup for Retrospect Express HD it was nicely backing up my C drive, except for 3 folders I had excluded. Apart from the bugs that made it crash when grooming, it would have been fine, but EMC appear to have stopped updating the Express HD version... In Retrospect it seems next to impossible to do this simple backup task nicely. The whole volume thing in the full version - its next to incomprehensible (and I have a maths and computing degree and 25 years in the software industry). The problem is that whatever I define, if I add a new folder at the top level of my C drive, then it isn't included in the backup. With Express HD, new folders automatically were added in, so nothing was missed. It looks as if the only way to do it is define a Volume, C:, and then go into the even more esoteric world of Selectors and set up some exclusions to eliminate the folders I do not want to back up. To to this I think I have to duplicate the selector 'All Files Except Cache Files' and then add in the folder exclusions as paths starting with and also exclude with things like System Volume Information. Please - there must be an easier way? As an aside - the documentation is truly terrible. Also, the wizard to make a script is useless - backing up some folders on a computers - that is mainstream backup, but the wizard offers no help whatsoever - it is either back up a drive, or it throws you into the volume hell. Also - their grooming method - keep last few days, last few weeks, and a monthly - is there any way to edit that? I want to keep the last 120 days, then weekly from before that - seems like I have to do a manual prune to do this? Also - why on earth didn't they think of a better name for things than folders and volumes - at least prefix them with something to indicate they are not real folders. I really wanted to not lose my backup history, which is why I got the full version - and that would work - but to be honest I really feel like just ditching the product. Sorry this is a rant, but I am really disillusioned. Having to waste hours of time and more money, because of a bug in a broken product is not my idea of fun. Its obvious now that there was a good reason to make the Express HD version - if EMC want to play in the consumer arena they need to do it with a solid product, not a cut down broken version they don't update. Anyway, please could you let me know if there is there an easy way to set up Retrospect to just back up a drive, and miss out some folders I don't want to back up, and automatically include any new top level folders I make?
  14. Good, thank you - maybe its just coincidence and there is a different problem. Still - this problem also happened on my old laptop with a different backup drive - I copied the backup files across to the new external when I changed laptop, and rebuilt the catalogue, and it all was working fine again until it hit 4gb (it had been auto-pruned down somewhere along the way). It would be good to hear someone out there who has currently got a large catalogue with Express 2.5 HD and is backing up regularly. The rebuild completed and I could do a backup. Catalogue file now about 3.9gb so I guess I will soon find out if mine will go over 4gb or not. Maybe coincidence, but just after this backup finished, I got an assert error: OS: Windows Vista version 6.0 (build 6001), Service Pack 1, (32 bit) Application: C:\Program Files\Retrospect\Retrospect Express HD 2.5\retrospect.exe, version 2.5.113 Exception occurred on 25/01/2009 at 00:05:47 Error info: Assertion failure at "memutil.cpp-252" Not sure if that is important. Thanks Jez
  15. Hi Several times now I have had to rebuild my catalogue, by removing the .rbc file. Each time, I noticed it was just under 4GB in size. Everything on the computer is NTFS - source drive, backup drive, other drives, so there should be no limit to the file size other than disk available (over 500GB). What happens is that on the backup that would take it over 4gb, it stops working in various ways. The most recent, it just had a series of failed backups - previously some sort of assertion failure and I cannot remember the others. Also this time, when I tried to remove a restore point, it ignored it - removes it when I click to remove, but then it is still there - so another rebuild is in progress to hopefulyl sort it again. I am using verison 2.5 of Retrospect Express HD. Has anyone out there got a .rbc file that is well over 4GB, and has working backups that they can restore from? Thanks. Jez.
×