Log shipping to another server with a different database name.

SQL Server 2000.
What are the steps for log shipping a database to another server ,b ut you
want to use a different database name on the secondary server?
Delton
start with
http://www.sql-server-performance.co...g_shipping.asp
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:uqvSzqD3GHA.4924@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2000.
> What are the steps for log shipping a database to another server ,b ut you
> want to use a different database name on the secondary server?
>
|||Delton Blackwell wrote:
> SQL Server 2000.
> What are the steps for log shipping a database to another server ,b ut you
> want to use a different database name on the secondary server?
>
If you're using your own scripted log-shipping solution, simply change
the RESTORE command that restores your backups. Change it to create a
database with a different name.
If you're using the log-shipping wizard gizmo, then I have no idea, I've
never used it.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log shipping to another server with a different database name.

SQL Server 2000.
What are the steps for log shipping a database to another server ,b ut you
want to use a different database name on the secondary server?Delton
start with
http://www.sql-server-performance.com/sql_server_log_shipping.asp
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:uqvSzqD3GHA.4924@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2000.
> What are the steps for log shipping a database to another server ,b ut you
> want to use a different database name on the secondary server?
>|||Delton Blackwell wrote:
> SQL Server 2000.
> What are the steps for log shipping a database to another server ,b ut you
> want to use a different database name on the secondary server?
>
If you're using your own scripted log-shipping solution, simply change
the RESTORE command that restores your backups. Change it to create a
database with a different name.
If you're using the log-shipping wizard gizmo, then I have no idea, I've
never used it.
Tracy McKibben
MCDBA
http://www.realsqlguy.comsql

Log shipping to another server with a different database name.

SQL Server 2000.
What are the steps for log shipping a database to another server ,b ut you
want to use a different database name on the secondary server?Delton
start with
http://www.sql-server-performance.c...og_shipping.asp
"Delton Blackwell" <deltonblackwell@.hotmail.com> wrote in message
news:uqvSzqD3GHA.4924@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2000.
> What are the steps for log shipping a database to another server ,b ut you
> want to use a different database name on the secondary server?
>|||Delton Blackwell wrote:
> SQL Server 2000.
> What are the steps for log shipping a database to another server ,b ut you
> want to use a different database name on the secondary server?
>
If you're using your own scripted log-shipping solution, simply change
the RESTORE command that restores your backups. Change it to create a
database with a different name.
If you're using the log-shipping wizard gizmo, then I have no idea, I've
never used it.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log Shipping Restore Failed - How do I find out why?

I set up log shipping for a database to fire every 10 mins. All the steps on
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServer
Even I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:

> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer
|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer

Log Shipping Restore Failed - How do I find out why?

I set up log shipping for a database to fire every 10 mins. All the steps o
n
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more
.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:

> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the lo
g
> bkp is created on the source server and is copied to the destination serve
r.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any mo
re.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer

Log Shipping Restore Failed - How do I find out why?

I set up log shipping for a database to fire every 10 mins. All the steps on
both servers work the first two times. On the 3rd 10 min interval, the log
bkp is created on the source server and is copied to the destination server.
However, the SQL Agent step, "Log Shipping Restore for
SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
appropriate destination server folder but the restore does not work any more.
Plus, the event interval on the SQL Agent jobs destination server were
showing every 10 mins but now are showing every 15 mins.
How can I determine what happened and how to fix it?
--
Picine Karppehd
A newbie to VB.Net,
pretty good with VB6,
Certified with SQLServerEven I was facing the similar issue. Whenever there was huge tlog backups,
restore job in the destination server used to fail. I increased the re-try
attempts by 1 after 1 minute for copy as well as restore job in the
destination server. And it seems to be running fine since.
To do the above, go to the restore job in your destination server,
properties, step, advanced, retry attempts...
HTH
GYK
"Picine Karppehd" wrote:
> I set up log shipping for a database to fire every 10 mins. All the steps on
> both servers work the first two times. On the 3rd 10 min interval, the log
> bkp is created on the source server and is copied to the destination server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer|||Picine,
Try restoring the copied log file yourself using Query Analyzer and if
there's an error, what the message is.
Ron
--
Ron Talmage
SQL Server MVP
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:2618C571-9B99-4365-94EC-B22927DF46B9@.microsoft.com...
> I set up log shipping for a database to fire every 10 mins. All the steps
on
> both servers work the first two times. On the 3rd 10 min interval, the
log
> bkp is created on the source server and is copied to the destination
server.
> However, the SQL Agent step, "Log Shipping Restore for
> SERVER.APPDB_logshipping" shows failure. The log bkp files are in the
> appropriate destination server folder but the restore does not work any
more.
> Plus, the event interval on the SQL Agent jobs destination server were
> showing every 10 mins but now are showing every 15 mins.
> How can I determine what happened and how to fix it?
> --
> Picine Karppehd
> A newbie to VB.Net,
> pretty good with VB6,
> Certified with SQLServer

