Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by haggis999

  1. I have just upgraded to Retrospect Professional 7.7.341 (64-bit) on my new Windows 7 Ultimate 64-bit PC and I am trying to run my first 'Duplicate' session in this new environment, duplicating a folder on the PC to an external hard disk. Previously I was running Retrospect Professional 7 under Windows XP and had no problems in duplicating a similar folder to the same external disk.


    Unfortunately, the duplication session fails just a few seconds after starting. The session log information is shown below.


    The log implies that the external drive is not ready to accept the writing of files. This is difficult to understand as my Retrospect session was preceded with some folder renaming on the disk using Windows Explorer, which worked fine. However, Retrospect does trigger an unexpected AutoPlay dialogue box every time I try to run the duplication.


    Needless to say, the Help in Retrospect lists nothing for this error code. Any suggestions on how to resolve this problem?






    + Executing Immediate Duplicate at 28/12/2010 11:29

    To volume My Pictures - DUPLICATE B on LaCie750 DiskB (L:)...


    - 28/12/2010 11:29:40: Copying My Pictures on MyData1 (G:)

    File "G:\My Pictures\Archive\Derivatives\DERIV_003\DCA_100616_9789 - 16E4.tif": can't write, error -1104 ( device not ready)

    Trouble writing files, error -1104 ( device not ready)

    28/12/2010 11:29:49: Execution incomplete

    Remaining: 4317 files, 17.1 GB

    Completed: 1 files, 138.2 MB

    Performance: 1036.0 MB/minute

    Duration: 00:00:08



  2. You may well be right that XP SP2 contained more than just a collection of Hotfixes but I think it unlikely that many significant bug fixes were not initially issued as a Hotfix. My question still stands, however. Is it necessary for smooth operation of Retrospect to ensure that the hotfixes on a recovery PC match the hotfixes that were installed on the failed PC?

  3. Quote:

    one thing to make sure is that when doing a full system restore is to make sure that you have the same service pack installed that was backed up. So if you had Win XP SP2 installed at the time of back then you will need to reinstall Win XP SP2 before the restore.



    A Win XP Service Pack is just a collection of previously issued Hotfixes. What about all the Hotfixes applied since the last SP? Are they important in a restore situation?



  4. Windows XP Service Packs don't come out very often, so maintaining a Windows installation CD with the latest SP added via 'slipstreaming' is not much of a problem. The i386 folder from this Windows installation CD is, of course, a vital component of the Retrospect DR CD. However, what about all the Hotfixes that Microsoft issues on a monthly basis in between Service Packs? Would it matter if your PC had one set of Hotfixes while your Retrospect DR CD was based on an i386 folder with a different set of Hotfixes?



  5. Russ,

    Thanks for the gracious and rapid apology. However, I am in no position to claim the moral high ground. As my wife will confirm, I'm becoming a grumpy old man and my own lapses in tact and diplomacy are becoming ever more frequent...


    I found your comments very interesting - and a little worrying. Over here in the UK, I have read nothing about what is going on at EMC. Is the future of Retrospect in some doubt?



  6. Russ,

    That sounds a bit dismissive. Have you got an issue with my earlier comments?


    The only reason I have resurrected this thread is that the topic keeps re-occurring on this forum and is thus obviously a regular source of user confusion. If EMC were to provide a more informative and more practical KB article on the subject then such confusion might be reduced. Is that not a desirable objective?



  7. Quote:

    I've used nLite to build several slipstreamed XP install disks. Very easy to use.



    I'm trying to use nLite right now for the first time but I'm getting confused at a very early stage. The link it provides to a Microsoft website to download the SP2 upgrade for Win XP Pro doesn't lead me anywhere useful. The SP2 upgrade is already installed on my PC and the website seems to be hiding any link for downloading it again for use by nLite. Can anyone tell me how to do this (or how to find the relevant file already on my PC, if that's a better alternative)?



  8. I am planning to replace my existing C: disk (containing Windows XP Pro and all my apps) with a larger disk and I would prefer not to reinstall everything from scratch. Would a Retrospect 7.0 DR CD restore my system successfully in such circumstances or is it limited to a disk of the same size as before?


    Apart from the time-saving aspect of such a procedure, I am also viewing this as an opportunity to test the DR process.



  9. Quote:

    Apparently you are under the mistaken impression that this forum is something other than user-to-user support.




    No, I am not confused in the slightest. There are a few EMC employees who participate in these forum discussions and I was simply trying to provoke a reaction from one of them. I'm certainly not planning to pay a substantial fee for the privilege of reporting flaws in EMC documentation - if anything, they should pay me! smile.gif.



  10. Quote:

    The Disaster Recovery CD MUST be at the same service pack level as the backup. For Windows XP, this is an absolute must [i.e., I have experience with it]. Not absolutely sure for other versions of Windows.



    My original Win XP Pro CD is at SP1, but my PC has been upgraded to SP2. Are you saying that the i386 folder used in creating the Retrospect DR CD cannot be taken from my original Win XP Pro SP1 CD but must be taken from a slipstreamed SP2 version?


    What about all the monthly Windows updates I have applied since SP2? Must they be also be slipstreamed into the CD from which the i386 folder is extracted?



  11. Personally, I would be extremely surprised (and disappointed) if it matters which drive you choose for installing Retrospect. However, you could never go wrong with installing an application on the C:\ drive. If any programmer were stupid enough to hard code any drive dependencies then the C:\ drive would be the obvious one for him to choose.



  12. When I create new Backup Sets, I am prevented from entering a name longer than 20 characters. Surprisingly, this rather irritating limitation does not appear to be documented. The User's Guide tells me that a CD/DVD Backup Set name cannot be changed, but 'File' Backup Sets can be renamed with Windows Explorer.


    Is it totally safe to rename a Backup Set? Would a Disaster Recovery CD based on the original Backup Set name still work with a renamed version of that Backup Set?



  13. Quote:

    You should be very careful with the duplicate option. If you are selecting the entire external harddrive as the destination for your duplicate, it will erase any files on the destination that do not exist on source. It will then copy over the new and changed files to the destination. The safer way to do it is to create a subvolume on your external harddrive called "Duplicate of XYZ" and set that as the destination. When you perform the duplicate, it will only affect the files in this folder and the rest of the files on your external harddrive will be untouched.



    Good point, Ronald! From the beginning, I just knew instinctively that creating a 'Duplicate of XYZ' subvolume was the correct approach, but that might not be so obvious to many other users - with potentially disastrous results. I will be slightly more cautious in future about telling people not to worry about this warning message!



  14. I was just referring to the normal Help at the right hand side of the main menu across the top of the Retrospect window. Click on Help and then Contents. The topic is also covered on p 35 of the printed User's Guide.


    If it is not a configuration issue, then it might be that another application (possibly DVD burning software) has grabbed the drive and is not letting Retrospect see it.



  15. I decided to press ahead with the 'Continue' option after receiving the over 650MB warning. The resulting ISO file was 651MB in size, and did NOT include the catalog file. Roxio 8 was able to successfully burn this to a 700MB CD-R.


    It looks as if this warning message is just there to cause unnecessary confusion and panic, a situation compounded by the utterly ridiculous KB advice to obtain a non-OEM version of the Windows installation CD! mad.gif. In over 20 years as an IT Manager, I hardly ever purchased a retail copy of Windows, because every new PC came with an OEM version of the operating system. If I had been stupid enough to follow EMC's advice, it would have cost me £159 GBP in the UK to buy the retail upgrade version of Win XP Pro. I would then have had two valid Windows licences for the same PC, just to get round a phantom problem in Retrospect!


    If anyone from EMC is reading this, can you please try to ensure that a more helpful KB article is created on this topic. This should address the following issues,

    • The statement that the catalogue file is one of the main things that are included on the DR ISO file is patently untrue in some cases. This needs to to be made clear.

    • Users should be advised that the 650MB limit is rather conservative, given that 700MB CD-R disks are now widely available.

    • Any suggestion that it is wrong to use an OEM version of the Windows installation CD should be deleted

    • Some advice about files or folders that could safely be deleted from the i386 folder is almost essential (alternatively, a list of the vital files could be supplied). How else can a user know how to cut down the size of an OEM version of the i386 folder?


  16. I have just tried to create a new Disaster Recovery CD-R from Retrospect Professional 7.0.326 and have received a warning message that the Disaster Recovery image file will be over 650MB and thus too big for most disk burners to handle. The only thing I am aware of having changed since my last (successful) attempt to create a DR CD is the Snapshot. I have read several existing threads on this forum about this subject, but have not found them particularly helpful. I have also read the KB article' 'Why is my Disaster Recovery ISO file too big for the CD?'



    This KB article identifies the following as the contents of the DR CD (with the sizes on my PC),


    SIZE .......... FILE/FOLDER

    39MB ......... C:\Program Files\Dantz\Retrospect

    67MB ......... C:\Documents and Settings\All Users\Application Data\Retrospect

    33MB ......... C:\WINDOWS\system32\drivers

    502MB ....... i386 folder from my Dell Win XP SP 1a Reinstallation CD

    123MB ....... Catalogue file for the Backup Set used for this DR




    The KB article says that the i386 folder might be too large if it is from an OEM version of Windows, as if users have a choice in the matter. Surely almost every PC on the planet is supplied with an OEM version of Windows! Is EMC expecting me to go out and buy a retail version of Windows just so their DR facility can work?


    Even if I were to delete the i386\LANG folder as some have suggested is possible (but with no confirmation from one of the EMC gurus), I only save 99MB which still leaves me over the limit. Can anyone please explain how I resolve this problem?


    As a secondary issue, how do I address the issue of my Windows XP reinstallation CD being at Service Pack 1a while my PC is currently running at SP2 with plenty of subsequent updates via the Windows Update service?



  • Create New...