January 12, 2009 at 7:17 am
Hi Everyone,
I have one issue..I have server A and Server B. Now on Server B my sql server agent is disabled. I have setup a maintenance plan on server A to rebuild index and full backup for all the databases in server B. But it is getting failed. any opinion on how to do that. Or is there any other way except setting up maintenance plan on server A to do this stuff.
Please remember my sql server agent on server B is disabled. I want to do that from server A only.
January 12, 2009 at 9:55 am
I haven't personally played with it, but it sounded cool and many have success with it
How to: Create Multiserver Maintenance Plans
http://msdn.microsoft.com/en-us/library/bb153887(SQL.90).aspx
January 13, 2009 at 8:09 am
Here's what we got from further investigation...the backup files are there and backup is also taken but then the job runs for so so long....should it be any issue with msdb database?
January 18, 2009 at 3:40 am
Are the backup files of same date when the job was invoked?
MJ
January 18, 2009 at 3:46 am
RPSql (1/12/2009)
Hi Everyone,I have one issue..I have server A and Server B. Now on Server B my sql server agent is disabled. I have setup a maintenance plan on server A to rebuild index and full backup for all the databases in server B. But it is getting failed. any opinion on how to do that. Or is there any other way except setting up maintenance plan on server A to do this stuff.
Please remember my sql server agent on server B is disabled. I want to do that from server A only.
what error message do you get?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 18, 2009 at 10:20 am
I faced this issue once....and thats bcos i had no SP2 on one node of the cluster.It was solved after installing sp2.
January 18, 2009 at 5:18 pm
I had the same problem, the backups jobs in maintenance would suddenly just run forever and ever.
I never resolved the problem and it happened more than once even microsoft could resolve it.
Eventually rebooted server and it worked, now it has happened again and i now stop the job and it works the next day....why it does this is another story but this is one way to restart the jobs without having to reboot.
If you ever find out the exact reason let me know but i got credit back from ms ..
Cheers
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply