Several options should do the trick, depending on what you want to do. To get as close as possible to your current procedure:
* On the box hosting the DVD burner, create a directory to hold incoming files. Share that directory over the local network (may require you to turn on file sharing) as winback (or whatever name you like). Assign a password or grant access via user, depending on how the box is set up.
* On each Windows box, use your favorite archiver (e.g. infozip) to bundle the files together, and send the result to \\dvdhost\winback\eachhostname.zip . If your archiver doesn't like UNC paths, NET USE J: \\dvdhost\winback will map the path to a drive letter.
* Burn the file(s) to DVD.
You can also reverse the sharing relationship (share a directory on the box to be backed up, sit at the DVD host and copy from said shared directory).
If you want to do file copies (e.g. for regular backups), take a look at Microsoft's robocopy. (Somewhat like rsync, but windows-specific.)
Note that a generic file copy won't preserver ACLs. If you want to do so, I'd suggest using ntbackup instead.
* On the box hosting the DVD burner, create a directory to hold incoming files. Share that directory over the local network (may require you to turn on file sharing) as winback (or whatever name you like). Assign a password or grant access via user, depending on how the box is set up.
* On each Windows box, use your favorite archiver (e.g. infozip) to bundle the files together, and send the result to \\dvdhost\winback\eachhostname.zip . If your archiver doesn't like UNC paths, NET USE J: \\dvdhost\winback will map the path to a drive letter.
* Burn the file(s) to DVD.
You can also reverse the sharing relationship (share a directory on the box to be backed up, sit at the DVD host and copy from said shared directory).
If you want to do file copies (e.g. for regular backups), take a look at Microsoft's robocopy. (Somewhat like rsync, but windows-specific.)
Note that a generic file copy won't preserver ACLs. If you want to do so, I'd suggest using ntbackup instead.
--Rick Owens