Log shipping issue

Hi,
I have tried to set up Log shipping on SQL Server 2000. After I had
successfully finished all the steps the log shipping ran well for about 45
minutes when it got out of sync.
I have deleted all the metadata about logshipping from primary,
secondary and from the monitoring server. (I had to do it from Query Analyzer
as from EM it wasn`t possible - i suppose something was stucked).
Now all the info about the old log shipping plan is gone. The problem
that I have is that when I try to set up a new log shipping plan, when I
chose the database for which I want to ship logs -> the log shipping checkbox
grayes out. If i select first the log shipping checkbox and then the
database, the checkbox also grays out but checked and I`m able to go further
and to set the rest of the options -> at the step at which I am suppose to
chose the secondary server, although it appears in the list, when I select it
nothing happens (the selection remains like there is no server selected)
The primary server uses Full Recovery model
I have manually restored all the backups from the primary to the
secondary to bring the secondary db uptodate.
Any ideas?
Thank you
--
Razvan Dragomir,
MCSA / MCSE / MCDB / MCITPI managed to solve the thing with log shipping check box being grayed out -
there was still some info in the log_shipping_databases.
But I still have the problem with the secondary server - i`m not able to
select it in the log shipping wizard. I have also create another test
database and it`s the same. .. looks like I can`t ship on that secondary
server.
All servers are Enterprise edition, having for services same users and
passwords (domain user)
Any ideas?
Thank you
--
Razvan Dragomir,
MCSA / MCSE / MCDB / MCITP
"Razvan Dragomir" wrote:
> Hi,
> I have tried to set up Log shipping on SQL Server 2000. After I had
> successfully finished all the steps the log shipping ran well for about 45
> minutes when it got out of sync.
> I have deleted all the metadata about logshipping from primary,
> secondary and from the monitoring server. (I had to do it from Query Analyzer
> as from EM it wasn`t possible - i suppose something was stucked).
> Now all the info about the old log shipping plan is gone. The problem
> that I have is that when I try to set up a new log shipping plan, when I
> chose the database for which I want to ship logs -> the log shipping checkbox
> grayes out. If i select first the log shipping checkbox and then the
> database, the checkbox also grays out but checked and I`m able to go further
> and to set the rest of the options -> at the step at which I am suppose to
> chose the secondary server, although it appears in the list, when I select it
> nothing happens (the selection remains like there is no server selected)
> The primary server uses Full Recovery model
> I have manually restored all the backups from the primary to the
> secondary to bring the secondary db uptodate.
> Any ideas?
> Thank you
> --
> Razvan Dragomir,
> MCSA / MCSE / MCDB / MCITP
>

Log shipping issue

Hi,
I have tried to set up Log shipping on SQL Server 2000. After I had
successfully finished all the steps the log shipping ran well for about 45
minutes when it got out of sync.
I have deleted all the metadata about logshipping from primary,
secondary and from the monitoring server. (I had to do it from Query Analyzer
as from EM it wasn`t possible - i suppose something was stucked).
Now all the info about the old log shipping plan is gone. The problem
that I have is that when I try to set up a new log shipping plan, when I
chose the database for which I want to ship logs -> the log shipping checkbox
grayes out. If i select first the log shipping checkbox and then the
database, the checkbox also grays out but checked and I`m able to go further
and to set the rest of the options -> at the step at which I am suppose to
chose the secondary server, although it appears in the list, when I select it
nothing happens (the selection remains like there is no server selected)
The primary server uses Full Recovery model
I have manually restored all the backups from the primary to the
secondary to bring the secondary db uptodate.
Any ideas?
Thank you
Razvan Dragomir,
MCSA / MCSE / MCDB / MCITP
I managed to solve the thing with log shipping check box being grayed out -
there was still some info in the log_shipping_databases.
But I still have the problem with the secondary server - i`m not able to
select it in the log shipping wizard. I have also create another test
database and it`s the same. .. looks like I can`t ship on that secondary
server.
All servers are Enterprise edition, having for services same users and
passwords (domain user)
Any ideas?
Thank you
Razvan Dragomir,
MCSA / MCSE / MCDB / MCITP
"Razvan Dragomir" wrote:

