Dear Friends

Thanks to Pual.

Now if i want to do the following solution suggested by
Mr. Paul it is giving me problem as when i take the
database backup it is 1.2GB and i can not transfer this
big file everyday from my branch to main office. ( takes
too much time ) so what i did is.

1. Created a maintaince plan for taking the Full backup
once in a month.
2. Add Transaction Log Backup for every day.
3. I transfer the Transaction log files on the main
server which are 16 MB or so and restore all the files.

Now my problem is everyday i get a new trn file with the
change in the date and i need to restore all the TRN with
the dates.

Like first the bakcup file
then trn of 16032005
then trn of 17032005
then trn of 18032005

I want to have a solution so that it will be
automatically done with the job.

Please suggest how i can achive the same.

Please also suggest if my approch is right.

Best regards
Sharad



*************************

Let's say you are doing daily log backups, and daily
database backups on the publishing server. I'd create a
log backup job on the primary server which'll backup the
log to a device (file) and overwrite it. This way, the
log file will be identical each time. Have another step
in the job copy over the backup file to the standby
server by using a network share. Once you can determine
how long the backup and transfer take, you can add on a
bit of contingency time and create a job on the standby
server to run at the appropriate time which'll pick up
the backup file. This will do a restore from the file
with the standby option to allow access. You must ensure
nobody is on the database at the time of the restore, so
an initial step might remove all users.
HTH,
Paul Ibison, SQL Server MVP, www.replicationanswers.com

Sharad,
you could have a backup device for each time of the day
that the transaction logs are created eg if you have
hourly transaction log backups, you have 24 devices.
Device1 holds the 1am tlog backup, Device2 holds the 2am
backup etc. Each backup is set to overwrite the previous
ones in the device. This way in effect, the filenames are
predictable. Alternatively, if you are only inteterested
in the latest one, you could make your life really simple
by having one transaction log and continually overwriting
it, which'll make the restore process a doddle.
HTH,
Paul Ibison, SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)