M
Matthew Mucklo
Discovered why a perfectly good Windows 2000 backup set will fail on
Windows XP(maybe this isn't a mystery for some, but I couldn't find
the answer on Google, so I'm posting it for your benefit).
This is useful to anyone who has tried to modify the bks files that
windows produces to create custom windows backup scripts.
Windows 2000 .bks files - Need to contain the magic number "FF FE" at
the beginning of the file (visible in any Hex editor). Solution -
edit the file in Notepad.
Windows XP .bks files (at least for XP Pro which was my test case) -
Need a regular MSDOS text file (no magic number). Solution - edit the
file in 'Edit' from a DOS prompt.
Unfortunately they don't seem to be compatible with one another. A
real mystery until I started viewing the files in a hex editor.
However if you automate a backup you can place these .bks files
anywhere, even on a mapped network drive to which you later backup to
(contrary to some opinions).
Here is an example using an SBS 2000 based network:
DOS Batch file. Make a shortcut to this on the person's desktop by
browsing over the network (using My Network Places) to find the file,
then even the backup script itself willc live on the network:
------------------------------------------------------------
REM Example Full Backup Script
REM Map the Backup Drive
net use t: "\\your-server\Backup Drive"
REM Map the user's home directory
net use u: "\\your-server\Users\%USERNAME%"
REM Make a directory on the backup drive for the user should one not
exist
mkdir t:\%USERNAME%
REM The .bks file lives on the mapped drive u:, then you backup to the
other mapped drive t:
%SystemRoot%\system32\NTBACKUP.EXE backup "@u:\Backup
Scripts\BackupSet.bks" /n "Media created %USERNAME%" /d "Set created
%USERNAME%" /v:no /r:no /rs:no /hcff /m normal /j "FullBackup" /l:s
/f "T:\%USERNAME%\%USERNAME%.bkf"
net use u: /DELETE
net use t: /DELETE
Windows XP(maybe this isn't a mystery for some, but I couldn't find
the answer on Google, so I'm posting it for your benefit).
This is useful to anyone who has tried to modify the bks files that
windows produces to create custom windows backup scripts.
Windows 2000 .bks files - Need to contain the magic number "FF FE" at
the beginning of the file (visible in any Hex editor). Solution -
edit the file in Notepad.
Windows XP .bks files (at least for XP Pro which was my test case) -
Need a regular MSDOS text file (no magic number). Solution - edit the
file in 'Edit' from a DOS prompt.
Unfortunately they don't seem to be compatible with one another. A
real mystery until I started viewing the files in a hex editor.
However if you automate a backup you can place these .bks files
anywhere, even on a mapped network drive to which you later backup to
(contrary to some opinions).
Here is an example using an SBS 2000 based network:
DOS Batch file. Make a shortcut to this on the person's desktop by
browsing over the network (using My Network Places) to find the file,
then even the backup script itself willc live on the network:
------------------------------------------------------------
REM Example Full Backup Script
REM Map the Backup Drive
net use t: "\\your-server\Backup Drive"
REM Map the user's home directory
net use u: "\\your-server\Users\%USERNAME%"
REM Make a directory on the backup drive for the user should one not
exist
mkdir t:\%USERNAME%
REM The .bks file lives on the mapped drive u:, then you backup to the
other mapped drive t:
%SystemRoot%\system32\NTBACKUP.EXE backup "@u:\Backup
Scripts\BackupSet.bks" /n "Media created %USERNAME%" /d "Set created
%USERNAME%" /v:no /r:no /rs:no /hcff /m normal /j "FullBackup" /l:s
/f "T:\%USERNAME%\%USERNAME%.bkf"
net use u: /DELETE
net use t: /DELETE