by John Paul Mueller.Now, I'm personally on a mission to kill Symantec Backup Exec, it's sort of a hobby of mine, so I'm using a number of F/OSS tools to get that done. A lot of those tools are command-line, such as Robocopy from the Windows Server 2003 Resource Kit, or Linux-based such as RESTORE.
One thing I was looking for was a light-weight SendMail type of application, without all of the overhead of SendMail. I found it in SendEmail. This nifty little app allows you to quickly send a text-based email message. You simply drop into one of your Path folders in Windows, set it up with the necessary parameters in a batch file, and the SendEmail app takes over from there.
So how am I using this with my backups? Well, I have Robocopy doing backups of critical data to a backup server with a SAN connection. Each individual server runs a batch script on a schedule that robocopies data to the appropriate folder on the Backup server. In the batch file, I have a sendemail snippet that notifies when the job begins, then the robocopy does it's thing, then the another sendemail notice telling me it's done, and a pause so that the cmd window waits for input.
Why the pause at the end? This way I or one of my guys has to log into each server every morning to confirm that the backup job ran and is complete. The robocopy also writes a log file, telling me where the errors are located, if any, so we just resolve the errors and we're ready for the next day's backup.
Pretty cool, eh? Critial backups, performed every day, on a schedule, with notifications, and NO BACKUP EXEC! We also use RESTORE to make snapshots, for archival purposes, but I haven't quite gotten that tweaked completely out yet.
More on that next time...
