Log Shipping without initial Full Backup

blakedba

Due to bandwith issues, I set up a seperate full backup and restore to our disaster database(READ ONLY). I tried using the GUI Log shipping with overwrite existing database...looks like it does a full backup angain and moving SEED file over network.

Is there a way I can get around this...

Thanks

John

Ben Pinchen

Unfortunately, if you use the GUI to set up log shipping it will always want to backup the source database, send it over the network and restore it on the destination. This is by design as most users using the wizard will require this to be done.

We will look into the possibility of allowing users to manually set-up their destination database for future releases.

The only way to workaround this would be to set the jobs up manually. If you set up a log shipping job with a small database, you can go to the SQL Server Agent jobs, find the backup and restore jobs and copy and edit these to reflect your main database. For more information regarding the log shipping process see -

http://www.red-gate.com/MessageBoard/vi ... g+shipping