log shipping login sync

Hi,

I have log shipping setup working fine. I created new login (jskow) on primary server and he is a valid user in the database which is configure for log shipping, My secondary server is read-only. I want to give jskow read access on secondary, I added jskow to secondary server, log shipping copied that database user to secondary database , but when I try to login to secondary server and use the read-only database , I get error not a valid user?,

any help?

thanks in advance.

Ram.Run SP_CHANGE_USERS_LOGIN with REPORT clause and see whether the login reported as orphaned user, if so use AUTO_FIX to fix the login.

Refer to BOOKS ONLINE for more information.

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

Log shipping in mssql 2000

Hi,

I am now trying to configure Log Shipping in my compeny but I have encountered some difficulties. The destination site and the source site are far from each other and the transaction logs are too big, this situation causes an huge overload on our private network (we use WAN which is complitly disconnected from the internet). Is there any way to compress the transacion logs with zip or rar and combine it in the log shipping mechanizem?

Is there another way for making this files smaller?

I would be greatful for any ideas in this matter.

Thanks in advance,
Zvi GilinskyThe only way I think is to increase time of Log shipping and meanwhile use compress software and ftp to transfer the file, then unzip it at desired location where LS can acces to restore.

BTW, any chance of hosting another standby server on the network and copy the files to this remote location as contingency.|||Dear Satya,

Correct me if I wrong.
As far as I know LS uses 3 primary jobs: one job on the source and two on the destinaion.
The job on the source creates the transaction logs, one job on the destination copy this files to the destination and the other job applies them on the destination DB.

If I will stop the job that copy the files and replace it by another job that compress these files, transfer them and then extract them won't it demage the LS mechanizem (wrong data in log shipping tables in msdb database)?

I also try to understand what the job that copy the files does but when I I see that it does the following line : EXECUTE master.dbo.xp_sqlmaint'-LSCopyPlainID "plan id"...
but when I query the msdb database : exec sp_help_maintenance_plan
this plan id isn't there. Where else can I see this plan id and it's details?

thanks,
zvi gilinsky|||Try to get dedicated link between primary & secondary servers to ensure no issues on network.

If you've such network problems in complying the log shipping to complete then better to think of contingency solution on a local network and use this remote server as seperate server.

Try to query against master database and see.

Log Shipping Error on SQL 2000 SP4

I'm attempting to configure log shipping on 2 servers with SQL Server 2000 sp4 Enterprise Edition. I keep getting the following error when the job attemtps to execute.

Error 14261: The specified primary_server_name.primary_database_name('C')
already exists.

I have tried this KB http://support.microsoft.com/kb/298743 and i got the same error again!

Please HELP!any hints ? :(|||Just a wild guess... Are you logshipping to the same instance or between to SQL instances? If the latter is the case, have you ran the MS solution on both instances? (just to be sure)