I am setting up log shipping according to the "How to Setup Log Shipping" Microsoft White Paper. I want to use log shipping for multiple databases on the same machine and I guess I need to configure each DB separately. My question is do I/should I use s
eparate transaction log backup shares on the primary and secondary machines corresponding to each database. Just wondering if there is a chance for a collison with the log file names between to different DBs? Thanks.
Jeff
Jeff,
I have used both scenarios: separate directories and the same directory for all files. The filenames are prefixed with the database name and the maintenance plan takes it into account, so there's no problem. However, I find maintenance easier (clearer) wi
th several directories.
HTH,
Paul Ibison
Showing posts with label multiple. Show all posts
Showing posts with label multiple. Show all posts
Friday, March 23, 2012
Wednesday, March 21, 2012
log shipping out of sync
I have set up a database with log shipping to the backup server. I have actually set it up multiple times because it continues to get out of sync, and I do not know another way to get it back in sync (despite much effort to learn how). I have not found much documentation in BOL, nor in the on-line areas that I can find. I have not been able to discover why it keeps getting out of sync.
If there is anyone who may shed some light on this, I would be very greatful.
Particulars (both servers):
Windows ADV Server 2003
SQL 2000 (Enterprise Ed.)
Servers on a work group (not domain)
There is a separate database on the same servers that continues to have successful log shipping.
Thank you very much (in advance).
If there is anyone who may shed some light on this, I would be very greatful.
Particulars (both servers):
Windows ADV Server 2003
SQL 2000 (Enterprise Ed.)
Servers on a work group (not domain)
There is a separate database on the same servers that continues to have successful log shipping.
Thank you very much (in advance).
you can try to manually restore the logs that was not applied to the secondary database, or, restore the latest full backup, and then re-sume logshipping to get your logshipping work again.
Is there anything particular on this configuration? you mentioned that Logshipping with other databases worked successfully on the same server so I assume your configuration of both LS are correct.
Thanks
Yunwen
Log Shipping Multi Instances
Can you cross log ship across multiple instances using both servers?If I understand you correctly, then yes (Enterprise
edition only)
>--Original Message--
>Can you cross log ship across multiple instances using
both servers?
>.
>|||Cindy, what do you mean by "cross log ship"? Do you mean setting up a log
shipping pair where the primary & secondary servers are two distinct named
SQL instances on a single physical server? If so, then yes (as Jono said)
but why would you want to (I can't think of any good reasons)?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:884201c4d126$ef9e06d0$a601280a@.phx.gbl...
> If I understand you correctly, then yes (Enterprise
> edition only)
>>--Original Message--
>>Can you cross log ship across multiple instances using
> both servers?
>>.
edition only)
>--Original Message--
>Can you cross log ship across multiple instances using
both servers?
>.
>|||Cindy, what do you mean by "cross log ship"? Do you mean setting up a log
shipping pair where the primary & secondary servers are two distinct named
SQL instances on a single physical server? If so, then yes (as Jono said)
but why would you want to (I can't think of any good reasons)?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:884201c4d126$ef9e06d0$a601280a@.phx.gbl...
> If I understand you correctly, then yes (Enterprise
> edition only)
>>--Original Message--
>>Can you cross log ship across multiple instances using
> both servers?
>>.
Log Shipping Multi Instances
If I understand you correctly, then yes (Enterprise
edition only)
>--Original Message--
>Can you cross log ship across multiple instances using
both servers?
>.
>
Cindy, what do you mean by "cross log ship"? Do you mean setting up a log
shipping pair where the primary & secondary servers are two distinct named
SQL instances on a single physical server? If so, then yes (as Jono said)
but why would you want to (I can't think of any good reasons)?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:884201c4d126$ef9e06d0$a601280a@.phx.gbl...[vbcol=seagreen]
> If I understand you correctly, then yes (Enterprise
> edition only)
> both servers?
sql
edition only)
>--Original Message--
>Can you cross log ship across multiple instances using
both servers?
>.
>
Cindy, what do you mean by "cross log ship"? Do you mean setting up a log
shipping pair where the primary & secondary servers are two distinct named
SQL instances on a single physical server? If so, then yes (as Jono said)
but why would you want to (I can't think of any good reasons)?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:884201c4d126$ef9e06d0$a601280a@.phx.gbl...[vbcol=seagreen]
> If I understand you correctly, then yes (Enterprise
> edition only)
> both servers?
sql
Log Shipping Multi Instances
If I understand you correctly, then yes (Enterprise
edition only)
>--Original Message--
>Can you cross log ship across multiple instances using
both servers?
>.
>Cindy, what do you mean by "cross log ship"? Do you mean setting up a log
shipping pair where the primary & secondary servers are two distinct named
SQL instances on a single physical server? If so, then yes (as Jono said)
but why would you want to (I can't think of any good reasons)?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:884201c4d126$ef9e06d0$a601280a@.phx.gbl...[vbcol=seagreen]
> If I understand you correctly, then yes (Enterprise
> edition only)
>
> both servers?
edition only)
>--Original Message--
>Can you cross log ship across multiple instances using
both servers?
>.
>Cindy, what do you mean by "cross log ship"? Do you mean setting up a log
shipping pair where the primary & secondary servers are two distinct named
SQL instances on a single physical server? If so, then yes (as Jono said)
but why would you want to (I can't think of any good reasons)?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:884201c4d126$ef9e06d0$a601280a@.phx.gbl...[vbcol=seagreen]
> If I understand you correctly, then yes (Enterprise
> edition only)
>
> both servers?
Monday, March 19, 2012
Log Shipping in multiple databases
I am trying to configure Log_Shipping in multiple databases on different
servers.
I tried to add it but it has to use the same destination copy folder, is
that true ?
i am using SQL2005.I haven't used the 2005 log shipping. Log shipping in general works under
the following model. There are two virtual jobs that run consecutively; the
first virtual job would be to create a log for a given time frame on the
source server and write it to the local disk and subsequently send a copy of
that log file to the destination server. The second virtual job is to read
the log file sent from the source server and when it reads the log file, it
can either delete it or more commonly, the file is saved for a given time to
another folder that consists of logs that have been read.
Example:
Write log to \\mysourceserver\backup\mylog_date_time.log
Copy mylog_date_time.log from \\mysourceserver\backup to
\\mysdestserver\backup
Read log \\mysourceserver\backup\mylog_date_time.log
Store log by moving \\mysourceserver\backup\mylog_date_time.log to
\\mysourceserver\storage\mylog_date_time.log
Finally there may be a purge time set to delete logs older than a set time.
--
Regards,
Jamie
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>|||Thanks Jamie for help,
I am already running Log Shipping from one server to another one, but i am
going to buy a new server with a highly configuration and want this new one
to be the main database and the old one be another log shipping database ( 1
main db and 2 log shipping db).
I tried it on a test server but any adding new server, has to change the
copy folder into the old server by force.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:786DB259-3386-4E4E-9A0A-FFE03BC5557B@.microsoft.com...
>I haven't used the 2005 log shipping. Log shipping in general works under
> the following model. There are two virtual jobs that run consecutively;
> the
> first virtual job would be to create a log for a given time frame on the
> source server and write it to the local disk and subsequently send a copy
> of
> that log file to the destination server. The second virtual job is to
> read
> the log file sent from the source server and when it reads the log file,
> it
> can either delete it or more commonly, the file is saved for a given time
> to
> another folder that consists of logs that have been read.
> Example:
> Write log to \\mysourceserver\backup\mylog_date_time.log
> Copy mylog_date_time.log from \\mysourceserver\backup to
> \\mysdestserver\backup
> Read log \\mysourceserver\backup\mylog_date_time.log
> Store log by moving \\mysourceserver\backup\mylog_date_time.log to
> \\mysourceserver\storage\mylog_date_time.log
> Finally there may be a purge time set to delete logs older than a set
> time.
> --
> Regards,
> Jamie
>
> "Mahmoud Amin" wrote:
>> I am trying to configure Log_Shipping in multiple databases on different
>> servers.
>> I tried to add it but it has to use the same destination copy folder, is
>> that true ?
>> i am using SQL2005.
>>|||Hi Amin,
You have 1 server which has primary db and you configure it
for log shipping to 2 different secondary servers....i guess this is what
you want....
but i think you are trying to configure log shipping from 1 st primary to 1
st secondary
and from the 1st primary to the same secondary server...so you'll have 2
copies of your log shipped db in your secoindary server......but that will
not server the purpose of log shipping as in case the seconday server is down
you won't have backup of primary server.......
but you can configure like that but you'll have only 1 shared folder which
conains both the logs from primary server
refer the below link for configuring log shipping just a sample
http://deepakinsql.blogspot.com/2007/06/how-to-configure-log-shipping-in-sql.html
Thanxx
Deepak
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>
servers.
I tried to add it but it has to use the same destination copy folder, is
that true ?
i am using SQL2005.I haven't used the 2005 log shipping. Log shipping in general works under
the following model. There are two virtual jobs that run consecutively; the
first virtual job would be to create a log for a given time frame on the
source server and write it to the local disk and subsequently send a copy of
that log file to the destination server. The second virtual job is to read
the log file sent from the source server and when it reads the log file, it
can either delete it or more commonly, the file is saved for a given time to
another folder that consists of logs that have been read.
Example:
Write log to \\mysourceserver\backup\mylog_date_time.log
Copy mylog_date_time.log from \\mysourceserver\backup to
\\mysdestserver\backup
Read log \\mysourceserver\backup\mylog_date_time.log
Store log by moving \\mysourceserver\backup\mylog_date_time.log to
\\mysourceserver\storage\mylog_date_time.log
Finally there may be a purge time set to delete logs older than a set time.
--
Regards,
Jamie
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>|||Thanks Jamie for help,
I am already running Log Shipping from one server to another one, but i am
going to buy a new server with a highly configuration and want this new one
to be the main database and the old one be another log shipping database ( 1
main db and 2 log shipping db).
I tried it on a test server but any adding new server, has to change the
copy folder into the old server by force.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:786DB259-3386-4E4E-9A0A-FFE03BC5557B@.microsoft.com...
>I haven't used the 2005 log shipping. Log shipping in general works under
> the following model. There are two virtual jobs that run consecutively;
> the
> first virtual job would be to create a log for a given time frame on the
> source server and write it to the local disk and subsequently send a copy
> of
> that log file to the destination server. The second virtual job is to
> read
> the log file sent from the source server and when it reads the log file,
> it
> can either delete it or more commonly, the file is saved for a given time
> to
> another folder that consists of logs that have been read.
> Example:
> Write log to \\mysourceserver\backup\mylog_date_time.log
> Copy mylog_date_time.log from \\mysourceserver\backup to
> \\mysdestserver\backup
> Read log \\mysourceserver\backup\mylog_date_time.log
> Store log by moving \\mysourceserver\backup\mylog_date_time.log to
> \\mysourceserver\storage\mylog_date_time.log
> Finally there may be a purge time set to delete logs older than a set
> time.
> --
> Regards,
> Jamie
>
> "Mahmoud Amin" wrote:
>> I am trying to configure Log_Shipping in multiple databases on different
>> servers.
>> I tried to add it but it has to use the same destination copy folder, is
>> that true ?
>> i am using SQL2005.
>>|||Hi Amin,
You have 1 server which has primary db and you configure it
for log shipping to 2 different secondary servers....i guess this is what
you want....
but i think you are trying to configure log shipping from 1 st primary to 1
st secondary
and from the 1st primary to the same secondary server...so you'll have 2
copies of your log shipped db in your secoindary server......but that will
not server the purpose of log shipping as in case the seconday server is down
you won't have backup of primary server.......
but you can configure like that but you'll have only 1 shared folder which
conains both the logs from primary server
refer the below link for configuring log shipping just a sample
http://deepakinsql.blogspot.com/2007/06/how-to-configure-log-shipping-in-sql.html
Thanxx
Deepak
"Mahmoud Amin" wrote:
> I am trying to configure Log_Shipping in multiple databases on different
> servers.
> I tried to add it but it has to use the same destination copy folder, is
> that true ?
> i am using SQL2005.
>
>
Monday, March 12, 2012
Log Shipping for multiple databases
Hello
we have SQL instance which contains databases (A, B, C...). When ever i configured LS with Standby option, and i want complete restore of database A (Primary) to stand by A (Secondary), then logs will always going to restore...
but SQL server is taking a copy of the Backup like "GJ_Temp_data, GJ_Temp_log" as the default file names, for restore the DB Backups.
if i want to set up for the database B, it is taking "GJ_Temp_data, GJ_Temp_log" again for the database B, and giving error as "the files are already in use".
If i script the Log shipping setup while enabling for Database A, and make sure that i will enabling it for remaining databases B, C, D..
Please advice, and give us best experienceS for enabling LS FOR Multiple databases on the single SQL Instance.
Thanks in advance.
Pls perform the below steps I assume there are 2 sql servers namely Sql1 and Sql2
1. Take full backup in Sql1 of database A and copy it to shared folder in Sql2 and restore with standby option
2. Take full backup in Sql1 of database B and copy it to shared folder in Sql2 and restore with standby option
3. Start the log backups,copy and restore jobs in principal and secondary servers for both the databases
Performing log shipping in a single sql instance will not server the purpose of log shipping as LS is a high availability solution and in your case if the single instance which holds both the primary and secondary db is down you cannot have a DR solution as a backup to your production db !
Thanxx
Deepak
Subscribe to:
Comments (Atom)