There is a often underlooked replication option available in MSSQL 2000 called "Attach & Go", this allows you to take a local replicated database and "Attach" it to a remote machine and you should be good. The key words to look up in BOL are "sp_copysubscription" and "sp_attachsubscription". These keywords should get you going to see if it would apply, the nice benefit of these are that there are no remote BCP of snapshots, and no daily/weekly snapshots needed (if you want them). As long as your local copy of the replicated database is up to date. [I've had great sucess with with, but I've only really used transactional replication. The approach is a lifesaver as it misses all the DB contention when dealing with snapshots]
Finally now I've hopefully wetted your appetites, there is the age old computer question...
Q: What is the fastest way to move 50Mb/1Tb/50Tb from one datacenter to another 50 miles away. VPN/FTP/Compressed etc?
A: Stick it in a car/truck and drive it! [Preferably on an attachable drive rather than tapes]
Obviously I have no idea if that approach would have applied in this case (physical security etc), but if you need to get a system up quickly that is often the fastest way and is most commonly overlooked in our connected world :-)