psk1
asked on
ASR backup "The files for the recovery diskette could not be created. The operation was aborted."
Often I can find a solution here or on the web without having to post a question, but this one's just not panning out for me:
I'm using Windows Server 2003 and when attempting to create an ASR backup I get the error "The files for the recovery diskette could not be created. The operation was aborted." The backup tool then just fails and really doesn't give any specific information why.
I've tried different floppies, I've tried different drives, I've tried looking for a missing component... I'm open to any and all suggestions at this point because this is just ridiculous.
Thanks.
I'm using Windows Server 2003 and when attempting to create an ASR backup I get the error "The files for the recovery diskette could not be created. The operation was aborted." The backup tool then just fails and really doesn't give any specific information why.
I've tried different floppies, I've tried different drives, I've tried looking for a missing component... I'm open to any and all suggestions at this point because this is just ridiculous.
Thanks.
Check this article if it is relevant for your setup. http://support.microsoft.com/default.aspx?scid=kb;en-us;316456
ASKER
The hard drives are RAID 0, but since Windows Server 2003 was installed freshly and no NT or other prior OS was ever installed on these drives, I'm not sure that the article is relevant, though it certainly could be. Regardless though, I don't seem to have the Ftonline.exe utility that is referenced in the article. I'm going to try to find it now.
ASKER
Installing SUPTOOLS.MSI from Windows Server 2003 installation CD under SUPPORT\TOOLS as per http://support.microsoft.com/kb/303246/EN-US/ ...
ASKER
So what is this fault-tolerant RAID setup? Maybe I'll ask this in another area but if someone knows I'd sure be glad to hear about my options. Maybe I should have set up my RAID differently?
The info in that article is only relevant if you had NT4 on the box before. Do you have any other messages in even log that can give some light to what causes this problem?
ASKER
No. The event log just repeats the error message.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sean,
That's useful information. But if the backup procedure halts before creating those files, I still have no protection.
That's useful information. But if the backup procedure halts before creating those files, I still have no protection.
If the server has sp1 on it I know why you are getting that error.
ASKER
Ah...the server DOES have SP1 on it... What's up, Dimante?
To work around this problem, there are four methods specified:
1. Replace Ntbackup program by using a third-party backup application that is not affected by this problem;
2. You can use the original release version of Windows Server 2003 or Windows Server 2000 SP4-based domain controllers; Note: Only Windows Server 2003 domain controllers can host and backup application partitions defined in a domain or a forest.
3. Put both the NTDS.DIT and Active Directory log files on a single volume with performance degrading in the process. Take your domain controller offline and resize disk partitions as required.
For more information about how to relocate the NTDS.DIT or Active Directory log files on a domain controller that booted into Directory Services Repair Mode, read the "how to move the database" or "how to move the log files" sections of this KB article, click the following article number to view the article in the Microsoft Knowledge Base:
816120 How to Use Ntdsutil to Manage Active Directory Files from the Command Line in Windows Server 2003
4. Add a dummy file in the log files directory with the archive bit set prior to performing a system state backup.
This is the exact word from MS on this You must have your log files and NTDS.DIT split up.
So the above mentioned will fix the issue. The dummy files goes in %systemroot%\system32\logf
-D-
1. Replace Ntbackup program by using a third-party backup application that is not affected by this problem;
2. You can use the original release version of Windows Server 2003 or Windows Server 2000 SP4-based domain controllers; Note: Only Windows Server 2003 domain controllers can host and backup application partitions defined in a domain or a forest.
3. Put both the NTDS.DIT and Active Directory log files on a single volume with performance degrading in the process. Take your domain controller offline and resize disk partitions as required.
For more information about how to relocate the NTDS.DIT or Active Directory log files on a domain controller that booted into Directory Services Repair Mode, read the "how to move the database" or "how to move the log files" sections of this KB article, click the following article number to view the article in the Microsoft Knowledge Base:
816120 How to Use Ntdsutil to Manage Active Directory Files from the Command Line in Windows Server 2003
4. Add a dummy file in the log files directory with the archive bit set prior to performing a system state backup.
This is the exact word from MS on this You must have your log files and NTDS.DIT split up.
So the above mentioned will fix the issue. The dummy files goes in %systemroot%\system32\logf
-D-