July 1, 2004 at 1:36 pm
Hi:
I am experiencing problems with master/target servers. First, the specs:
Server 1:
---SQL Server 7.0 - 7.00.961
---Standard Edition on Windows NT 4.0
---Service Pack 6
---Security is Mixed Authentication
---Using SQL Server authentication for BOTH SQL Server and SQL Server Agent connections(identical logons, etc)
Server 2:
---SQL Server 2000 - 8.00.760
---Desktop Engine on Windows NT 5.0 (MSDE 2000)
---Service Pack 4
---Enterprise Manager 2000 installed
---Security is Mixed Authentication
---Using Windows authentication for BOTH SQL Server and SQL Server Agent connections (identical logins, etc)
---Terminal Services
The backup tape drive is on Server 1. We need to be able to back up the databases on Server 2, therefore, I am using Enterprise Manager 2000 on Server 2 to try and initiate the multiserver administration process and define Server 1 as Master. When I go through the process of defining Server 1 as a Master, I experience problems while trying to enlist Server 2 as the target. Here is what I get:
"The SQL Server and SQL Server Agent logon accounts must be changed."
I don't understand. Both the SQL Server and SQL Server Agent logon accounts are the same. After pressing "OK," I type in the account name and password and receive the following error:
"Unable to verify whether this is a valid account. Try specifying a different account."
Thanks so much!
Eve
July 1, 2004 at 3:35 pm
I am not sure what acounts you are talking about when you say :
Server 1 Using SQL Server authentication for BOTH SQL Server and SQL Server Agent connections(identical logons, etc)
Server 2 Using Windows authentication for BOTH SQL Server and SQL Server Agent connections (identical logins, etc)
Do you mean how you (your Enterprise Manager) connect(s) to SQL server OR you mean startup accounts for SQL Server and Agent? It is evident that SQL account could not be startup account for a service. Windows service should be started on the Windows Domain account in order for this service to access anything on the network using Windows authentication. If you are using Local System or any local user account for the starup account for Agent service you have to get an error message that the account could not be valiudated. This is also the case when the servers and accounts are in different domains that don't trust each other.
I advise to start all 4 services (2 on each server) on the same Domain account, give this account System Administrators membership in both SQL Servers AND make sure this account has required Windows rights to do your jobs. The best is to add this account to Windows Administrators on both servers provided that Builtin\Administrators in SQL Server have sysadmin rights.
Yelena
Regards,Yelena Varsha
July 1, 2004 at 4:23 pm
Hi Yelena:
Thank you for helping and being patient with me. I managed to make Server 1 as a master but was unsuccessful in enlisting Server 2 as a target. The error message I get is:
"Error 14539: Only a Standard or Enterprise Edition of SQL Server can be enlisted into an MSX."
1.) Do I HAVE to upgrade Server 2 to the standard edition of 2000? Is there no way around that?
2.) If so, are there any issues I need to be aware of (aside from backing up) before doing so?
3.) Since Server 1 is running SQL Server 7.0 (standard), do you forsee any problems with it being a Master?
Thanks again,
Eve
July 2, 2004 at 8:09 am
Eve,
I don't maintain master/target architecture at all for the reason that we usually have a "server by project/department " way of doing things. Departmnets like to have a server to themselves even if it is located in the Data Center. They usually don't like an admin account from another server to access their server. The most I maintain is a read-only login to MSDB to check for backup jobs from the web page. We have all servers backed up to tapes centrally, so I did not have a need yet.
Now to your solutions: since I am also a solution developer (sort of) I guess I have to suggest something.
What I would probably do. Schedule your regular DB Backups on Server 2 (MSDE). Add the second step to the backup job to copy the SQL backup files to Server 1 OR use a Windows Scheduler on Server 1 or server 2 to copy those backup files from Server 2 to Server 1. Then use SQL Server or Windows Scheduler on Server 1 or your backup SW to backup those files on tape. I use just basic Copy command to copy files.
I use this second or a third step to a job to copy backups from the server to a network location if I want to get database or transaction log backups off the machine to the network location right away for data protection because we are running Windows tape backups only once a day.
Let me know if you need more help. I am out of the office Mon Jul 5
Yelena
Regards,Yelena Varsha
July 2, 2004 at 10:57 am
Thank you so much Yelena. I will definitely try it!
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply