log shipping with cluster

is there any link about logshipping with windows 2000 cluster ?

Have you encountered a problem? These two technologies are independent of each other and shouldn't have problems when used together.|||

Hi Matt,

case closed, thank you for you response.

t tried to configure the log shipping from the passive node, not the owner, thats why it failed. thx.

sql

log shipping with cluster

is there any link about logshipping with windows 2000 cluster ?

Have you encountered a problem? These two technologies are independent of each other and shouldn't have problems when used together.|||

Hi Matt,

case closed, thank you for you response.

t tried to configure the log shipping from the passive node, not the owner, thats why it failed. thx.

Log Shipping Transaction Logs.

Hi,

We currently have a couple a large Databases running on SQL 2000 SP3 Clustered Windows 2000 SP3 environment.

Log Shipping is enabled for both databases shipping to a Standalone SQL 2000 SP3 Windows 2000 SP3 box.

Log Shipping occurs every 15 mins with the Transaction Files on average being no more than 500KB in size. However, every now and then a Transaction Log comes through and it can be as big as 3.52GB.

Not sure why this is happening. Anyone got any ideas?

Regards

Paul TowlerIs this after substantial activity or reindexing?|||i think auto shrink or some other job is enabled
if iam right, the auto shrink or job gets activated and the step goes thru
which will obviously create transaction file with huge size.|||Thanks for your replies.

There is a Job to Optimise the Database which does re-index the database. I presume all the indexing changes count as changes and therefore shipped as one big Transacton file.

Hopefully there is a way to prevent these hugh Transaction Files without turning off the indexing job.

Regards
Paul Towlersql

log shipping restore failure

I don't understand, have sql 2000 on a win2000server. I set the sqlserver to
startup using the ./administrator account.
I use Windows XP on my destkop and use desktop connection to get to the
server. I log on as the administrator account.
I created a log shipping maintenance plan. As long as I am logged on to the
server, and use the SA account to register the servers in in Ent Manager.
The jobs ALL run fine. Until I log off. Once off, the jobs all go to hell..
The restores all start to fail. The backups still work, but the restores
fail. This happens every time I recreate the jobs. I get the following
erron on the restore
.....Executed as user: CHLSNT010\Administrator. sqlmaint.exe failed.
[SQLSTATE 42000] (Error 22029). The step failed.
I can't find anything on error 22029.
Can anyone help with this.
Thanks
Gordon
You'll find more details when you right click on the plan and view history
or details ..
"gordon" <gordon@.discussions.microsoft.com> wrote in message
news:EBFCF72E-CE7A-4660-9C4C-812BEE4336E6@.microsoft.com...
> I don't understand, have sql 2000 on a win2000server. I set the sqlserver
to
> startup using the ./administrator account.
> I use Windows XP on my destkop and use desktop connection to get to the
> server. I log on as the administrator account.
> I created a log shipping maintenance plan. As long as I am logged on to
the
> server, and use the SA account to register the servers in in Ent Manager.
> The jobs ALL run fine. Until I log off. Once off, the jobs all go to
hell..
> The restores all start to fail. The backups still work, but the restores
> fail. This happens every time I recreate the jobs. I get the following
> erron on the restore
> ....Executed as user: CHLSNT010\Administrator. sqlmaint.exe failed.
> [SQLSTATE 42000] (Error 22029). The step failed.
> I can't find anything on error 22029.
> Can anyone help with this.
> Thanks
> Gordon
|||Yes, there is no failure there. Only as below. Any ideas why?
"Hassan" wrote:

> You'll find more details when you right click on the plan and view history
> or details ..
> "gordon" <gordon@.discussions.microsoft.com> wrote in message
> news:EBFCF72E-CE7A-4660-9C4C-812BEE4336E6@.microsoft.com...
> to
> the
> hell..
>
>

Log Shipping Question

