Hi,

Please refer to this article.

http://support.microsoft.com/default.aspx?scid=kb;...

You may have to replace the ntdll.dll file from another installation of Windows 2000.

Thanks and regards,

Note : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

Hi Jim,

The short answer is "no".

The long answer is:

I beleive the issue you have is a known issue. I beleive if you apply the latest hotfixes it is supposedly fixed. But then you'll run into further issues and it still won't work.

As for miracles, try this:
1. Install Windows 2003
2. Install Veritas
3. Inventory and catalogue tape
4. Restore c: and System State

Seriously, IDR is just a wizard that automates the above, so the fact it's bug ridden doesn't pose any serious issues- just work around it.


As a Veritas reseller, we don't push nor supply if asked IDR options, because we can't deal with people wanting their money back. We have discussed this with Veritas and informed them we would reverse this position if only a tech could demonstrate that the product can in some circumstance work. They were not able to do any more than refer us to this forum.

Hello,

Please update us on this issue.


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

Sounds like I am in a very very small minority. Yes, I have had IDR working.

It was over a couple of years ago, at a different company. We had several business-critical servers initially running NT4 and Backup Exec 8.6. I was tasked with writing Disaster Recovery procedures for the Windows servers, because all the Unix servers (etc) had them and the Windows servers didn't.

And it took maybe a month or two... and somehow I still have hair...

But we were recovering the servers using IDR disks (3.5 inch, 1.44 MB) and tape backups (Ultrium) which were stored offsite - the whole DR concept was taken extremely seriously. I wouldn't know where to begin with an IDR from a "backup to disk folder".

Just when we got the NT4 IDR procedure licked, the company started migrating the servers to Windows 2000, and the OS upgrade made the entire IDR process more difficult: The IDR 3.5 inch disks are now server specific instead of generic, and I'm not sure we had the Windows 2000 IDR working to the same level of reliability before I left that company. Windows 2000 was even more prone to the dreaded STOP error if it was slightly upset by trivial differences that it couldn't be bothered to correct. So I can well understand your frustration with Windows 2003. When it works, it is fantastic. But when it doesn't work...

If it will help, I'll see if I can still lay my hands on the NT4 / BE8.6 procedure that worked back then. I've not had to update it as my current employers don't require such extreme contingencies.

Best wishes,
Keith

Hello Jim,



Could you please Update us on the issue?



NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered
and would be moved to answered questions pool.

*************************************************
************************************************

Hi Shweta,

You may want to read these posts once in a while.

I go and state IDR simply doesn't work, and you reply asking for an update, as though I'd resolved the issue.

Yes Shweta, IDR doesn't work, that perfectly answers everybody's questions.

Hello,

Please update us on this issue.

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

sorry for not getting back to this sooner, the boss put it on hold for a while. but i have yet to get it to work in any way shape or form. i cannot belive we paid for this and that companies haven't filed a class action suit of this.

if its not catalog files it's something else like " set cannot {insert your favorite item here} " what a pain.