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
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>

Backup to network drive using Workgroup/Standard.

I am using SQL Server 2005 Express Edition. I am planning on upgrading to either Workgroup or Standard edition. While working with Express Edition I did find out that this version does not support backup to a network drive.
My question is:

Is it possible to backup directly to a network drive using a Workgroup/ Standard edition of SQL Server rather than backing up to a local drive and then 'copy and paste' to a network drive like the Express Edition.

My other question is :
Given a database limit of 50GB, which one of the editions, Workgroup or Standard, will be appropriate for use.Thank you for your time and patience.
Regards
Berly Sam

You cannot backup to a network share with any edition of SQL Server.

SQL Server Backup will only used locally attached drives, or NAS/SAN LUNs. You can either backup locally, and then move the file to a network share (both tasks can be automated with SQL Agent -not included with SQL Express), or Check out the several third party backup tools. (Idera, Red-Gate, to name a couple.)

Workgroup-Standard-Enterprise, which is 'best'. It depends upon the functionality that you require. With a database of that size, you are definitely between the Standard and Enterprise Editions (in my opinion). You may wish to check out the functionality differences at this site.

|||Thats not exactly true, you cannot see the backup media in the SQL Server dialog as it only displays local fixed drives, but you can specify a UNC share within the dialog textbox or within the script. Depending on the situation you should rather consider using a local /SAN / NAS backup first and then copy it to a network share if needed.

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Jens,

I consider it a gentle ‘challenge’ for me to give more consideration to why I responded as I did. And I appreciate that.

As I contemplate why I thought so, all I can remember is ever since 6.5, I have always taught to backup locally and xcopy to a net share. I can only imagine that was because of the speed issues of what used to be slower networks, as well as the persistence and permissions issues related to mapped drives.

And I now realize that I have not reconsidered or changed that practice in the intervening years.

I’m glad that you challenged me, now I have tested and affirmed that a backup to a UNC works just fine. But I doubt that I will change my practice of Backing up locally and using xcopy to move the backup file to a network resource -the BACKUP won't fail because of any network issues.

Regards,

- Arnie Rowland

Backup to a share

Hi, I have 2 win2k3, they are in a workgroup and the credential I use to open
a session on both machines is "Administrator", "password". SQL server account
is the same (administrator).
I on the sql box, I create a share to the 2nd box. I can create, deleteor do
anything on this share. However, when I create a maintenance plan to backup
some DBs to this share, the job fails.
I tried UNC,it did not work neither.
How can or is it possible to backup to a share?
ThanksOf course this is possible. Start by giving permissions on that share to the
Windows account used by the SQL Server service, that is, that account must be
able to write files to that share. Connect as that account and make sure you
have access to the share.
If the job still does not work go to the View History section of the job and
look for error messages. Also take a look at the SQL Server error log.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"SalamElias" wrote:
> Hi, I have 2 win2k3, they are in a workgroup and the credential I use to open
> a session on both machines is "Administrator", "password". SQL server account
> is the same (administrator).
> I on the sql box, I create a share to the 2nd box. I can create, deleteor do
> anything on this share. However, when I create a maintenance plan to backup
> some DBs to this share, the job fails.
> I tried UNC,it did not work neither.
> How can or is it possible to backup to a share?
> Thanks|||SQL Server itself (and SQL Server Agent) are not running as Administrator,
are they? When you map a drive letter, it is mapped for YOUR username only.
This drive letter is not visible to other users (e.g. the user that SQL
services run as).
When you tried a UNC path, what does "did not work" mean? Do you get an
error message? If so, what is it?
"SalamElias" <eliassal@.online.nospam> wrote in message
news:56435BAD-689C-468E-AE71-894760DB63BD@.microsoft.com...
> Hi, I have 2 win2k3, they are in a workgroup and the credential I use to
> open
> a session on both machines is "Administrator", "password". SQL server
> account
> is the same (administrator).
> I on the sql box, I create a share to the 2nd box. I can create, deleteor
> do
> anything on this share. However, when I create a maintenance plan to
> backup
> some DBs to this share, the job fails.
> I tried UNC,it did not work neither.
> How can or is it possible to backup to a share?
> Thanks|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/kb/555128
For SQL 2000, but it works just the same for SQL 2005 as far as required
permissions.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"SalamElias" <eliassal@.online.nospam> wrote in message
news:56435BAD-689C-468E-AE71-894760DB63BD@.microsoft.com...
> Hi, I have 2 win2k3, they are in a workgroup and the credential I use to
> open
> a session on both machines is "Administrator", "password". SQL server
> account
> is the same (administrator).
> I on the sql box, I create a share to the 2nd box. I can create, deleteor
> do
> anything on this share. However, when I create a maintenance plan to
> backup
> some DBs to this share, the job fails.
> I tried UNC,it did not work neither.
> How can or is it possible to backup to a share?
> Thanks|||As I said, both credetnials are the same and I can create, delete modify any
file in the share which are used to run both services SQL server and agnet
When editing the MP, in the backup task page, I click on the button with 3
dots opposite to folder, I see only the local disks C:\ and E:\ not the
mapped share Z:\backup.
Regards
"Ben Nevarez" wrote:
> Of course this is possible. Start by giving permissions on that share to the
> Windows account used by the SQL Server service, that is, that account must be
> able to write files to that share. Connect as that account and make sure you
> have access to the share.
> If the job still does not work go to the View History section of the job and
> look for error messages. Also take a look at the SQL Server error log.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "SalamElias" wrote:
> > Hi, I have 2 win2k3, they are in a workgroup and the credential I use to open
> > a session on both machines is "Administrator", "password". SQL server account
> > is the same (administrator).
> > I on the sql box, I create a share to the 2nd box. I can create, deleteor do
> > anything on this share. However, when I create a maintenance plan to backup
> > some DBs to this share, the job fails.
> > I tried UNC,it did not work neither.
> > How can or is it possible to backup to a share?
> >
> > Thanks

