Balancing scalability with availability

We are beginning to design a new application with SQL Server 2005. Our current production environment is slated to be two SQL Server 2005 machines with the databases residing on an EMC SAN. We have requirements to both have automatic failover between servers for availability and also be able to balance the load over two hot servers for scalability.

Can anyone point me in the right direction for things I need to consider in order to be able to implement both of these requirements? Can I implement database mirroring (for failover) and transactional replication (for balancing) given the hardware configuration I'v mentioned? Is more information needed? Where should I turn next?

I am coming off a mainly Oracle background for the last ten or so years with a smattering of SQL Server mixed in. I've tried to hit the ground running on this project, but sometimes find myself hitting the wall running instead.

Thanks,

Larry

Automatic failover can be accomplished with Database Mirroring, and clustering. With both of these technologies the mirrored server or the failover node will be offline so you can't access the databases on these mirrored servers - hence they won't deliver load balancing. For load balancing you could use replication assuming all the DML occurs on one server. Replication will not provide client failover however.

-- Hilary Cotter

|||

That is not correct.

The instance hosting the mirror database is NOT offline. It is online and running otherwise transactions would not be able to reach it. The mirror database is inaccessible, because it is in a recovering state.

As far as clustering goes, the secondary node is also not offline. It is online and functioning, otherwise, there would be no way to failover to the node. There is only one copy of the database within a cluster, so you can't use the secondary node to execute anything.

The combination that is being asked for - automatic failover along with scalability is not possible. Failover clustering will automatically failover, but is not a scalability solution. Database Mirroring running in high availability operating mode will automatically failover, but is not a scalability solution. However, if your applications are not coded to intercept the disconnect and then reconnect to the cluster, it doesn't matter if the cluster automatically fails over, because only those applications forming new connections will find it. If your applications are not coded to utilize the new connection library in ADO.NET that shipped with VS 2005, then your applications are not going to automatically failover to the mirror when it gets promoted.

Replication is your closest bet to getting both fault tolerance as well as scalability. If your applications are built with a connection library that can detect that the server they are connected to is offline and then reform a connection to a secondary server and continue issuing transactions, then you can accomplish the basic goals. Your application then handles the automatic failover while the replication engine keeps everything synchronized to allow scalability. The basic options here are transactional with queued updating subscribers and merge. I would NOT configure a bi-directional or peer-to-peer architecture unless your are going to have full control over your applications and can guarantee that you can never have a conflict generated.

Backup( thru DB Maintenace plan) to another server failing

We have 4 servers in a workgroup environment. I have created 2 users (
SQLOwner and SQLAgent) on all the four servers with Admin privs. On all the
servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
Service.
I have created a DBMaintenance Plan on 3 servers to backup the user
databases directly onto Server 4 ( Use this directory ->
\\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running fine
(for 2 months). All of a sudden the jobs are failing. From the Job History I
see the following error ...
Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
(Error 22029). The step failed.
I see the following error from SQLServer Logs ...
BackupDiskFile::CreateMedia: Backup device
'\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK ' failed to create.
Operating system error = 1330(Logon failure: the specified account password
has expired.).
I verified the password for the user SQLAgent (the owner SQLServer Agent
service) on all the servers and it is same. SQLAgent user is setup as non
expiring account.
When I tried to backup a single database (use this directory ->
\\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
verify backup file location. Do you want to use the backup file location
anyway ?"
RK
Look at
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default...b;en-us;555128
Walk through the troubleshooting steps at the bottom. It is likely a
permissions issue or an expured account issue.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> We have 4 servers in a workgroup environment. I have created 2 users (
> SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> the
> servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
> Service.
> I have created a DBMaintenance Plan on 3 servers to backup the user
> databases directly onto Server 4 ( Use this directory ->
> \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running
> fine
> (for 2 months). All of a sudden the jobs are failing. From the Job History
> I
> see the following error ...
> Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error 22029). The step failed.
> I see the following error from SQLServer Logs ...
> BackupDiskFile::CreateMedia: Backup device
> '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK ' failed to create.
> Operating system error = 1330(Logon failure: the specified account
> password
> has expired.).
> I verified the password for the user SQLAgent (the owner SQLServer Agent
> service) on all the servers and it is same. SQLAgent user is setup as non
> expiring account.
> When I tried to backup a single database (use this directory ->
> \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> verify backup file location. Do you want to use the backup file location
> anyway ?"
>
> --
> RK
|||Thanks fo r the quick Reply Geoff. I figured what the problem was. SQLOwner
account on SQL 03 server ( where all servers are writing their backups) was
expired. I changed it a non-expiring account
I thought for backup jobs we are only concerned about the user running the
SQLServerAgent service, which is SQLAgent user in my case.
"Geoff N. Hiten" wrote:

> Look at
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/default...b;en-us;555128
> Walk through the troubleshooting steps at the bottom. It is likely a
> permissions issue or an expured account issue.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
>
>
|||The SQL Agent invokes the backup command. The SQL engine actually runs the
command so you have to be concerned about the login account for the SQL
Server service, not the SQL Agent service.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...[vbcol=seagreen]
> Thanks fo r the quick Reply Geoff. I figured what the problem was.
> SQLOwner
> account on SQL 03 server ( where all servers are writing their backups)
> was
> expired. I changed it a non-expiring account
> I thought for backup jobs we are only concerned about the user running the
> SQLServerAgent service, which is SQLAgent user in my case.
> "Geoff N. Hiten" wrote:
|||Thank you
"Geoff N. Hiten" wrote:

> The SQL Agent invokes the backup command. The SQL engine actually runs the
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
>
>
|||I am backing up user databases on SQL04, but i am writing the backups to
SQL03 directly (use this directory -> \\SQL03\D$...). How does user account
on SQL03 expiring affect the backup job on SQL04 ?
In my case SQL03 happened to be another SQL Server. What is if the
destination server (SQL03) does not even have a SQL Serer running on it ?
"Geoff N. Hiten" wrote:

> The SQL Agent invokes the backup command. The SQL engine actually runs the
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
>
>
|||The fact that the target server is a SQL server does not matter. It is the
SQL service account from the originating server that must have file system
rights to the target server. If the target server also happens to run a SQL
instance it does not matter.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...[vbcol=seagreen]
>I am backing up user databases on SQL04, but i am writing the backups to
> SQL03 directly (use this directory -> \\SQL03\D$...). How does user
> account
> on SQL03 expiring affect the backup job on SQL04 ?
> In my case SQL03 happened to be another SQL Server. What is if the
> destination server (SQL03) does not even have a SQL Serer running on it ?
> "Geoff N. Hiten" wrote:
|||It makes sense now. Thank you Geoff.
"Geoff N. Hiten" wrote:

> The fact that the target server is a SQL server does not matter. It is the
> SQL service account from the originating server that must have file system
> rights to the target server. If the target server also happens to run a SQL
> instance it does not matter.
> GNH
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...
>
>

Backup( thru DB Maintenace plan) to another server failing

We have 4 servers in a workgroup environment. I have created 2 users (
SQLOwner and SQLAgent) on all the four servers with Admin privs. On all the
servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
Service.
I have created a DBMaintenance Plan on 3 servers to backup the user
databases directly onto Server 4 ( Use this directory ->
\\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running fin
e
(for 2 months). All of a sudden the jobs are failing. From the Job History I
see the following error ...
Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
(Error 22029). The step failed.
I see the following error from SQLServer Logs ...
BackupDiskFile::CreateMedia: Backup device
'\\SQL03\D$\SQLData\SQL04\ExIc_db_200503
150100.BAK' failed to create.
Operating system error = 1330(Logon failure: the specified account password
has expired.).
I verified the password for the user SQLAgent (the owner SQLServer Agent
service) on all the servers and it is same. SQLAgent user is setup as non
expiring account.
When I tried to backup a single database (use this directory ->
\\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
verify backup file location. Do you want to use the backup file location
anyway ?"
RKLook at
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/defaul...kb;en-us;555128
Walk through the troubleshooting steps at the bottom. It is likely a
permissions issue or an expured account issue.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> We have 4 servers in a workgroup environment. I have created 2 users (
> SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> the
> servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
> Service.
> I have created a DBMaintenance Plan on 3 servers to backup the user
> databases directly onto Server 4 ( Use this directory ->
> \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running
> fine
> (for 2 months). All of a sudden the jobs are failing. From the Job History
> I
> see the following error ...
> Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000
]
> (Error 22029). The step failed.
> I see the following error from SQLServer Logs ...
> BackupDiskFile::CreateMedia: Backup device
> '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503
150100.BAK' failed to create.
> Operating system error = 1330(Logon failure: the specified account
> password
> has expired.).
> I verified the password for the user SQLAgent (the owner SQLServer Agent
> service) on all the servers and it is same. SQLAgent user is setup as non
> expiring account.
> When I tried to backup a single database (use this directory ->
> \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> verify backup file location. Do you want to use the backup file location
> anyway ?"
>
> --
> RK|||Thanks fo r the quick Reply Geoff. I figured what the problem was. SQLOwner
account on SQL 03 server ( where all servers are writing their backups) was
expired. I changed it a non-expiring account
I thought for backup jobs we are only concerned about the user running the
SQLServerAgent service, which is SQLAgent user in my case.
"Geoff N. Hiten" wrote:

> Look at
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/defaul...kb;en-us;555128
> Walk through the troubleshooting steps at the bottom. It is likely a
> permissions issue or an expured account issue.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
>
>|||The SQL Agent invokes the backup command. The SQL engine actually runs the
command so you have to be concerned about the login account for the SQL
Server service, not the SQL Agent service.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...[vbcol=seagreen]
> Thanks fo r the quick Reply Geoff. I figured what the problem was.
> SQLOwner
> account on SQL 03 server ( where all servers are writing their backups)
> was
> expired. I changed it a non-expiring account
> I thought for backup jobs we are only concerned about the user running the
> SQLServerAgent service, which is SQLAgent user in my case.
> "Geoff N. Hiten" wrote:
>|||Thank you
"Geoff N. Hiten" wrote:

> The SQL Agent invokes the backup command. The SQL engine actually runs th
e
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
>
>|||I am backing up user databases on SQL04, but i am writing the backups to
SQL03 directly (use this directory -> \\SQL03\D$...). How does user account
on SQL03 expiring affect the backup job on SQL04 ?
In my case SQL03 happened to be another SQL Server. What is if the
destination server (SQL03) does not even have a SQL Serer running on it ?
"Geoff N. Hiten" wrote:

> The SQL Agent invokes the backup command. The SQL engine actually runs th
e
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
>
>|||The fact that the target server is a SQL server does not matter. It is the
SQL service account from the originating server that must have file system
rights to the target server. If the target server also happens to run a SQL
instance it does not matter.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...[vbcol=seagreen]
>I am backing up user databases on SQL04, but i am writing the backups to
> SQL03 directly (use this directory -> \\SQL03\D$...). How does user
> account
> on SQL03 expiring affect the backup job on SQL04 ?
> In my case SQL03 happened to be another SQL Server. What is if the
> destination server (SQL03) does not even have a SQL Serer running on it ?
> "Geoff N. Hiten" wrote:
>|||It makes sense now. Thank you Geoff.
"Geoff N. Hiten" wrote:

> The fact that the target server is a SQL server does not matter. It is th
e
> SQL service account from the originating server that must have file system
> rights to the target server. If the target server also happens to run a S
QL
> instance it does not matter.
> GNH
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...
>
>

Backup( thru DB Maintenace plan) to another server failing

We have 4 servers in a workgroup environment. I have created 2 users (
SQLOwner and SQLAgent) on all the four servers with Admin privs. On all the
servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
Service.
I have created a DBMaintenance Plan on 3 servers to backup the user
databases directly onto Server 4 ( Use this directory ->
\\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running fine
(for 2 months). All of a sudden the jobs are failing. From the Job History I
see the following error ...
Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
(Error 22029). The step failed.
I see the following error from SQLServer Logs ...
BackupDiskFile::CreateMedia: Backup device
'\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
Operating system error = 1330(Logon failure: the specified account password
has expired.).
I verified the password for the user SQLAgent (the owner SQLServer Agent
service) on all the servers and it is same. SQLAgent user is setup as non
expiring account.
When I tried to backup a single database (use this directory ->
\\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
verify backup file location. Do you want to use the backup file location
anyway ?"
--
RKLook at
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
Walk through the troubleshooting steps at the bottom. It is likely a
permissions issue or an expured account issue.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> We have 4 servers in a workgroup environment. I have created 2 users (
> SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> the
> servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
> Service.
> I have created a DBMaintenance Plan on 3 servers to backup the user
> databases directly onto Server 4 ( Use this directory ->
> \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running
> fine
> (for 2 months). All of a sudden the jobs are failing. From the Job History
> I
> see the following error ...
> Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error 22029). The step failed.
> I see the following error from SQLServer Logs ...
> BackupDiskFile::CreateMedia: Backup device
> '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> Operating system error = 1330(Logon failure: the specified account
> password
> has expired.).
> I verified the password for the user SQLAgent (the owner SQLServer Agent
> service) on all the servers and it is same. SQLAgent user is setup as non
> expiring account.
> When I tried to backup a single database (use this directory ->
> \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> verify backup file location. Do you want to use the backup file location
> anyway ?"
>
> --
> RK|||Thanks fo r the quick Reply Geoff. I figured what the problem was. SQLOwner
account on SQL 03 server ( where all servers are writing their backups) was
expired. I changed it a non-expiring account
I thought for backup jobs we are only concerned about the user running the
SQLServerAgent service, which is SQLAgent user in my case.
"Geoff N. Hiten" wrote:
> Look at
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> Walk through the troubleshooting steps at the bottom. It is likely a
> permissions issue or an expured account issue.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> > We have 4 servers in a workgroup environment. I have created 2 users (
> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> > the
> > servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
> > Service.
> >
> > I have created a DBMaintenance Plan on 3 servers to backup the user
> > databases directly onto Server 4 ( Use this directory ->
> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running
> > fine
> > (for 2 months). All of a sudden the jobs are failing. From the Job History
> > I
> > see the following error ...
> >
> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> > (Error 22029). The step failed.
> >
> > I see the following error from SQLServer Logs ...
> >
> > BackupDiskFile::CreateMedia: Backup device
> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> > Operating system error = 1330(Logon failure: the specified account
> > password
> > has expired.).
> >
> > I verified the password for the user SQLAgent (the owner SQLServer Agent
> > service) on all the servers and it is same. SQLAgent user is setup as non
> > expiring account.
> >
> > When I tried to backup a single database (use this directory ->
> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> > verify backup file location. Do you want to use the backup file location
> > anyway ?"
> >
> >
> > --
> > RK
>
>|||The SQL Agent invokes the backup command. The SQL engine actually runs the
command so you have to be concerned about the login account for the SQL
Server service, not the SQL Agent service.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> Thanks fo r the quick Reply Geoff. I figured what the problem was.
> SQLOwner
> account on SQL 03 server ( where all servers are writing their backups)
> was
> expired. I changed it a non-expiring account
> I thought for backup jobs we are only concerned about the user running the
> SQLServerAgent service, which is SQLAgent user in my case.
> "Geoff N. Hiten" wrote:
>> Look at
>> HowTo: Backup to UNC name using Database Maintenance Wizard
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
>> Walk through the troubleshooting steps at the bottom. It is likely a
>> permissions issue or an expured account issue.
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>> Senior Database Administrator
>>
>> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
>> > We have 4 servers in a workgroup environment. I have created 2 users (
>> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
>> > the
>> > servers SQLOwner runs MSSQLServer service and SQLAgent run
>> > SQLSERVERAgent
>> > Service.
>> >
>> > I have created a DBMaintenance Plan on 3 servers to backup the user
>> > databases directly onto Server 4 ( Use this directory ->
>> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
>> > running
>> > fine
>> > (for 2 months). All of a sudden the jobs are failing. From the Job
>> > History
>> > I
>> > see the following error ...
>> >
>> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
>> > (Error 22029). The step failed.
>> >
>> > I see the following error from SQLServer Logs ...
>> >
>> > BackupDiskFile::CreateMedia: Backup device
>> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
>> > Operating system error = 1330(Logon failure: the specified account
>> > password
>> > has expired.).
>> >
>> > I verified the password for the user SQLAgent (the owner SQLServer
>> > Agent
>> > service) on all the servers and it is same. SQLAgent user is setup as
>> > non
>> > expiring account.
>> >
>> > When I tried to backup a single database (use this directory ->
>> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
>> > verify backup file location. Do you want to use the backup file
>> > location
>> > anyway ?"
>> >
>> >
>> > --
>> > RK
>>|||Thank you
"Geoff N. Hiten" wrote:
> The SQL Agent invokes the backup command. The SQL engine actually runs the
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
> > SQLOwner
> > account on SQL 03 server ( where all servers are writing their backups)
> > was
> > expired. I changed it a non-expiring account
> > I thought for backup jobs we are only concerned about the user running the
> > SQLServerAgent service, which is SQLAgent user in my case.
> >
> > "Geoff N. Hiten" wrote:
> >
> >> Look at
> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >>
> >> Walk through the troubleshooting steps at the bottom. It is likely a
> >> permissions issue or an expured account issue.
> >>
> >> Geoff N. Hiten
> >> Microsoft SQL Server MVP
> >> Senior Database Administrator
> >>
> >>
> >>
> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> >> > We have 4 servers in a workgroup environment. I have created 2 users (
> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> >> > the
> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
> >> > SQLSERVERAgent
> >> > Service.
> >> >
> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
> >> > databases directly onto Server 4 ( Use this directory ->
> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
> >> > running
> >> > fine
> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
> >> > History
> >> > I
> >> > see the following error ...
> >> >
> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> >> > (Error 22029). The step failed.
> >> >
> >> > I see the following error from SQLServer Logs ...
> >> >
> >> > BackupDiskFile::CreateMedia: Backup device
> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> >> > Operating system error = 1330(Logon failure: the specified account
> >> > password
> >> > has expired.).
> >> >
> >> > I verified the password for the user SQLAgent (the owner SQLServer
> >> > Agent
> >> > service) on all the servers and it is same. SQLAgent user is setup as
> >> > non
> >> > expiring account.
> >> >
> >> > When I tried to backup a single database (use this directory ->
> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> >> > verify backup file location. Do you want to use the backup file
> >> > location
> >> > anyway ?"
> >> >
> >> >
> >> > --
> >> > RK
> >>
> >>
> >>
>
>|||I am backing up user databases on SQL04, but i am writing the backups to
SQL03 directly (use this directory -> \\SQL03\D$...). How does user account
on SQL03 expiring affect the backup job on SQL04 ?
In my case SQL03 happened to be another SQL Server. What is if the
destination server (SQL03) does not even have a SQL Serer running on it ?
"Geoff N. Hiten" wrote:
> The SQL Agent invokes the backup command. The SQL engine actually runs the
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
> > SQLOwner
> > account on SQL 03 server ( where all servers are writing their backups)
> > was
> > expired. I changed it a non-expiring account
> > I thought for backup jobs we are only concerned about the user running the
> > SQLServerAgent service, which is SQLAgent user in my case.
> >
> > "Geoff N. Hiten" wrote:
> >
> >> Look at
> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >>
> >> Walk through the troubleshooting steps at the bottom. It is likely a
> >> permissions issue or an expured account issue.
> >>
> >> Geoff N. Hiten
> >> Microsoft SQL Server MVP
> >> Senior Database Administrator
> >>
> >>
> >>
> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> >> > We have 4 servers in a workgroup environment. I have created 2 users (
> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> >> > the
> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
> >> > SQLSERVERAgent
> >> > Service.
> >> >
> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
> >> > databases directly onto Server 4 ( Use this directory ->
> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
> >> > running
> >> > fine
> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
> >> > History
> >> > I
> >> > see the following error ...
> >> >
> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> >> > (Error 22029). The step failed.
> >> >
> >> > I see the following error from SQLServer Logs ...
> >> >
> >> > BackupDiskFile::CreateMedia: Backup device
> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> >> > Operating system error = 1330(Logon failure: the specified account
> >> > password
> >> > has expired.).
> >> >
> >> > I verified the password for the user SQLAgent (the owner SQLServer
> >> > Agent
> >> > service) on all the servers and it is same. SQLAgent user is setup as
> >> > non
> >> > expiring account.
> >> >
> >> > When I tried to backup a single database (use this directory ->
> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> >> > verify backup file location. Do you want to use the backup file
> >> > location
> >> > anyway ?"
> >> >
> >> >
> >> > --
> >> > RK
> >>
> >>
> >>
>
>|||The fact that the target server is a SQL server does not matter. It is the
SQL service account from the originating server that must have file system
rights to the target server. If the target server also happens to run a SQL
instance it does not matter.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...
>I am backing up user databases on SQL04, but i am writing the backups to
> SQL03 directly (use this directory -> \\SQL03\D$...). How does user
> account
> on SQL03 expiring affect the backup job on SQL04 ?
> In my case SQL03 happened to be another SQL Server. What is if the
> destination server (SQL03) does not even have a SQL Serer running on it ?
> "Geoff N. Hiten" wrote:
>> The SQL Agent invokes the backup command. The SQL engine actually runs
>> the
>> command so you have to be concerned about the login account for the SQL
>> Server service, not the SQL Agent service.
>> GNH
>> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
>> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
>> > SQLOwner
>> > account on SQL 03 server ( where all servers are writing their backups)
>> > was
>> > expired. I changed it a non-expiring account
>> > I thought for backup jobs we are only concerned about the user running
>> > the
>> > SQLServerAgent service, which is SQLAgent user in my case.
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> Look at
>> >> HowTo: Backup to UNC name using Database Maintenance Wizard
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
>> >>
>> >> Walk through the troubleshooting steps at the bottom. It is likely a
>> >> permissions issue or an expured account issue.
>> >>
>> >> Geoff N. Hiten
>> >> Microsoft SQL Server MVP
>> >> Senior Database Administrator
>> >>
>> >>
>> >>
>> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
>> >> > We have 4 servers in a workgroup environment. I have created 2 users
>> >> > (
>> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On
>> >> > all
>> >> > the
>> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
>> >> > SQLSERVERAgent
>> >> > Service.
>> >> >
>> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
>> >> > databases directly onto Server 4 ( Use this directory ->
>> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
>> >> > running
>> >> > fine
>> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
>> >> > History
>> >> > I
>> >> > see the following error ...
>> >> >
>> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE
>> >> > 42000]
>> >> > (Error 22029). The step failed.
>> >> >
>> >> > I see the following error from SQLServer Logs ...
>> >> >
>> >> > BackupDiskFile::CreateMedia: Backup device
>> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to
>> >> > create.
>> >> > Operating system error = 1330(Logon failure: the specified account
>> >> > password
>> >> > has expired.).
>> >> >
>> >> > I verified the password for the user SQLAgent (the owner SQLServer
>> >> > Agent
>> >> > service) on all the servers and it is same. SQLAgent user is setup
>> >> > as
>> >> > non
>> >> > expiring account.
>> >> >
>> >> > When I tried to backup a single database (use this directory ->
>> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to
>> >> > to
>> >> > verify backup file location. Do you want to use the backup file
>> >> > location
>> >> > anyway ?"
>> >> >
>> >> >
>> >> > --
>> >> > RK
>> >>
>> >>
>> >>
>>|||It makes sense now. Thank you Geoff.
"Geoff N. Hiten" wrote:
> The fact that the target server is a SQL server does not matter. It is the
> SQL service account from the originating server that must have file system
> rights to the target server. If the target server also happens to run a SQL
> instance it does not matter.
> GNH
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...
> >I am backing up user databases on SQL04, but i am writing the backups to
> > SQL03 directly (use this directory -> \\SQL03\D$...). How does user
> > account
> > on SQL03 expiring affect the backup job on SQL04 ?
> >
> > In my case SQL03 happened to be another SQL Server. What is if the
> > destination server (SQL03) does not even have a SQL Serer running on it ?
> >
> > "Geoff N. Hiten" wrote:
> >
> >> The SQL Agent invokes the backup command. The SQL engine actually runs
> >> the
> >> command so you have to be concerned about the login account for the SQL
> >> Server service, not the SQL Agent service.
> >>
> >> GNH
> >>
> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> >> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
> >> > SQLOwner
> >> > account on SQL 03 server ( where all servers are writing their backups)
> >> > was
> >> > expired. I changed it a non-expiring account
> >> > I thought for backup jobs we are only concerned about the user running
> >> > the
> >> > SQLServerAgent service, which is SQLAgent user in my case.
> >> >
> >> > "Geoff N. Hiten" wrote:
> >> >
> >> >> Look at
> >> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >> >>
> >> >> Walk through the troubleshooting steps at the bottom. It is likely a
> >> >> permissions issue or an expured account issue.
> >> >>
> >> >> Geoff N. Hiten
> >> >> Microsoft SQL Server MVP
> >> >> Senior Database Administrator
> >> >>
> >> >>
> >> >>
> >> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> >> >> > We have 4 servers in a workgroup environment. I have created 2 users
> >> >> > (
> >> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On
> >> >> > all
> >> >> > the
> >> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
> >> >> > SQLSERVERAgent
> >> >> > Service.
> >> >> >
> >> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
> >> >> > databases directly onto Server 4 ( Use this directory ->
> >> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
> >> >> > running
> >> >> > fine
> >> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
> >> >> > History
> >> >> > I
> >> >> > see the following error ...
> >> >> >
> >> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE
> >> >> > 42000]
> >> >> > (Error 22029). The step failed.
> >> >> >
> >> >> > I see the following error from SQLServer Logs ...
> >> >> >
> >> >> > BackupDiskFile::CreateMedia: Backup device
> >> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to
> >> >> > create.
> >> >> > Operating system error = 1330(Logon failure: the specified account
> >> >> > password
> >> >> > has expired.).
> >> >> >
> >> >> > I verified the password for the user SQLAgent (the owner SQLServer
> >> >> > Agent
> >> >> > service) on all the servers and it is same. SQLAgent user is setup
> >> >> > as
> >> >> > non
> >> >> > expiring account.
> >> >> >
> >> >> > When I tried to backup a single database (use this directory ->
> >> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to
> >> >> > to
> >> >> > verify backup file location. Do you want to use the backup file
> >> >> > location
> >> >> > anyway ?"
> >> >> >
> >> >> >
> >> >> > --
> >> >> > RK
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>