How to configure Logshipping across the two forests

Hi,
I have configured Log shipping in my organisation which has two forests. One
forest has primary server and monitor server while the other forest has
secondary server. While configuring the Log shipping, read only database was
created successfully on the secondary server. Primary server is taking
transaction log backup on the specified time interval but it is not being
restored on the secondary server. What is the problem? How can I proceed?
Please guide me.
With regards,
Rajendra
You mentioned the secondary server is set to read only. Are there users in
there while you're trying to restore logs? If so, then the database is
already in a fully recovered state. From books online:
"It is not possible to apply a transaction log backup:
Unless the database or differential database backup preceding the
transaction log backup is restored first.
Unless all preceding transaction logs created since the database or
differential database were backed up are applied first.
If the database has already recovered and all outstanding transactions
have either been rolled back or rolled forward."
If you're trying to create a secondary reporting database, you might want to
try using replication instead. Depending on how you set it up, the secondary
data set can be kept more "up to date", and users can get in and out. Of
course, the database can't be read only, as replication will be writing to
it, but you can set all the users in the db_DataReader database role.
"Rajendra" wrote:

> Hi,
> I have configured Log shipping in my organisation which has two forests. One
> forest has primary server and monitor server while the other forest has
> secondary server. While configuring the Log shipping, read only database was
> created successfully on the secondary server. Primary server is taking
> transaction log backup on the specified time interval but it is not being
> restored on the secondary server. What is the problem? How can I proceed?
> Please guide me.
> With regards,
> Rajendra
|||Users Can be in the database on a secondary server if the
database has been restored using STANDBY which is an
option in the maintenance plan wizard. This is why there
is also the option to remove the users before a log
restore.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi friends,
Thanx for the reply. But I was asking whether it is possible to configure
Log shipping across the forests or not?I think share name acorss the forests
is creating some problem because I am not able connect SQL server with server
name if forests is other than the forest where my computer resides. That's
why I am connecting SQL server using IP address.
With regards
"Rajendra" wrote:

> Hi,
> I have configured Log shipping in my organisation which has two forests. One
> forest has primary server and monitor server while the other forest has
> secondary server. While configuring the Log shipping, read only database was
> created successfully on the secondary server. Primary server is taking
> transaction log backup on the specified time interval but it is not being
> restored on the secondary server. What is the problem? How can I proceed?
> Please guide me.
> With regards,
> Rajendra
|||Rajendra,
do you have a forest trust? If so, this should be possible. Can you see the
share at all? If not, perhaps you need to edit the hosts file for it to be
accessible.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

How to configure Log shipping on SQL server 2000 developer edition

Rajendra,
you should be able to use the log shipping wizard to set
things up. If you do need to script it out, then you
could use profiler while the wizard runs, but the main
part will be in the maintenance plan, which is not
scriptable in the usual meaning of the word.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul,
Thanx for ur reply but I don't have Enterprise edition. We purchased the
developer edition because Log shipping feature was listed in the available
features of SQL server 2000. If it is not available in developer edition then
Why Microsoft claimed to have this feature in developer edition?
"Paul Ibison" wrote:

> Rajendra,
> you should be able to use the log shipping wizard to set
> things up. If you do need to script it out, then you
> could use profiler while the wizard runs, but the main
> part will be in the maintenance plan, which is not
> scriptable in the usual meaning of the word.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Rajendra,
this facility should be there as developer is essentially
the same functionalitywise as enterprise edition and I
have just checked on a box at work. If you start the
maintenance plan wizard, and the log-shipping checkbox is
disabled for a particular database, this is because the
database is in simple recovery mode - perhaps this is the
case? Also, can you do select @.@.version just to confirm
that you have the developer edition installed.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||It is not installed in the developer edition, only the EE one.
I suggest Rajendra check out this link for info on how to set it up without
using EE.
http://www.sql-server-performance.co...g_shipping.asp
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:01fa01c4ba7e$668d7a10$a401280a@.phx.gbl...
> Rajendra,
> this facility should be there as developer is essentially
> the same functionalitywise as enterprise edition and I
> have just checked on a box at work. If you start the
> maintenance plan wizard, and the log-shipping checkbox is
> disabled for a particular database, this is because the
> database is in simple recovery mode - perhaps this is the
> case? Also, can you do select @.@.version just to confirm
> that you have the developer edition installed.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||AFAIK it is installed with Enterprise, Developer and
Enterprise Evaluation Editions - I can see the options on
my desktop, which only has Developer Edition.
Rgds,
Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I'm sorry, I just realized that this laptop has standard edition SQL Server.
I'll take your word for it Paul! Thanks for the clarification.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:0c2d01c4ba9a$9095e8d0$a601280a@.phx.gbl...
> AFAIK it is installed with Enterprise, Developer and
> Enterprise Evaluation Editions - I can see the options on
> my desktop, which only has Developer Edition.
> Rgds,
> Paul Ibison, SQL Server MVP, WWW.Replicationanswers.Com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

how to clear up log file in primary database in log shipping ?