Hello,
I want to setup SQL Log Shipping btwn two servers.
- Do the servers have to run same version of Windows? Can one be Win2003 and
the other Win2K Server? Or one Win2k Advanced and one Win2k Standard Server?
- Do I have to run the same version/build/ServicePack of SQL Server?
many thanks
christos
If you are using the Enterprise Edition of SQL Server's Log Shipping
functions both SQL Server's have to be Enterprise Edition. If you are
rolling your own version of Log Shipping, there are no SQL Server version
requirements or OS requirements (other than NT workstation/server, XP
professional, Win2k server/professional, Windows 2003).
"Christos Kritikos" <ChristosKritikos@.discussions.microsoft.com> wrote in
message news:D025AB19-599D-4806-9817-2804C182F38A@.microsoft.com...
> Hello,
> I want to setup SQL Log Shipping btwn two servers.
> - Do the servers have to run same version of Windows? Can one be Win2003
and
> the other Win2K Server? Or one Win2k Advanced and one Win2k Standard
Server?
> - Do I have to run the same version/build/ServicePack of SQL Server?
> many thanks
> christos
>

Log Shipping problem

I have several SQL Server 2000 SP4 instances on Windows 2003 Advanced Server and Datacenter Edition shipping logs to a SQL Server 2000 SP4 instance on Windows 2003 Advanced Server. All of the log shipping pairs work fine except in the case of one instance. When I set up a log shipping pair from it, the maintenance plan, jobs and entries in the system tables are created successfuly, the initial database (which is small in my example) is backed up as part of the log shipping setup, copied to the secondary server and restored. But when the "copy" job executes in the secondary server, it doesn't copy the transaction log backups from the backup server. Other log shipping pairs established from other primaries to this secondary server work fine, so I know it is not a communications problem between this particular primary and the secondary server. The "copy" job indicates that it succeeds, but it doesn't do anything. I use LiteSpeed 2005 both on the primaries and on the secondary server. In the secondary server I have LiteSpeed's NCS (Native Command Substitution) installed, since the Log Shipping maintenance plans cannot be converted to LiteSpeed. Again, this works fine for all other instances. The configuration settings of the problematic primary are analogous to the configuration settings of the other instances. Log shipping used to work from the problematic primary to other secondary server, but not now. I suspect that this has something to do with inconsistencies in some system tables in the primary server. Has anyone a hint to offer?

If you are using the third party tool, have you contacted the vendor in first place.

If it is a SQL Server log shipping, then I would suggest to check SQL error log and event logs on both the servers to ensure there is no issue with SQL components, also you might take help of network admin to see why this is happenning with a network trace etc.

Log Shipping Error 4323

Hi all,

Scenario : MS Windows 2003 SP1 - MS SQL Server 2000 EE SP4

Log Shipping

My secondary server was restoring backup logs successfully, but suddenly i got the following error:

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4323: [Microsoft][ODBC SQL Server Driver][SQL Server]The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

How can I fix this situation without re create the maintenance plan ?

We had the same issue some time ago, this was related to a new file being created in a filegroup on the source. Don't know if this applies to your case, but restoring a backup of this new file on the secondary server solved the pb (unless we had to restore the whole db, sorry I can't remember, my memory is gone... together with the customer :o).

HTH,

Vincent

Log Shipping Error 4323

Hi all,

Scenario : MS Windows 2003 SP1 - MS SQL Server 2000 EE SP4

Log Shipping

My secondary server was restoring backup logs successfully, but suddenly i got the following error:

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4323: [Microsoft][ODBC SQL Server Driver][SQL Server]The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

How can I fix this situation without re create the maintenance plan ?

We had the same issue some time ago, this was related to a new file being created in a filegroup on the source. Don't know if this applies to your case, but restoring a backup of this new file on the secondary server solved the pb (unless we had to restore the whole db, sorry I can't remember, my memory is gone... together with the customer :o).

HTH,

Vincent

Log shipping error

Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
local user on both machines same username and password.
The user has the following on both servers.
act as operating system
logon as a batch job
logon as a service
When I run through the Database Maintenance Plan Wizard, at the last
screen when doing the steps I get the error.
Unable to copy the initialization file to the secondary server.
I have searched endlessly for the reason but have been unsuccessful.
Can anyone shed some light on what I could be missing.
Thanks.I think, your local accoutn not geeting acces the seconary mechines
folder. create a Mapped drive to the secondary server and try to copy
the backup.
pisquem@.gmail.com wrote:
> Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
> local user on both machines same username and password.
> The user has the following on both servers.
> act as operating system
> logon as a batch job
> logon as a service
> When I run through the Database Maintenance Plan Wizard, at the last
> screen when doing the steps I get the error.
> Unable to copy the initialization file to the secondary server.
> I have searched endlessly for the reason but have been unsuccessful.
> Can anyone shed some light on what I could be missing.
> Thanks.|||I tried as you described and I was able to map a drive, connect to it
and copy the file over.
Any other ideas?

