Preventing Silent Failures in MS-DOS Batch Backups

The risk of the silent failure

When automating file operations in MS-DOS, the primary engineering challenge is the "silent failure." If a source drive is missing, a disk is full, or a file is locked, a standard batch script will often proceed to the next line as if nothing happened. This leaves the user with an incomplete backup and a false sense of security. To build a reliable backup system, you must move beyond simple copy commands and explicitly evaluate the ERRORLEVEL variable after every critical operation.

MS-DOS batch files are plain-text scripts executed by COMMAND.COM. While they provide basic logic through loops and conditionals, they lack structured exception handling. The solution is to rely on the return codes provided by core commands to ensure data integrity.

Binary integrity and variable parsing

In a legacy MS-DOS environment, the standard COPY command may treat files as text by default. This can lead to control characters being translated or stripped, which corrupts binary files like archives, executables, or database files. Using the /B switch forces a binary-stream copy, ensuring the destination file is a bit-for-bit match of the source.

Another technical hurdle is how variables are expanded. In standard MS-DOS batching, variables like %VAR% are expanded at parse time. If you update a variable inside a loop, the value will not update for the duration of that block. While later versions of the command processor introduced delayed expansion (!VAR!), the most portable approach for legacy DOS is to keep logic linear or use temporary files to store state.

Example: A verifiable backup script

The following script backs up files from C:\DATA to D:\BACKUP. It includes checks for the destination directory and the success of the copy operation. Run this within a DOS environment or emulator with administrative access to the specified drives.

@echo off
REM BACKUP.BAT - copy data set with explicit checks

REM Ensure the backup destination directory exists
IF NOT EXIST D:\BACKUP (
    MD D:\BACKUP
)

REM Check if directory creation failed
IF ERRORLEVEL 1 (
    ECHO Error: Could not create backup directory.
    GOTO END
)

ECHO Copying files from C:\DATA to D:\BACKUP...
COPY /B C:\DATA\*.* D:\BACKUP\

REM Check if the copy command succeeded
IF ERRORLEVEL 1 (
    ECHO Backup failed! Check source drive or disk space.
) ELSE (
    ECHO Backup completed successfully.
)

:END
pause

Trade-offs and limitations

While effective for simple tasks, batch scripting has distinct constraints that impact engineering decisions:

• No Unicode Support: MS-DOS does not support Unicode. Filenames with non-ASCII characters will be corrupted or misinterpreted.
• Synchronous Execution: Scripts run synchronously. The command prompt is blocked until the copy finishes, meaning you cannot run concurrent backup tasks without separate system instances.
• Manual Logging: There is no built-in logging system. To maintain a history of operations, you must manually redirect output to a text file using the > operator (e.g., COPY /B ... > backup.log).

Verification and result checking

To confirm the backup worked, perform a manual comparison of the source and destination. Use the DIR command to check file counts and timestamps:

1. Run DIR C:\DATA /T:C to view source creation timestamps.
2. Run DIR D:\BACKUP to verify the files exist in the destination.
3. Test the failure path: Temporarily point the script to a non-existent source (e.g., C:\NOPE\*.*) and confirm that the IF ERRORLEVEL 1 branch triggers the error message.

Actionable closing

When automating in MS-DOS, never assume a command succeeded. Always use the /B switch for binary integrity and check the ERRORLEVEL immediately after every file operation to prevent silent data loss.