our database system is runninig in log shipping mode.
currently, primary database log file get much more bigger,
but I dare not shrink log file in primary database ,
because do this will affect log shipping.
any way reslove this?
regards!Backup Log has Active and Inactive Portions. To Truncate Inactive
portion user the following command in SQL Query Analyser
USE The following Command
BACKUP LOG { database_name | @.database_name_var }
WITH TRUNCATE_ONLY|||That would break the log shipping!
AFAIK, shrinking of log file should be OK in a log shipping scenario...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rex" <r.ghodasara@.gmail.com> wrote in message
news:1143808657.133001.205870@.u72g2000cwu.googlegroups.com...
> Backup Log has Active and Inactive Portions. To Truncate Inactive
> portion user the following command in SQL Query Analyser
> USE The following Command
> BACKUP LOG { database_name | @.database_name_var }
> WITH TRUNCATE_ONLY
>|||thanks ,
but according to your point
as time goes, the logfile will get bigger and bigger,
shrinking logfile is not the best way?
do you think so ?
I meant how to clear up logfile and don't affect log shipping?|||The log file is emptied each time you do backup of the transaction log. So, it will grow until it
has the size needed to accommodate the modifications you do between two log backups, so just let it
be the size it need to be. If you see it grow beyond that, you can perhaps have had a long running
transaction in the log preventing the file to be emptied to a high degree. See
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for more information.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<lovexueer@.gmail.com> wrote in message news:1143814572.962154.266770@.g10g2000cwb.googlegroups.com...
> thanks ,
> but according to your point
> as time goes, the logfile will get bigger and bigger,
> shrinking logfile is not the best way?
> do you think so ?
> I meant how to clear up logfile and don't affect log shipping?
>

how to clear up log file in primary database in log shipping ?

our database system is runninig in log shipping mode.
currently, primary database log file get much more bigger,
but I dare not shrink log file in primary database ,
because do this will affect log shipping.
any way reslove this?
regards!
Backup Log has Active and Inactive Portions. To Truncate Inactive
portion user the following command in SQL Query Analyser
USE The following Command
BACKUP LOG { database_name | @.database_name_var }
WITH TRUNCATE_ONLY
|||That would break the log shipping!
AFAIK, shrinking of log file should be OK in a log shipping scenario...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rex" <r.ghodasara@.gmail.com> wrote in message
news:1143808657.133001.205870@.u72g2000cwu.googlegr oups.com...
> Backup Log has Active and Inactive Portions. To Truncate Inactive
> portion user the following command in SQL Query Analyser
> USE The following Command
> BACKUP LOG { database_name | @.database_name_var }
> WITH TRUNCATE_ONLY
>
|||thanks ,
but according to your point
as time goes, the logfile will get bigger and bigger,
shrinking logfile is not the best way?
do you think so ?
I meant how to clear up logfile and don't affect log shipping?
|||The log file is emptied each time you do backup of the transaction log. So, it will grow until it
has the size needed to accommodate the modifications you do between two log backups, so just let it
be the size it need to be. If you see it grow beyond that, you can perhaps have had a long running
transaction in the log preventing the file to be emptied to a high degree. See
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for more information.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<lovexueer@.gmail.com> wrote in message news:1143814572.962154.266770@.g10g2000cwb.googlegr oups.com...
> thanks ,
> but according to your point
> as time goes, the logfile will get bigger and bigger,
> shrinking logfile is not the best way?
> do you think so ?
> I meant how to clear up logfile and don't affect log shipping?
>

how to clear up log file in primary database in log shipping ?

our database system is runninig in log shipping mode.
currently, primary database log file get much more bigger,
but I dare not shrink log file in primary database ,
because do this will affect log shipping.
any way reslove this?
regards!Backup Log has Active and Inactive Portions. To Truncate Inactive
portion user the following command in SQL Query Analyser
USE The following Command
BACKUP LOG { database_name | @.database_name_var }
WITH TRUNCATE_ONLY|||That would break the log shipping!
AFAIK, shrinking of log file should be OK in a log shipping scenario...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Rex" <r.ghodasara@.gmail.com> wrote in message
news:1143808657.133001.205870@.u72g2000cwu.googlegroups.com...
> Backup Log has Active and Inactive Portions. To Truncate Inactive
> portion user the following command in SQL Query Analyser
> USE The following Command
> BACKUP LOG { database_name | @.database_name_var }
> WITH TRUNCATE_ONLY
>|||thanks ,
but according to your point
as time goes, the logfile will get bigger and bigger,
shrinking logfile is not the best way?
do you think so ?
I meant how to clear up logfile and don't affect log shipping?|||The log file is emptied each time you do backup of the transaction log. So,
it will grow until it
has the size needed to accommodate the modifications you do between two log
backups, so just let it
be the size it need to be. If you see it grow beyond that, you can perhaps h
ave had a long running
transaction in the log preventing the file to be emptied to a high degree. S
ee
http://www.karaszi.com/SQLServer/info_dont_shrink.asp for more information.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<lovexueer@.gmail.com> wrote in message news:1143814572.962154.266770@.g10g2000cwb.googlegroup
s.com...
> thanks ,
> but according to your point
> as time goes, the logfile will get bigger and bigger,
> shrinking logfile is not the best way?
> do you think so ?
> I meant how to clear up logfile and don't affect log shipping?
>