Christian,
Understood. How then do you perform full backups on your production
databses if log shipping is implementated?
Can you setup log shipping from 5:00 AM to 11:00 PM and then do your full
backups and any maintenace between 12:00 AM and 3:30 AM. Would the secondary
server be able to understand this logic? Thanks!!
"Christian Donner" wrote:
> "foghorn69@news.postalias" schrieb:
>
> > I was able to successfully create log shipping in our development environment
> > across a simulated WAN between two SQL Servers.
> >
> > I went to implement this in my production environment and all seemed to work
> > fine during the initial setup however, the monitor server says under Log
> > Shipping Pair Properties "backup not occuring" There are no errors in the
> > event log on the source server.
> >
> > I have a Win2003 SQL Cluster with SQL2000 Enterprise Edition logging to our
> > DR site. The remote server is not in a cluster just a stand alone Win2003
> > Server with SQL2000 Enterprise Edition. I setup a share on both servers
> > called "LogShipping" each with the appropriate permissions.
> >
> > On the LogShipping Maintenance Plan I have the TRN backups occurs every 15
> > minutes and I have verified this is happening. I have this scheduled between
> > 6:00 AM and 10:00 PM every day. These files are being dropped into the
> > "LogShipping" share folder on the source server. I can see where the inital
> > backup was copied to the destination server with the
> > "database_logshipping_init.bak" file in the LogShipping share on the
> > destination server.
> >
> > On another maintenance plan (Source Server only) I am backing up the
> > database every 4 hours but it is not part of the LogShipping Maintenance
> > Plan.
> >
> > What would cause the log shipping to just stop? The intial database was
> > copied but nothing else has occured??
>
> Logshipping bases on incremental backups. The regular backup every four
> hours sets a new starting point for the TA-Log which will not be understood
> by the standby server - it will need to be reinitialized with the new full
> database backup ...
> (That's the major drawback with logshipping!) >> Stay informed about: Log Shipping