Log shipping error

Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
local user on both machines same username and password.
The user has the following on both servers.
act as operating system
logon as a batch job
logon as a service
When I run through the Database Maintenance Plan Wizard, at the last
screen when doing the steps I get the error.
Unable to copy the initialization file to the secondary server.
I have searched endlessly for the reason but have been unsuccessful.
Can anyone shed some light on what I could be missing.
Thanks.
I think, your local accoutn not geeting acces the seconary mechines
folder. create a Mapped drive to the secondary server and try to copy
the backup.
pisquem@.gmail.com wrote:
> Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
> local user on both machines same username and password.
> The user has the following on both servers.
> act as operating system
> logon as a batch job
> logon as a service
> When I run through the Database Maintenance Plan Wizard, at the last
> screen when doing the steps I get the error.
> Unable to copy the initialization file to the secondary server.
> I have searched endlessly for the reason but have been unsuccessful.
> Can anyone shed some light on what I could be missing.
> Thanks.
|||I tried as you described and I was able to map a drive, connect to it
and copy the file over.
Any other ideas?

Log shipping error

Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
local user on both machines same username and password.
The user has the following on both servers.
act as operating system
logon as a batch job
logon as a service
When I run through the Database Maintenance Plan Wizard, at the last
screen when doing the steps I get the error.
Unable to copy the initialization file to the secondary server.
I have searched endlessly for the reason but have been unsuccessful.
Can anyone shed some light on what I could be missing.
Thanks.I think, your local accoutn not geeting acces the seconary mechines
folder. create a Mapped drive to the secondary server and try to copy
the backup.
pisquem@.gmail.com wrote:
> Ok I have 2 stand alone SQL Servers on Windows 2003 server. i have a
> local user on both machines same username and password.
> The user has the following on both servers.
> act as operating system
> logon as a batch job
> logon as a service
> When I run through the Database Maintenance Plan Wizard, at the last
> screen when doing the steps I get the error.
> Unable to copy the initialization file to the secondary server.
> I have searched endlessly for the reason but have been unsuccessful.
> Can anyone shed some light on what I could be missing.
> Thanks.|||I tried as you described and I was able to map a drive, connect to it
and copy the file over.
Any other ideas?

Log shipping / Standby

Hi,
I have to create a standby Server for the Production Server using Log
Shipping. These are the details:
Production Server:
OS: Windows 2000 Server SP4
SQL Server: SQL Server Enterprise Edition 8.00.650(SP2)
Standby Server:
OS: Windows 2003 Server Standard Edition
SQL Server: SQL Server Enterprise Edition 8.00.760(SP3)
Production Server do not have any DTS packages but there are a couple of
jobs and DTS packages that import and export data from the Production server.
They do not reside on the Production server. Is it a good idea to recreate
all these jobs and DTS packages on the same server using the name of standby
server and once the Production Server goes down - disable jobs referencing
Production server and enable jobs referencing standby server? Can I create
the logins on the standby server and start using them once the Production
Server goes down?
Thanks in advance.
Hi
Yes you cam move jobs and packages to the standby server, you sure , you
will have to create a login for connection
Remember,Log shipping failover is not automatic.
http://www.sql-server-performance.com/sql_server_log_shipping.asp
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:2884B662-4101-4385-9E58-25978961C48D@.microsoft.com...
> Hi,
> I have to create a standby Server for the Production Server using Log
> Shipping. These are the details:
> Production Server:
> OS: Windows 2000 Server SP4
> SQL Server: SQL Server Enterprise Edition 8.00.650(SP2)
> Standby Server:
> OS: Windows 2003 Server Standard Edition
> SQL Server: SQL Server Enterprise Edition 8.00.760(SP3)
> Production Server do not have any DTS packages but there are a couple of
> jobs and DTS packages that import and export data from the Production
> server.
> They do not reside on the Production server. Is it a good idea to recreate
> all these jobs and DTS packages on the same server using the name of
> standby
> server and once the Production Server goes down - disable jobs referencing
> Production server and enable jobs referencing standby server? Can I create
> the logins on the standby server and start using them once the Production
> Server goes down?
> Thanks in advance.