Backup to a share

Hi, I have 2 win2k3, they are in a workgroup and the credential I use to open
a session on both machines is "Administrator", "password". SQL server account
is the same (administrator).
I on the sql box, I create a share to the 2nd box. I can create, deleteor do
anything on this share. However, when I create a maintenance plan to backup
some DBs to this share, the job fails.
I tried UNC,it did not work neither.
How can or is it possible to backup to a share?
Thanks
Of course this is possible. Start by giving permissions on that share to the
Windows account used by the SQL Server service, that is, that account must be
able to write files to that share. Connect as that account and make sure you
have access to the share.
If the job still does not work go to the View History section of the job and
look for error messages. Also take a look at the SQL Server error log.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"SalamElias" wrote:

> Hi, I have 2 win2k3, they are in a workgroup and the credential I use to open
> a session on both machines is "Administrator", "password". SQL server account
> is the same (administrator).
> I on the sql box, I create a share to the 2nd box. I can create, deleteor do
> anything on this share. However, when I create a maintenance plan to backup
> some DBs to this share, the job fails.
> I tried UNC,it did not work neither.
> How can or is it possible to backup to a share?
> Thanks
|||SQL Server itself (and SQL Server Agent) are not running as Administrator,
are they? When you map a drive letter, it is mapped for YOUR username only.
This drive letter is not visible to other users (e.g. the user that SQL
services run as).
When you tried a UNC path, what does "did not work" mean? Do you get an
error message? If so, what is it?
"SalamElias" <eliassal@.online.nospam> wrote in message
news:56435BAD-689C-468E-AE71-894760DB63BD@.microsoft.com...
> Hi, I have 2 win2k3, they are in a workgroup and the credential I use to
> open
> a session on both machines is "Administrator", "password". SQL server
> account
> is the same (administrator).
> I on the sql box, I create a share to the 2nd box. I can create, deleteor
> do
> anything on this share. However, when I create a maintenance plan to
> backup
> some DBs to this share, the job fails.
> I tried UNC,it did not work neither.
> How can or is it possible to backup to a share?
> Thanks
|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/kb/555128
For SQL 2000, but it works just the same for SQL 2005 as far as required
permissions.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"SalamElias" <eliassal@.online.nospam> wrote in message
news:56435BAD-689C-468E-AE71-894760DB63BD@.microsoft.com...
> Hi, I have 2 win2k3, they are in a workgroup and the credential I use to
> open
> a session on both machines is "Administrator", "password". SQL server
> account
> is the same (administrator).
> I on the sql box, I create a share to the 2nd box. I can create, deleteor
> do
> anything on this share. However, when I create a maintenance plan to
> backup
> some DBs to this share, the job fails.
> I tried UNC,it did not work neither.
> How can or is it possible to backup to a share?
> Thanks
|||As I said, both credetnials are the same and I can create, delete modify any
file in the share which are used to run both services SQL server and agnet
When editing the MP, in the backup task page, I click on the button with 3
dots opposite to folder, I see only the local disks C:\ and E:\ not the
mapped share Z:\backup.
Regards
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Of course this is possible. Start by giving permissions on that share to the
> Windows account used by the SQL Server service, that is, that account must be
> able to write files to that share. Connect as that account and make sure you
> have access to the share.
> If the job still does not work go to the View History section of the job and
> look for error messages. Also take a look at the SQL Server error log.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "SalamElias" wrote: