Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Log Shipping

 
   Database Forums (Home) -> Replication RSS
Next:  multiple select but ......php/mysql/html  
Author Message
foghorn69newspostalias

External


Since: Jul 19, 2005
Posts: 7



(Msg. 1) Posted: Sun Aug 07, 2005 5:20 am
Post subject: Log Shipping
Archived from groups: microsoft>public>sqlserver>replication (more info?)

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??

 >> Stay informed about: Log Shipping 
Back to top
Login to vote
Christian Donner

External


Since: May 24, 2005
Posts: 16



(Msg. 2) Posted: Sun Aug 07, 2005 7:02 am
Post subject: RE: Log Shipping [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"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 
Back to top
Login to vote
foghorn69newspostalias

External


Since: Jul 19, 2005
Posts: 7



(Msg. 3) Posted: Sun Aug 07, 2005 10:39 am
Post subject: RE: Log Shipping [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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 
Back to top
Login to vote
Christian Donner

External


Since: May 24, 2005
Posts: 16



(Msg. 4) Posted: Sun Aug 07, 2005 12:19 pm
Post subject: RE: Log Shipping [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"foghorn69@news.postalias" schrieb:

> 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!!

I never found a method to backup my databases with active logshipping - the
standby server seems to be the only backup you get! I gave up logshipping
because of that and use a rather complex transactional replication based
scenario instead ...
 >> Stay informed about: Log Shipping 
Back to top
Login to vote
foghorn69newspostalias

External


Since: Jul 19, 2005
Posts: 7



(Msg. 5) Posted: Sun Aug 07, 2005 1:07 pm
Post subject: RE: Log Shipping [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Is it possible then to log ship the same database from the source server to
two different destinations servers? I would assume you just create two
maintenance plans?

What happens if you run a full backup on the destination server. Is the log
shipping chain broken?

"Christian Donner" wrote:

> "foghorn69@news.postalias" schrieb:
>
> > 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!!
>
> I never found a method to backup my databases with active logshipping - the
> standby server seems to be the only backup you get! I gave up logshipping
> because of that and use a rather complex transactional replication based
> scenario instead ...
 >> Stay informed about: Log Shipping 
Back to top
Login to vote
Christian Donner

External


Since: May 24, 2005
Posts: 16



(Msg. 6) Posted: Mon Aug 08, 2005 11:02 am
Post subject: RE: Log Shipping [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"foghorn69@news.postalias" schrieb:

> Is it possible then to log ship the same database from the source server to
> two different destinations servers? I would assume you just create two
> maintenance plans?
>
> What happens if you run a full backup on the destination server. Is the log
> shipping chain broken?

1. No, each Logshipping produces its own backup and interrupts the sequence
of the other one.
2. No, databases in warm stand by can generally not be backuped ...
 >> Stay informed about: Log Shipping 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
SQL 2005 Log Shipping - I am wanting to implement log shipping on a new install of sql2005 standard. I searched the site but couldn't really find my answer. Is log shipping "built-in" to SQL 2005 Standard? Scott

Log Shipping between 2000 and 2005 - Hi - We have a SQL 2000 Standard production database and a 2005 Standard backup/reporting database. What would the steps be to make the 2000 database the Primary database in a Log Shipping configuration and the 2005 the Secondary database? Thanks

Log Shipping & Backups - I have a Win2K3 SQL Cluster that is currently log shipping to my DR SQL Server and a DEV SQL Server. Everything is working perfectly. For piece of mind, I would still like to do a backup of the production server everynight but that is not possible..

Log Shipping issue - Hi All, I am a new learner of SQL2000. Recently I learned to setup log shipping. I have Primary Server (A) and 1st Secondary Server (B) at my head office. I also have 2nd Secondary (C) at a remote site. Server A log ship logs to server B and C. Server ...

Replication or Log shipping - If i want to my test server database should be in sync with my prod database, which one is the best. after complete data sync i dont want any data updates. i am going to setting up only one way, from prod to test. please advise if any risks or issues
   Database Forums (Home) -> Replication All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]