Not sure if this is helpful, but I never could get the SQL agent running right with Arcserve 6.5 and SQL under WinNT 4.0, so I took the cheap way out- I dumped the database at regular intervals to a seperate volume and backed up the resulting dump as a file as opposed to backing up the database through the agent. Worked like a charm. My down time was minimal (2GB database) and my backups were 100% for a long time. I'm not sure if SQL 2000 is as easy, but previous versions made this the simplest solution. Since you're going over a network anyway, this might even be safer as far as restores are concerned. If it's a small database (under 800MB or so) you can probably dump the database several times a day and keep the dumps fairly handy in case a quick rollback is necessary. That one saved my bacon more than a dozen times, but you have to have the space available!