March 28, 2003 at 9:10 am
This is in response to an email I received in which I thought some you fellow members might want to give imput to. Jay I hope this was okay that I posted it here.
Jay you cannot directly log ship the msdb and master databases for these databases must be online on the standby server.
What you can try, I have yet had a need to do this, is log ship msdb to standby as another dbname, from there experiment on either coming up on the renamed msdb (stopping all services, renaming the msdb data files, then start SQL back up. Alternately, another option might be to just DTS over the msdb replication tables(however I am a bit green on this idea).
Either way it's a bit out of the box and you most definitely will need some heavy testing.
Not sure why you would want to log ship master. Other than the initial setup. The only thing I ever maintain from here is logins, and for that I use scripts.
cheers
quote:
hey man u can be a big help of mine after reading that u have log shipped 60 database,>have u ever done a log shipping of databse on a server which is getting replicated, ie it is a publisher and many subscriber to that database, i want to have a log shipping of that database, ie, if i change any publication properties on my production server, how does it change in the stand by server, i guess to my knowledge it should be done by log shipping msdb and master database. and how do i transfer jobs from my production to back up servers.
>
>thnks in advance
>
>Regards
>Jay
>
John Zacharkan
John Zacharkan
March 28, 2003 at 9:41 am
I would also use DTS packages to export the data that you need. If you want to also replicate the jobs, I would set my production server as a master server, and all my backups servers as target servers. This way you create and modify all your jobs you need, and they are downloaded from your target servers you specify.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply