veejuu Posted August 7, 2006 Report Share Posted August 7, 2006 I was trying to create an ISO image to burn a CD-R from. The whole process runs on well, including print-out of the information. It clearly tells me the name and location of the ISO file which I need to burn a CD-R, however at the described location there is no such ISO file. Infact, anywhere on my entire harddisc is the file! I tried search function, I tried manually searching through the file explorer ... with no luck! The ISO-file Retrospect says it has successfully created is just not there! What can I do? System: WIN XP SP2 Retrospect: 7.06 Professional Link to comment Share on other sites More sharing options...
nekr0phage Posted August 8, 2006 Report Share Posted August 8, 2006 Hi, When you go through disaster recovery image creation you can specify where the image file will be stored. I would try creating the image again and saving it in a place like the root of the C: drive where there are no potential problems with hidden files or user permissions. Link to comment Share on other sites More sharing options...
veejuu Posted August 9, 2006 Author Report Share Posted August 9, 2006 I am not a pc-specialist (albeit a fairly experienced user) - so is my interpretation correct that "root of the c: drive" simply means directly on C: and not in any folder that resides on C:? That's what I did - I tried to save the iso-image directly to C:xxxx.iso - with no result. There is nothing visible and a search of the entire harddisc does not reveal the needed file. Link to comment Share on other sites More sharing options...
nekr0phage Posted August 9, 2006 Report Share Posted August 9, 2006 Hi Veejuu, When you go through the disaster recovery wizard it should take a good 5-10 minutes to create the image. Is this what you see when you create DR or does it finish immediately? Link to comment Share on other sites More sharing options...
veejuu Posted August 11, 2006 Author Report Share Posted August 11, 2006 Hi Foster, It took about 4 minutes to create the image file (resp. until the program said "finish"). Link to comment Share on other sites More sharing options...
nekr0phage Posted August 14, 2006 Report Share Posted August 14, 2006 Veeju, It sounds as if the file is being created. Can you compare the used space on disk before DR creation with the used space after? You would want to see a decrease of ~600MB. You might also try directing the DR wizard to store the .iso file in a new (empty) directory on your drive, that way you can simply get properties on that folder to determine whether the file is being created but is hidden, or if the file is not actually being created. Link to comment Share on other sites More sharing options...
mee Posted August 20, 2006 Report Share Posted August 20, 2006 Quote: I was trying to create an ISO image to burn a CD-R from. The whole process runs on well, including print-out of the information. It clearly tells me the name and location of the ISO file which I need to burn a CD-R, however at the described location there is no such ISO file. Infact, anywhere on my entire harddisc is the file! I tried search function, I tried manually searching through the file explorer ... with no luck! The ISO-file Retrospect says it has successfully created is just not there! What can I do? System: WIN XP SP2 Retrospect: 7.06 Professional I have the exact same problem, with Retrospect 7.5.285 (latest update). I have tried many times. Each time there is a report that the .iso was created successfully, but I cannot find it. I have tried saving it to different locations, but it is never there. I have done searches of all my HDs for *.iso, but that one is never there. (BTW, I have Explorer set to show hidden files, extensions, etc.) I also read a post from someone else, a couple months earlier, using 7.0, having this problem. I'm having it with 7.5. There are probably others, who never bothered to write here. I hope someone can solve this problem! Link to comment Share on other sites More sharing options...
mee Posted August 20, 2006 Report Share Posted August 20, 2006 Here's the earlier thread I saw: http://forums.dantz.com/ubbthreads/showflat.php?Cat=0&Board=professional&Number=72159 I e-mailed that poster, and asked him if he found a solution. He has not. I hope the Retrospect programmers are investigating this problem! ----------------------------------------- My system--Windows XP Pro SP2, latest updates Link to comment Share on other sites More sharing options...
veejuu Posted August 22, 2006 Author Report Share Posted August 22, 2006 Foster, the ISO image is never actually created - the total amount of available diskspace does not change upon trying to create an iso-image. veejuu Link to comment Share on other sites More sharing options...
veejuu Posted August 22, 2006 Author Report Share Posted August 22, 2006 ... and of course I have already tried to specify a specific location to save the supposedly created iso-file to - just to be sure it is not hidden anywhere on my harddisc. Link to comment Share on other sites More sharing options...
nekr0phage Posted August 22, 2006 Report Share Posted August 22, 2006 Veejuu, Mee, Could you both verify that Add/Remove programs displays the correct Retrospect version. In addition to that try uninstalling Retrospect, rebooting and reinstalling the current version. That's basically what we did to get around this problem with the customer I alluded to in my post to Bill (thanks for digging up that thread, mee). Link to comment Share on other sites More sharing options...
mee Posted August 25, 2006 Report Share Posted August 25, 2006 Foster, I might try the uninstall and reinstall. Bill, by the way, has not solved the problem on his system, from his response to my e-mail. Yes, I'm sure I have the latest version. However, since this seems to be happening to multiple users (probably many more who didn't bother to write), I think there is a bug there in Retrospect, which the developers should be investigating, and working on a fix for ASAP. Link to comment Share on other sites More sharing options...
mee Posted August 25, 2006 Report Share Posted August 25, 2006 Quote: However, since this seems to be happening to multiple users (probably many more who didn't bother to write), I think there is a bug there in Retrospect, which the developers should be investigating, and working on a fix for ASAP. Besides those who didn't bother to write, probably many users haven't yet tried to create the disaster recovery disks. When (if) they try it, they might also encounter this problem. So--the problem could be much more widespread than you think. Link to comment Share on other sites More sharing options...
nekr0phage Posted August 25, 2006 Report Share Posted August 25, 2006 Quote: Quote: However, since this seems to be happening to multiple users (probably many more who didn't bother to write), I think there is a bug there in Retrospect, which the developers should be investigating, and working on a fix for ASAP. Besides those who didn't bother to write, probably many users haven't yet tried to create the disaster recovery disks. When (if) they try it, they might also encounter this problem. So--the problem could be much more widespread than you think. I disagree. I myself, as well as others I personally know, have succesfully created disaster recovery images with the current version of Retrospect. Also, I have talked to people using different versions of Retrospect who have encountered this issue. So while it will happen occasionally to different customers, it is probably an environmental issue rather than a bug within the software. Link to comment Share on other sites More sharing options...
mee Posted August 25, 2006 Report Share Posted August 25, 2006 Quote: Quote: Quote: However, since this seems to be happening to multiple users (probably many more who didn't bother to write), I think there is a bug there in Retrospect, which the developers should be investigating, and working on a fix for ASAP. Besides those who didn't bother to write, probably many users haven't yet tried to create the disaster recovery disks. When (if) they try it, they might also encounter this problem. So--the problem could be much more widespread than you think. I disagree. I myself, as well as others I personally know, have succesfully created disaster recovery images with the current version of Retrospect. Also, I have talked to people using different versions of Retrospect who have encountered this issue. So while it will happen occasionally to different customers, it is probably an environmental issue rather than a bug within the software. A bug does not only exist if it happens to every user in every situation. It is clear that this is a problem, having occurred to multiple users. EMC should really be investigating this. By the way, I have created ISOs with other programs, without problems. As (I think) you are the EMC employee providing support on this forum, have you reported this problem to the software developers? Are they looking into it? Link to comment Share on other sites More sharing options...
nekr0phage Posted August 25, 2006 Report Share Posted August 25, 2006 Mee, Again, I disagree. I am well aware that a bug does not need to occur with every single installation. My point is that people are performing this operation succesfully, and that infers that the limited number of users experiencing this problem may either have something configured incorrectly (which was the case with the other user I referenced in my previous post), or there is another variable in their environment that is causing this issue. It is clear that there is a problem, it is *not* clear that this is a problem with the software. Until such time as this can be reliably reproduced and the application can be shown to be at fault, it is not something for developers to be concerned with. Now, would you like to continue troubleshooting your problem? Link to comment Share on other sites More sharing options...
mee Posted August 25, 2006 Report Share Posted August 25, 2006 Quote: Mee, Again, I disagree. I am well aware that a bug does not need to occur with every single installation. My point is that people are performing this operation succesfully, and that infers that the limited number of users experiencing this problem may either have something configured incorrectly (which was the case with the other user I referenced in my previous post), or there is another variable in their environment that is causing this issue. It is clear that there is a problem, it is *not* clear that this is a problem with the software. Until such time as this can be reliably reproduced and the application can be shown to be at fault, it is not something for developers to be concerned with. Now, would you like to continue troubleshooting your problem? As I mentioned, you (nor I) have no idea how many people have had this problem, and how many have performed the operation successfully. The ratio of one to the other is unknown. The fact that several people have reported the same problem, indicates that there is definitely a problem. Could it have something to do with interaction with some background program, service, etc. Of course it could! That could be said of most software problems. If that is the case, it is probably an interaction with a a commonly used program, since several people have reported the problem. If that is the case, you certainly should look into it, and try to fix it. The fact that a problem might have something to do with an interaction with something else in the software environment, does not mean that there is no problem! Developers of software programs try to make them compatible with other common software programs, and minimize conflicts. So yes, developers should be concerned if their program is not working as it should for some people, even if that is caused by some kind of environmental interaction, even if the problem does not occur with every user on every system. Regarding your last question, about continuing troubleshooting, of course. Do you have any other suggestions? (By the way, the reason Bill doesn't write here any more, is that he got tired of writing about this problem, with no solution offered for it, that worked for him. I guess that's one way to handle tech support--put people off, tell them nothing's wrong with your software, until they get tired of writing about it, and stop complaining. I don't think that's a very good way to handle it though, and not a good way to encourage customer loyalty.) Link to comment Share on other sites More sharing options...
RonaldL Posted August 25, 2006 Report Share Posted August 25, 2006 Hi mee, Could you download Filemon: http://www.sysinternals.com/Utilities/Filemon.html Run it while creating the ISO. You can go to Options>Filter/Highlight and put Retrospect in the Include field. Try the DR creation process again and see whether there are entries showing Retrospect attempting to write to the location you've specified. (Wait for it to get to the point where Retrospect is saying "Creating ISO". Also, could you navigate to the folder where you are saving the file to see whether the file starts to be created and then gets deleted or is never created in the first place. Be sure to update to 7.5.320 if you have not already. If all this fails, we may need to have you start with brand new configuration files to see if the same problem persists. As a test, you can go to c:\Documents and Settings\All Users\Application Data and rename the Retrospect folder to Retrospect-old. Relaunch Retrospect and enter your license code. Add in your existing backup set catalog and attempt the DR ISO creation process again. If this does not work, you can rename the Retrospect-old folder back to Retrospect to get all of your settings back. If this still fails, I would lean towards a software conflict and we should start to investgate which program could be possibly causing it. Link to comment Share on other sites More sharing options...
mee Posted August 28, 2006 Report Share Posted August 28, 2006 I posted a response to Ronald's post earlier today. For some strange reason my post doesn't appear now. Fortunately I had saved the text in Clipmate, so I can easily repost it. If it ends up appearing twice, you can delete this second one. I cannot see my post hours later though, including after refreshing the screen. My post from this afternoon appears below---------------------- Thanks, Ronald. These are the most constructive (diagnostic) suggestions I have seen so far. I will try these procedures sometime soon, and let you know the results. If any of the others who have this problem (if any are still reading) try these diagnostic procedures, please post your results. (By the way, I did try the earlier suggested procedure of uninstall, reboot, reinstall, reboot, and that didn't help. Still had the same problem.) I didn't know there is now a version 7.5.320. I have 7.5.285. Yes, I will download the update. (P.S.-later I see the link to 7.5.320 is no longer there, although it is mentioned on the update page. I saw another post that said it was withdrawn to fix a few bugs. Before making it available, you might want to check if there is anything in the code that could possibly be causing this problem of disappearing ISOs, even though not on all systems. I haven't yet had a chance to try the diagnostic procedures you mention, but I will do them when I can.) Link to comment Share on other sites More sharing options...
mee Posted September 2, 2006 Report Share Posted September 2, 2006 bump Link to comment Share on other sites More sharing options...
mee Posted September 4, 2006 Report Share Posted September 4, 2006 I just upgraded to the newest build, 7.5.324, and lo and behold--now in the process of creating the .iso, and I see it is really working. So, to whomever has this problem, make sure you update to this new build. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.