October 15, 2009 at 2:43 pm
I am receiving a message - Unable to copy the initialization file to the secondary server. I have registered the full secondary domain server name in Enterprise Mgr. I have the setup account with sysadmin and dbo of database. The setup account is also a domain account. However, I have 2 other accounts on the primary server, one for sql server and one for the sql agent. These two accounts have also been changed to be domain accounts and have sysadmin and dbo rights to database to be logshipped. I have several questions, do any of these accts need access to any other databases besides the database to be logshipped? The logshipping setup acct, the sql agent acct and sql server acct has access to write to the logshipping share and these same 3 accts have access to the read/write/update acess on the secondary server directory setup to receive the logs. I dont know why I would have this error when I know I can write to the directory. I have reviewed MS 811890. Everytime the setup failes I have to run a sql to cleanup the primary logshipping info in the msdb database. I have also changed the monitor server to be the secondary server so I had to cleanup the monitor server info in the msdb database. No matter what I do, I cannot get past this error. Help!!!!
October 15, 2009 at 4:04 pm
I failed to mention that I cannot create the maintenance plan so I can't just restore the database to the standby and keep going,
Thanks everyone.
October 15, 2009 at 5:38 pm
You can setup the database on the secondary server manually by using RESTORE DATABASE with an undo file. Then in the log shipping setup, you tell it that the database already exists.
MJ
October 16, 2009 at 2:04 pm
I did this and created the maintenance plan and jobs on both the primary and secondary servers. However, now I am monitoring the process and I am finding that the transaction log backups are not being copied over to the secondary server. The backup job on the primary server runs successfully created a tran log backup file. The copy job on the secondary server runs to success, however no tran logs backups are being copied over, the restore job on the secondary server runs to success, but no transaction logs are there to restore. I'm not sure where to look at to fix this.
Anyone have any ideas?
Thanks again.,
October 16, 2009 at 2:39 pm
I failed to mention that I decided that to put the log shipping monitor on the secondary server. I read somewhere that MS recommends putting it there in case you lose the primary, you can still view where logshipping stands on the secondary server. Don't know if that would cause stop the transaction log from being copied to the secondary server.
October 16, 2009 at 5:03 pm
Try to run the transaction log copy job command under query analyzer and see if it copies the files or not. Seems to be a permission issue altogether.
Also, while executing job from QA it will run from your security context.
MJ
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply