Hi Guys,
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
Biju,
although the graphical interface doesn't implement the option to backup to a different computer (in terms of browsing), you can use a network share by typing it in. I haven't done this in anger before but I guess the usual constraints of bandwidth, networ
k useage etc would obviously apply.
Regards,
Paul Ibison
Showing posts with label planning. Show all posts
Showing posts with label planning. Show all posts
Friday, March 23, 2012
logshipping question
Hi Guys,
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
1. Don't try to do log shipping at an interval less than 2 minutes. It can
be done, but you are going to have an extremely difficult time handling all
of the error messages that will pop up due to latency and congestion.
2. You can use a network share if you choose to. The only impact is that
there will be a slightly longer delay as your backups transit across your
network card instead of to the local disk. The negative impact is that your
backups are streaming down your network card which impacts network
throughput. But, that impact is similar to what happens if you back up to
local disk and then copy the backup over, so that consideration is
essentially a wash.
3. Watch you full backups carefully. They will block the transaction log
backups which can cause all of your alarms to go off.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||A one minute transaction log backup is VERY ambitious. Most people go for between 5 and 15 minutes. If you test lab this with production-like equipment you will understand why 1-min intervals is so difficult to achieve on SQL2K.
If the network connection is broken, the transaction log copy job will retry the copy the next time it is scheduled to run. No data will be lost. It will keep retrying until the logs are successfully copied or the out-of-synch time is reached.
With an interval of 1-min performance could be a real concern.
i am planning to implement logshipping in sql 2000 which
is already a pulisher for transactional replication.
i am planning to take transaction log backup in the
interval of 1(one) minute.
if network connection broken will it affect restoring at
desination server?
can i make the share for transaction log backup folder on
network instead of production server?
overall will it have any negative impacton source server.
Pls advice
Thanks
Biju
1. Don't try to do log shipping at an interval less than 2 minutes. It can
be done, but you are going to have an extremely difficult time handling all
of the error messages that will pop up due to latency and congestion.
2. You can use a network share if you choose to. The only impact is that
there will be a slightly longer delay as your backups transit across your
network card instead of to the local disk. The negative impact is that your
backups are streaming down your network card which impacts network
throughput. But, that impact is similar to what happens if you back up to
local disk and then copy the backup over, so that consideration is
essentially a wash.
3. Watch you full backups carefully. They will block the transaction log
backups which can cause all of your alarms to go off.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||A one minute transaction log backup is VERY ambitious. Most people go for between 5 and 15 minutes. If you test lab this with production-like equipment you will understand why 1-min intervals is so difficult to achieve on SQL2K.
If the network connection is broken, the transaction log copy job will retry the copy the next time it is scheduled to run. No data will be lost. It will keep retrying until the logs are successfully copied or the out-of-synch time is reached.
With an interval of 1-min performance could be a real concern.
Monday, March 12, 2012
Logins with Log shipping
We are planning on using our secondary database as a reporting server with
log shipping. The problem is that log shipping puts the db in read only mode
and occasionally we need to add user permissions to the secondary only. The
only option I see is everytime permissions are needed we would have to take
the database out of read only mode, grant the permissions and then put the db
back to read only. Does anyone have any other ideas that might work? Thanks!
this won't work - by making the change you will break the log shipping
chain.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Anita" <Anita@.discussions.microsoft.com> wrote in message
news:6C1A0C65-2281-45A8-9A9C-5762DA7D9E6D@.microsoft.com...
> We are planning on using our secondary database as a reporting server with
> log shipping. The problem is that log shipping puts the db in read only
mode
> and occasionally we need to add user permissions to the secondary only.
The
> only option I see is everytime permissions are needed we would have to
take
> the database out of read only mode, grant the permissions and then put the
db
> back to read only. Does anyone have any other ideas that might work?
Thanks!
|||Anita,
you could add a separate role to the primary server and assign all the
necessary permissions there. Also, add a login to this role. As long as you
have the same login on the secondary server (same SID) the permissions will
be applicable there.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
log shipping. The problem is that log shipping puts the db in read only mode
and occasionally we need to add user permissions to the secondary only. The
only option I see is everytime permissions are needed we would have to take
the database out of read only mode, grant the permissions and then put the db
back to read only. Does anyone have any other ideas that might work? Thanks!
this won't work - by making the change you will break the log shipping
chain.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Anita" <Anita@.discussions.microsoft.com> wrote in message
news:6C1A0C65-2281-45A8-9A9C-5762DA7D9E6D@.microsoft.com...
> We are planning on using our secondary database as a reporting server with
> log shipping. The problem is that log shipping puts the db in read only
mode
> and occasionally we need to add user permissions to the secondary only.
The
> only option I see is everytime permissions are needed we would have to
take
> the database out of read only mode, grant the permissions and then put the
db
> back to read only. Does anyone have any other ideas that might work?
Thanks!
|||Anita,
you could add a separate role to the primary server and assign all the
necessary permissions there. Also, add a login to this role. As long as you
have the same login on the secondary server (same SID) the permissions will
be applicable there.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Subscribe to:
Posts (Atom)