> Hi,
> I have tried to set up Log shipping on SQL Server 2000. After I had
> successfully finished all the steps the log shipping ran well for about 45
> minutes when it got out of sync.
> I have deleted all the metadata about logshipping from primary,
> secondary and from the monitoring server. (I had to do it from Query Analyzer
> as from EM it wasn`t possible - i suppose something was stucked).
> Now all the info about the old log shipping plan is gone. The problem
> that I have is that when I try to set up a new log shipping plan, when I
> chose the database for which I want to ship logs -> the log shipping checkbox
> grayes out. If i select first the log shipping checkbox and then the
> database, the checkbox also grays out but checked and I`m able to go further
> and to set the rest of the options -> at the step at which I am suppose to
> chose the secondary server, although it appears in the list, when I select it
> nothing happens (the selection remains like there is no server selected)
> The primary server uses Full Recovery model
> I have manually restored all the backups from the primary to the
> secondary to bring the secondary db uptodate.
> Any ideas?
> Thank you
> --
> Razvan Dragomir,
> MCSA / MCSE / MCDB / MCITP
>

Log shipping issue

Hi,
I have tried to set up Log shipping on SQL Server 2000. After I had
successfully finished all the steps the log shipping ran well for about 45
minutes when it got out of sync.
I have deleted all the metadata about logshipping from primary,
secondary and from the monitoring server. (I had to do it from Query Analyze
r
as from EM it wasn`t possible - i suppose something was stucked).
Now all the info about the old log shipping plan is gone. The problem
that I have is that when I try to set up a new log shipping plan, when I
chose the database for which I want to ship logs -> the log shipping checkbo
x
grayes out. If i select first the log shipping checkbox and then the
database, the checkbox also grays out but checked and I`m able to go further
and to set the rest of the options -> at the step at which I am suppose to
chose the secondary server, although it appears in the list, when I select i
t
nothing happens (the selection remains like there is no server selected)
The primary server uses Full Recovery model
I have manually restored all the backups from the primary to the
secondary to bring the secondary db uptodate.
Any ideas?
Thank you
--
Razvan Dragomir,
MCSA / MCSE / MCDB / MCITPI managed to solve the thing with log shipping check box being grayed out -
there was still some info in the log_shipping_databases.
But I still have the problem with the secondary server - i`m not able to
select it in the log shipping wizard. I have also create another test
database and it`s the same. .. looks like I can`t ship on that secondary
server.
All servers are Enterprise edition, having for services same users and
passwords (domain user)
Any ideas?
Thank you
Razvan Dragomir,
MCSA / MCSE / MCDB / MCITP
"Razvan Dragomir" wrote:

> Hi,
> I have tried to set up Log shipping on SQL Server 2000. After I had
> successfully finished all the steps the log shipping ran well for about 45
> minutes when it got out of sync.
> I have deleted all the metadata about logshipping from primary,
> secondary and from the monitoring server. (I had to do it from Query Analy
zer
> as from EM it wasn`t possible - i suppose something was stucked).
> Now all the info about the old log shipping plan is gone. The problem
> that I have is that when I try to set up a new log shipping plan, when I
> chose the database for which I want to ship logs -> the log shipping check
box
> grayes out. If i select first the log shipping checkbox and then the
> database, the checkbox also grays out but checked and I`m able to go furth
er
> and to set the rest of the options -> at the step at which I am suppose to
> chose the secondary server, although it appears in the list, when I select
it
> nothing happens (the selection remains like there is no server selected)
> The primary server uses Full Recovery model
> I have manually restored all the backups from the primary to the
> secondary to bring the secondary db uptodate.
> Any ideas?
> Thank you
> --
> Razvan Dragomir,
> MCSA / MCSE / MCDB / MCITP
>