You could look at the constaints on the foreign key. Does it allow duplicates, does it allow nulls?

Here is suggestion which I have not tried with database backups but I have used from scheduling jobs with the windows scheduler. Create a batch program(text file with DOS commands, and with extension .bat). In the batch program connect to -iSQL and pass to it a .sql file that contains the backup instructions.--> That means you also have to create a .sql file. Now create a schedule in windows scheduler that executes the bat program Windows Scheduler calls mybackup.bat; mybackup.bat calls -isql which in turn calls mybackup.sql. Test the whole thing on test on test database.