Log shipping / Standby

Hi,
I have to create a standby Server for the Production Server using Log
Shipping. These are the details:
Production Server:
OS: Windows 2000 Server SP4
SQL Server: SQL Server Enterprise Edition 8.00.650(SP2)
Standby Server:
OS: Windows 2003 Server Standard Edition
SQL Server: SQL Server Enterprise Edition 8.00.760(SP3)
Production Server do not have any DTS packages but there are a couple of
jobs and DTS packages that import and export data from the Production server.
They do not reside on the Production server. Is it a good idea to recreate
all these jobs and DTS packages on the same server using the name of standby
server and once the Production Server goes down - disable jobs referencing
Production server and enable jobs referencing standby server? Can I create
the logins on the standby server and start using them once the Production
Server goes down?
Thanks in advance.Hi
Yes you cam move jobs and packages to the standby server, you sure , you
will have to create a login for connection
Remember,Log shipping failover is not automatic.
http://www.sql-server-performance.com/sql_server_log_shipping.asp
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:2884B662-4101-4385-9E58-25978961C48D@.microsoft.com...
> Hi,
> I have to create a standby Server for the Production Server using Log
> Shipping. These are the details:
> Production Server:
> OS: Windows 2000 Server SP4
> SQL Server: SQL Server Enterprise Edition 8.00.650(SP2)
> Standby Server:
> OS: Windows 2003 Server Standard Edition
> SQL Server: SQL Server Enterprise Edition 8.00.760(SP3)
> Production Server do not have any DTS packages but there are a couple of
> jobs and DTS packages that import and export data from the Production
> server.
> They do not reside on the Production server. Is it a good idea to recreate
> all these jobs and DTS packages on the same server using the name of
> standby
> server and once the Production Server goes down - disable jobs referencing
> Production server and enable jobs referencing standby server? Can I create
> the logins on the standby server and start using them once the Production
> Server goes down?
> Thanks in advance.

Log shipping / Standby

Hi,
I have to create a standby Server for the Production Server using Log
Shipping. These are the details:
Production Server:
OS: Windows 2000 Server SP4
SQL Server: SQL Server Enterprise Edition 8.00.650(SP2)
Standby Server:
OS: Windows 2003 Server Standard Edition
SQL Server: SQL Server Enterprise Edition 8.00.760(SP3)
Production Server do not have any DTS packages but there are a couple of
jobs and DTS packages that import and export data from the Production server
.
They do not reside on the Production server. Is it a good idea to recreate
all these jobs and DTS packages on the same server using the name of standby
server and once the Production Server goes down - disable jobs referencing
Production server and enable jobs referencing standby server? Can I create
the logins on the standby server and start using them once the Production
Server goes down?
Thanks in advance.Hi
Yes you cam move jobs and packages to the standby server, you sure , you
will have to create a login for connection
Remember,Log shipping failover is not automatic.
http://www.sql-server-performance.c...og_shipping.asp
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:2884B662-4101-4385-9E58-25978961C48D@.microsoft.com...
> Hi,
> I have to create a standby Server for the Production Server using Log
> Shipping. These are the details:
> Production Server:
> OS: Windows 2000 Server SP4
> SQL Server: SQL Server Enterprise Edition 8.00.650(SP2)
> Standby Server:
> OS: Windows 2003 Server Standard Edition
> SQL Server: SQL Server Enterprise Edition 8.00.760(SP3)
> Production Server do not have any DTS packages but there are a couple of
> jobs and DTS packages that import and export data from the Production
> server.
> They do not reside on the Production server. Is it a good idea to recreate
> all these jobs and DTS packages on the same server using the name of
> standby
> server and once the Production Server goes down - disable jobs referencing
> Production server and enable jobs referencing standby server? Can I create
> the logins on the standby server and start using them once the Production
> Server goes down?
> Thanks in advance.

Log Shipping (SQL 2000) btwn OS versions?

Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on Windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks |||yellowbug wrote:
> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on Windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log Shipping (SQL 2000) btwn OS versions?

Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks :)|||yellowbug wrote:
> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks :)
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com