Basic Question

We want to set up another office as an online disaster recovery site. Can I
clister between two SQL servers over a T1?
Your best bet is using third party software, though you might be able to use
MNS (Majority Node Set). Have you looked into Log Shipping with SQL?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Rick Vines" <Rick Vines@.discussions.microsoft.com> wrote in message
news:640BDCB1-F523-4B21-AF91-AB24D58D2DCD@.microsoft.com...
> We want to set up another office as an online disaster recovery site. Can
> I
> clister between two SQL servers over a T1?

Bandwidth Utilization...

I have two identical SQL Servers... same OS... same config... when i
run my SSIS package on one server... Bandwidth utilization goes upto
20 mb... and package completes in 10 mins. Its getting data from
oracle DB. I will be migrating this package to another the other
server... there it takes about 1 hour... and bandwidth utilization is
about 2mb... why is the difference in speed of getting data? What
can be the contributor for this? I am using oracle 9i drivers for both
servers... on one its 9.2.0.0 (upto 20 mb speed) and the other one is
9.2.0.6 (2mb max). I dont think it can be the driver version. However
I cant seem to find the 9.2.0.0 to rule out this possibility.
Any help will be greatly appreciated.
Regards, zomer.
How are the NIC's configured? Is one configured at 10MB? What about the other
NIC settings?
Have you checked the event log on the machine that is getting low
utilization? Anything there?
I don't know what its called, but I know that the network guys can limit the
bandwidth someone uses. Ask your network guys and see if its been done.
Hope that helps,
Jay
"zomer" wrote:

> I have two identical SQL Servers... same OS... same config... when i
> run my SSIS package on one server... Bandwidth utilization goes upto
> 20 mb... and package completes in 10 mins. Its getting data from
> oracle DB. I will be migrating this package to another the other
> server... there it takes about 1 hour... and bandwidth utilization is
> about 2mb... why is the difference in speed of getting data? What
> can be the contributor for this? I am using oracle 9i drivers for both
> servers... on one its 9.2.0.0 (upto 20 mb speed) and the other one is
> 9.2.0.6 (2mb max). I dont think it can be the driver version. However
> I cant seem to find the 9.2.0.0 to rule out this possibility.
> Any help will be greatly appreciated.
> Regards, zomer.
>
|||Both are at 100 Full Duplex. That is the Speed of the OAM router.
That OAM router is locked on 100 full also.
Everything else is the same on both machines... except the ora driver
version.
sql

Bandwidth Utilization...

I have two identical SQL Servers... same OS... same config... when i
run my SSIS package on one server... Bandwidth utilization goes upto
20 mb... and package completes in 10 mins. Its getting data from
oracle DB. I will be migrating this package to another the other
server... there it takes about 1 hour... and bandwidth utilization is
about 2mb... why is the difference in speed of getting data? What
can be the contributor for this? I am using oracle 9i drivers for both
servers... on one its 9.2.0.0 (upto 20 mb speed) and the other one is
9.2.0.6 (2mb max). I dont think it can be the driver version. However
I cant seem to find the 9.2.0.0 to rule out this possibility.
Any help will be greatly appreciated.
Regards, zomer.How are the NIC's configured? Is one configured at 10MB? What about the other
NIC settings?
Have you checked the event log on the machine that is getting low
utilization? Anything there?
I don't know what its called, but I know that the network guys can limit the
bandwidth someone uses. Ask your network guys and see if its been done.
Hope that helps,
Jay
"zomer" wrote:
> I have two identical SQL Servers... same OS... same config... when i
> run my SSIS package on one server... Bandwidth utilization goes upto
> 20 mb... and package completes in 10 mins. Its getting data from
> oracle DB. I will be migrating this package to another the other
> server... there it takes about 1 hour... and bandwidth utilization is
> about 2mb... why is the difference in speed of getting data? What
> can be the contributor for this? I am using oracle 9i drivers for both
> servers... on one its 9.2.0.0 (upto 20 mb speed) and the other one is
> 9.2.0.6 (2mb max). I dont think it can be the driver version. However
> I cant seem to find the 9.2.0.0 to rule out this possibility.
> Any help will be greatly appreciated.
> Regards, zomer.
>|||Both are at 100 Full Duplex. That is the Speed of the OAM router.
That OAM router is locked on 100 full also.
Everything else is the same on both machines... except the ora driver
version.

Bandwidth Utilization...

I have two identical SQL Servers... same OS... same config... when i
run my SSIS package on one server... Bandwidth utilization goes upto
20 mb... and package completes in 10 mins. Its getting data from
oracle DB. I will be migrating this package to another the other
server... there it takes about 1 hour... and bandwidth utilization is
about 2mb... why is the difference in speed of getting data? What
can be the contributor for this? I am using oracle 9i drivers for both
servers... on one its 9.2.0.0 (upto 20 mb speed) and the other one is
9.2.0.6 (2mb max). I dont think it can be the driver version. However
I cant seem to find the 9.2.0.0 to rule out this possibility.
Any help will be greatly appreciated.
Regards, zomer.How are the NIC's configured? Is one configured at 10MB? What about the othe
r
NIC settings?
Have you checked the event log on the machine that is getting low
utilization? Anything there?
I don't know what its called, but I know that the network guys can limit the
bandwidth someone uses. Ask your network guys and see if its been done.
Hope that helps,
Jay
"zomer" wrote:

> I have two identical SQL Servers... same OS... same config... when i
> run my SSIS package on one server... Bandwidth utilization goes upto
> 20 mb... and package completes in 10 mins. Its getting data from
> oracle DB. I will be migrating this package to another the other
> server... there it takes about 1 hour... and bandwidth utilization is
> about 2mb... why is the difference in speed of getting data? What
> can be the contributor for this? I am using oracle 9i drivers for both
> servers... on one its 9.2.0.0 (upto 20 mb speed) and the other one is
> 9.2.0.6 (2mb max). I dont think it can be the driver version. However
> I cant seem to find the 9.2.0.0 to rule out this possibility.
> Any help will be greatly appreciated.
> Regards, zomer.
>|||Both are at 100 Full Duplex. That is the Speed of the OAM router.
That OAM router is locked on 100 full also.
Everything else is the same on both machines... except the ora driver
version.

Backups with differntial & Transactional

Hi friends, Good Morning

Hey there is a question, i have two servers where replication is implemented, The two servers is used to take backup on dailybasis, on one server we take differential backup, and on second server we take transactional backup on same time, when we restore the backups on the opposite servers (backup taken on 1st server will be restored on 2nd server and 2nd server backup will be restored on 1st server)what are contents u find difference in the dataIs that how you implemented replication? By crossing the restores?|||Take a look - it will help you to know more details about backuping for replicated databases

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replbackup_8enn.asp

Backups of Logs - Growing way, way out of control & Need Assistanc

Hello All
I should start by saying, I am not a SQL guru at all!
We have many, many SQL2005 SP1 on Win2k3 SP1 Servers, being backed up by
NetBackup 5.1 MP5 using an online SQL Agent.
I will start with the good news, in that all FULL Backups work fine! I have
discovered that the Transaction logs are NOT included in this FULL Backup.
In NetBackup there is an option to "Backup and Truncate the logs" - so I
attempted to do this, and it claims it worked fine (the Application log also
shows event id 18265 and the description gives an indication "log was backed
up Database ect and ending in "No user action is required".
Great! but here is the problem. The .ldf files are growing WAY out of
control. For example, they can grow to over 40GB in a week !
I know there is a query or a SHRINK command that can be used to help, but I
am being told that NetBackup should be "truncating" the log down. I guess
this means shrinking.
Could anyone please tell me if I am going nuts !!! Is it a case that the SQL
2005 Administrator has to manually shrink the logs or run a query to do this?
Or could something be setup wrong in SQL2005.
Any help is warmly appreciated.
Thank you
SimonConsider a log file a bucket. As modifications are performed, the bucket is filled. It is only
emptied when you BACKUP LOG, not for BACKUP DATABASE. Unless you have the database in simple
recovery mode, when you will get an error message if you do BACKUP LOG. This bucket can grow in size
by SQL Server if it becomes full and modifications are performed (autogrow).
So, one reason for large log files is that you never did backup log. You now did it, and that log
backup was probably pretty big and you should now have a lot of empty space in the log file. This
can be a valid situation for shrinking the log file. See
http://www.karaszi.com/SQLServer/info_dont_shrink.asp.
But, since you use some 3:rd party tool to do the backup, we don't know what command (like BACKUP
LOG) was submitted. I'd run a Profiler trace to see what backup command is submitted by that app.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:CEEAEBF3-D30B-476B-B248-D0A93510139C@.microsoft.com...
> Hello All
> I should start by saying, I am not a SQL guru at all!
> We have many, many SQL2005 SP1 on Win2k3 SP1 Servers, being backed up by
> NetBackup 5.1 MP5 using an online SQL Agent.
> I will start with the good news, in that all FULL Backups work fine! I have
> discovered that the Transaction logs are NOT included in this FULL Backup.
> In NetBackup there is an option to "Backup and Truncate the logs" - so I
> attempted to do this, and it claims it worked fine (the Application log also
> shows event id 18265 and the description gives an indication "log was backed
> up Database ect and ending in "No user action is required".
> Great! but here is the problem. The .ldf files are growing WAY out of
> control. For example, they can grow to over 40GB in a week !
> I know there is a query or a SHRINK command that can be used to help, but I
> am being told that NetBackup should be "truncating" the log down. I guess
> this means shrinking.
> Could anyone please tell me if I am going nuts !!! Is it a case that the SQL
> 2005 Administrator has to manually shrink the logs or run a query to do this?
> Or could something be setup wrong in SQL2005.
> Any help is warmly appreciated.
> Thank you
> Simon|||Tibor thanks
Is there a way of telling what free space is in the log file. I sort of
understand the "bucket" route now :-)
I am guessing that if the log file size was 2GB in size, it does NOT mean
that SQL would use that - so in other words, the bucket may only contain 1GB
of data. Whats the best way of finding out?
Will check the link out as well. I apprecaite that a 3rd party tool is doing
the backup, but it sounds like I may be on the right track - the only concern
I had is the log file does not shrink. but if the query I showed below is
run, then the file is reduced down in size.
Simon
"Tibor Karaszi" wrote:
> Consider a log file a bucket. As modifications are performed, the bucket is filled. It is only
> emptied when you BACKUP LOG, not for BACKUP DATABASE. Unless you have the database in simple
> recovery mode, when you will get an error message if you do BACKUP LOG. This bucket can grow in size
> by SQL Server if it becomes full and modifications are performed (autogrow).
> So, one reason for large log files is that you never did backup log. You now did it, and that log
> backup was probably pretty big and you should now have a lot of empty space in the log file. This
> can be a valid situation for shrinking the log file. See
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp.
> But, since you use some 3:rd party tool to do the backup, we don't know what command (like BACKUP
> LOG) was submitted. I'd run a Profiler trace to see what backup command is submitted by that app.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:CEEAEBF3-D30B-476B-B248-D0A93510139C@.microsoft.com...
> > Hello All
> > I should start by saying, I am not a SQL guru at all!
> > We have many, many SQL2005 SP1 on Win2k3 SP1 Servers, being backed up by
> > NetBackup 5.1 MP5 using an online SQL Agent.
> >
> > I will start with the good news, in that all FULL Backups work fine! I have
> > discovered that the Transaction logs are NOT included in this FULL Backup.
> >
> > In NetBackup there is an option to "Backup and Truncate the logs" - so I
> > attempted to do this, and it claims it worked fine (the Application log also
> > shows event id 18265 and the description gives an indication "log was backed
> > up Database ect and ending in "No user action is required".
> >
> > Great! but here is the problem. The .ldf files are growing WAY out of
> > control. For example, they can grow to over 40GB in a week !
> >
> > I know there is a query or a SHRINK command that can be used to help, but I
> > am being told that NetBackup should be "truncating" the log down. I guess
> > this means shrinking.
> >
> > Could anyone please tell me if I am going nuts !!! Is it a case that the SQL
> > 2005 Administrator has to manually shrink the logs or run a query to do this?
> >
> > Or could something be setup wrong in SQL2005.
> >
> > Any help is warmly appreciated.
> > Thank you
> > Simon
>|||Tibor thanks
Is there a way of telling what free space is in the log file. I sort of
understand the "bucket" route now :-)
I am guessing that if the log file size was 2GB in size, it does NOT mean
that SQL would use that - so in other words, the bucket may only contain 1GB
of data. Whats the best way of finding out?
Will check the link out as well. I apprecaite that a 3rd party tool is doing
the backup, but it sounds like I may be on the right track - the only concern
I had is the log file does not shrink. but if the query I showed below is
run, then the file is reduced down in size.
Simon
"Tibor Karaszi" wrote:
> Consider a log file a bucket. As modifications are performed, the bucket is filled. It is only
> emptied when you BACKUP LOG, not for BACKUP DATABASE. Unless you have the database in simple
> recovery mode, when you will get an error message if you do BACKUP LOG. This bucket can grow in size
> by SQL Server if it becomes full and modifications are performed (autogrow).
> So, one reason for large log files is that you never did backup log. You now did it, and that log
> backup was probably pretty big and you should now have a lot of empty space in the log file. This
> can be a valid situation for shrinking the log file. See
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp.
> But, since you use some 3:rd party tool to do the backup, we don't know what command (like BACKUP
> LOG) was submitted. I'd run a Profiler trace to see what backup command is submitted by that app.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:CEEAEBF3-D30B-476B-B248-D0A93510139C@.microsoft.com...
> > Hello All
> > I should start by saying, I am not a SQL guru at all!
> > We have many, many SQL2005 SP1 on Win2k3 SP1 Servers, being backed up by
> > NetBackup 5.1 MP5 using an online SQL Agent.
> >
> > I will start with the good news, in that all FULL Backups work fine! I have
> > discovered that the Transaction logs are NOT included in this FULL Backup.
> >
> > In NetBackup there is an option to "Backup and Truncate the logs" - so I
> > attempted to do this, and it claims it worked fine (the Application log also
> > shows event id 18265 and the description gives an indication "log was backed
> > up Database ect and ending in "No user action is required".
> >
> > Great! but here is the problem. The .ldf files are growing WAY out of
> > control. For example, they can grow to over 40GB in a week !
> >
> > I know there is a query or a SHRINK command that can be used to help, but I
> > am being told that NetBackup should be "truncating" the log down. I guess
> > this means shrinking.
> >
> > Could anyone please tell me if I am going nuts !!! Is it a case that the SQL
> > 2005 Administrator has to manually shrink the logs or run a query to do this?
> >
> > Or could something be setup wrong in SQL2005.
> >
> > Any help is warmly appreciated.
> > Thank you
> > Simon
>|||> Is there a way of telling what free space is in the log file.
Sure.:
DBCC SQLPERF(LOGSPACE)
> I am guessing that if the log file size was 2GB in size, it does NOT mean
> that SQL would use that - so in other words, the bucket may only contain 1GB
> of data. Whats the best way of finding out?
Correct thinking. Use above command.
So, when MS is using the term "truncating", I prefer to say "emptying". This is not the same and
shrinking the file size. Here's an elaboration on the "bucket" analogy:
http://sqlblog.com/blogs/tibor_karaszi/archive/2007/02/25/leaking-roof-and-file-shrinking.aspx
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:300F61B2-2E71-4252-AFEA-DAE45567F14F@.microsoft.com...
> Tibor thanks
> Is there a way of telling what free space is in the log file. I sort of
> understand the "bucket" route now :-)
> I am guessing that if the log file size was 2GB in size, it does NOT mean
> that SQL would use that - so in other words, the bucket may only contain 1GB
> of data. Whats the best way of finding out?
> Will check the link out as well. I apprecaite that a 3rd party tool is doing
> the backup, but it sounds like I may be on the right track - the only concern
> I had is the log file does not shrink. but if the query I showed below is
> run, then the file is reduced down in size.
> Simon
> "Tibor Karaszi" wrote:
>> Consider a log file a bucket. As modifications are performed, the bucket is filled. It is only
>> emptied when you BACKUP LOG, not for BACKUP DATABASE. Unless you have the database in simple
>> recovery mode, when you will get an error message if you do BACKUP LOG. This bucket can grow in
>> size
>> by SQL Server if it becomes full and modifications are performed (autogrow).
>> So, one reason for large log files is that you never did backup log. You now did it, and that log
>> backup was probably pretty big and you should now have a lot of empty space in the log file. This
>> can be a valid situation for shrinking the log file. See
>> http://www.karaszi.com/SQLServer/info_dont_shrink.asp.
>> But, since you use some 3:rd party tool to do the backup, we don't know what command (like BACKUP
>> LOG) was submitted. I'd run a Profiler trace to see what backup command is submitted by that app.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Simon" <Simon@.discussions.microsoft.com> wrote in message
>> news:CEEAEBF3-D30B-476B-B248-D0A93510139C@.microsoft.com...
>> > Hello All
>> > I should start by saying, I am not a SQL guru at all!
>> > We have many, many SQL2005 SP1 on Win2k3 SP1 Servers, being backed up by
>> > NetBackup 5.1 MP5 using an online SQL Agent.
>> >
>> > I will start with the good news, in that all FULL Backups work fine! I have
>> > discovered that the Transaction logs are NOT included in this FULL Backup.
>> >
>> > In NetBackup there is an option to "Backup and Truncate the logs" - so I
>> > attempted to do this, and it claims it worked fine (the Application log also
>> > shows event id 18265 and the description gives an indication "log was backed
>> > up Database ect and ending in "No user action is required".
>> >
>> > Great! but here is the problem. The .ldf files are growing WAY out of
>> > control. For example, they can grow to over 40GB in a week !
>> >
>> > I know there is a query or a SHRINK command that can be used to help, but I
>> > am being told that NetBackup should be "truncating" the log down. I guess
>> > this means shrinking.
>> >
>> > Could anyone please tell me if I am going nuts !!! Is it a case that the SQL
>> > 2005 Administrator has to manually shrink the logs or run a query to do this?
>> >
>> > Or could something be setup wrong in SQL2005.
>> >
>> > Any help is warmly appreciated.
>> > Thank you
>> > Simon
>>|||Thank you! I think I understand a bit better now!
Any recommendations on a 2005 SQL book? Microsoft one perhaps or do you have
another recommendation?
Thanks
"Tibor Karaszi" wrote:
> > Is there a way of telling what free space is in the log file.
> Sure.:
> DBCC SQLPERF(LOGSPACE)
>
> > I am guessing that if the log file size was 2GB in size, it does NOT mean
> > that SQL would use that - so in other words, the bucket may only contain 1GB
> > of data. Whats the best way of finding out?
> Correct thinking. Use above command.
> So, when MS is using the term "truncating", I prefer to say "emptying". This is not the same and
> shrinking the file size. Here's an elaboration on the "bucket" analogy:
> http://sqlblog.com/blogs/tibor_karaszi/archive/2007/02/25/leaking-roof-and-file-shrinking.aspx
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:300F61B2-2E71-4252-AFEA-DAE45567F14F@.microsoft.com...
> > Tibor thanks
> > Is there a way of telling what free space is in the log file. I sort of
> > understand the "bucket" route now :-)
> >
> > I am guessing that if the log file size was 2GB in size, it does NOT mean
> > that SQL would use that - so in other words, the bucket may only contain 1GB
> > of data. Whats the best way of finding out?
> >
> > Will check the link out as well. I apprecaite that a 3rd party tool is doing
> > the backup, but it sounds like I may be on the right track - the only concern
> > I had is the log file does not shrink. but if the query I showed below is
> > run, then the file is reduced down in size.
> >
> > Simon
> >
> > "Tibor Karaszi" wrote:
> >
> >> Consider a log file a bucket. As modifications are performed, the bucket is filled. It is only
> >> emptied when you BACKUP LOG, not for BACKUP DATABASE. Unless you have the database in simple
> >> recovery mode, when you will get an error message if you do BACKUP LOG. This bucket can grow in
> >> size
> >> by SQL Server if it becomes full and modifications are performed (autogrow).
> >>
> >> So, one reason for large log files is that you never did backup log. You now did it, and that log
> >> backup was probably pretty big and you should now have a lot of empty space in the log file. This
> >> can be a valid situation for shrinking the log file. See
> >> http://www.karaszi.com/SQLServer/info_dont_shrink.asp.
> >>
> >> But, since you use some 3:rd party tool to do the backup, we don't know what command (like BACKUP
> >> LOG) was submitted. I'd run a Profiler trace to see what backup command is submitted by that app.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> >> news:CEEAEBF3-D30B-476B-B248-D0A93510139C@.microsoft.com...
> >> > Hello All
> >> > I should start by saying, I am not a SQL guru at all!
> >> > We have many, many SQL2005 SP1 on Win2k3 SP1 Servers, being backed up by
> >> > NetBackup 5.1 MP5 using an online SQL Agent.
> >> >
> >> > I will start with the good news, in that all FULL Backups work fine! I have
> >> > discovered that the Transaction logs are NOT included in this FULL Backup.
> >> >
> >> > In NetBackup there is an option to "Backup and Truncate the logs" - so I
> >> > attempted to do this, and it claims it worked fine (the Application log also
> >> > shows event id 18265 and the description gives an indication "log was backed
> >> > up Database ect and ending in "No user action is required".
> >> >
> >> > Great! but here is the problem. The .ldf files are growing WAY out of
> >> > control. For example, they can grow to over 40GB in a week !
> >> >
> >> > I know there is a query or a SHRINK command that can be used to help, but I
> >> > am being told that NetBackup should be "truncating" the log down. I guess
> >> > this means shrinking.
> >> >
> >> > Could anyone please tell me if I am going nuts !!! Is it a case that the SQL
> >> > 2005 Administrator has to manually shrink the logs or run a query to do this?
> >> >
> >> > Or could something be setup wrong in SQL2005.
> >> >
> >> > Any help is warmly appreciated.
> >> > Thank you
> >> > Simon
> >>
> >>
>|||There are so many books out there. First think about what area you want (admin, architecture, some
specific component, programming etc), then browse at various book sites. I've always liked the
"Inside SQL Server" series from MS Press.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:26E40685-B062-4B78-BAB5-FCCCCCB5D5E8@.microsoft.com...
> Thank you! I think I understand a bit better now!
> Any recommendations on a 2005 SQL book? Microsoft one perhaps or do you have
> another recommendation?
> Thanks
> "Tibor Karaszi" wrote:
>> > Is there a way of telling what free space is in the log file.
>> Sure.:
>> DBCC SQLPERF(LOGSPACE)
>>
>> > I am guessing that if the log file size was 2GB in size, it does NOT mean
>> > that SQL would use that - so in other words, the bucket may only contain 1GB
>> > of data. Whats the best way of finding out?
>> Correct thinking. Use above command.
>> So, when MS is using the term "truncating", I prefer to say "emptying". This is not the same and
>> shrinking the file size. Here's an elaboration on the "bucket" analogy:
>> http://sqlblog.com/blogs/tibor_karaszi/archive/2007/02/25/leaking-roof-and-file-shrinking.aspx
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Simon" <Simon@.discussions.microsoft.com> wrote in message
>> news:300F61B2-2E71-4252-AFEA-DAE45567F14F@.microsoft.com...
>> > Tibor thanks
>> > Is there a way of telling what free space is in the log file. I sort of
>> > understand the "bucket" route now :-)
>> >
>> > I am guessing that if the log file size was 2GB in size, it does NOT mean
>> > that SQL would use that - so in other words, the bucket may only contain 1GB
>> > of data. Whats the best way of finding out?
>> >
>> > Will check the link out as well. I apprecaite that a 3rd party tool is doing
>> > the backup, but it sounds like I may be on the right track - the only concern
>> > I had is the log file does not shrink. but if the query I showed below is
>> > run, then the file is reduced down in size.
>> >
>> > Simon
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> Consider a log file a bucket. As modifications are performed, the bucket is filled. It is only
>> >> emptied when you BACKUP LOG, not for BACKUP DATABASE. Unless you have the database in simple
>> >> recovery mode, when you will get an error message if you do BACKUP LOG. This bucket can grow
>> >> in
>> >> size
>> >> by SQL Server if it becomes full and modifications are performed (autogrow).
>> >>
>> >> So, one reason for large log files is that you never did backup log. You now did it, and that
>> >> log
>> >> backup was probably pretty big and you should now have a lot of empty space in the log file.
>> >> This
>> >> can be a valid situation for shrinking the log file. See
>> >> http://www.karaszi.com/SQLServer/info_dont_shrink.asp.
>> >>
>> >> But, since you use some 3:rd party tool to do the backup, we don't know what command (like
>> >> BACKUP
>> >> LOG) was submitted. I'd run a Profiler trace to see what backup command is submitted by that
>> >> app.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "Simon" <Simon@.discussions.microsoft.com> wrote in message
>> >> news:CEEAEBF3-D30B-476B-B248-D0A93510139C@.microsoft.com...
>> >> > Hello All
>> >> > I should start by saying, I am not a SQL guru at all!
>> >> > We have many, many SQL2005 SP1 on Win2k3 SP1 Servers, being backed up by
>> >> > NetBackup 5.1 MP5 using an online SQL Agent.
>> >> >
>> >> > I will start with the good news, in that all FULL Backups work fine! I have
>> >> > discovered that the Transaction logs are NOT included in this FULL Backup.
>> >> >
>> >> > In NetBackup there is an option to "Backup and Truncate the logs" - so I
>> >> > attempted to do this, and it claims it worked fine (the Application log also
>> >> > shows event id 18265 and the description gives an indication "log was backed
>> >> > up Database ect and ending in "No user action is required".
>> >> >
>> >> > Great! but here is the problem. The .ldf files are growing WAY out of
>> >> > control. For example, they can grow to over 40GB in a week !
>> >> >
>> >> > I know there is a query or a SHRINK command that can be used to help, but I
>> >> > am being told that NetBackup should be "truncating" the log down. I guess
>> >> > this means shrinking.
>> >> >
>> >> > Could anyone please tell me if I am going nuts !!! Is it a case that the SQL
>> >> > 2005 Administrator has to manually shrink the logs or run a query to do this?
>> >> >
>> >> > Or could something be setup wrong in SQL2005.
>> >> >
>> >> > Any help is warmly appreciated.
>> >> > Thank you
>> >> > Simon
>> >>
>> >>

Backups Failing on Production Servers

Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being used
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
Thanks
Your message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the file
to do a backup.
ChrisR
"Cynthia" wrote:

> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and the
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being used
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30 PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>

Backups Failing on Production Servers

Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being used
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the file
to do a backup.
--
ChrisR
"Cynthia" wrote:
> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and the
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being used
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30 PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>

Backups Failing on Production Servers

Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being use
d
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge
] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the fil
e
to do a backup.
ChrisR
"Cynthia" wrote:

> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and t
he
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being u
sed
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30
PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEd
ge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>

Backups Best Practices

I have a question about using sqllitespeed.
They say it is faster doing a backup, what about restores,
I have several standby servers that I do full backups on
once in a while, so I don't have to run so many trans
logs. Does it restore fast as well?
Gary

>--Original Message--
>It looks like I have been presented with 2 options for
backing up to tape.
> 1. Use veritas SQL Agent and back up the full every
<blank> days and logs every <blank> days
> 2. Backup using native SQL agent to disk and using
veritas to backup the BAK files to tape every night.
>Anyone have an opinion on which is best and why?
>.
>Yes the restores are generally faster as well.
Andrew J. Kelly
SQL Server MVP
"Gary Abbott" <anonymous@.discussions.microsoft.com> wrote in message
news:116ba01c3f5bb$cd70b130$a101280a@.phx
.gbl...
> I have a question about using sqllitespeed.
> They say it is faster doing a backup, what about restores,
> I have several standby servers that I do full backups on
> once in a while, so I don't have to run so many trans
> logs. Does it restore fast as well?
> Gary
>
> backing up to tape.
> <blank> days and logs every <blank> days
> veritas to backup the BAK files to tape every night.

Backups

Hi All,
We have setup Transactional Replication with queued updating subscribers option. Our Servers are in Failover cluster with windows 2000 AS. We are doing Full and Transactional log backups as usual. Can any one suggest what are the recovery scenarios, in ca
se of Publisher (if it is completely down, I mean all clusters are down) and User interactions to Subscriber immediately, so that data is more than of Publisher db.
Please provide us valuable suggestions.
Thanks,
John.
I'm not exactly sure what your question is. You loose me with this statement
:
"so that data is more than of Publisher db. "
With queued Updating, your Subscriber is essentially a mirror of your
Publisher's data. If your Publisher goes offline permanently you will lose
transactions that are on your publisher and haven't made their way back to
the Subscriber.
So, its not too hard to clone your Subscriber to rebuild your Publisher. To
do this you would have to drop your subscriber, copy the subscriber schema
and data to the publisher, re run your publication scripts on your new
publisher, and do a no-sync subscription.
If your Publisher goes offline for an extended period your chance of
bringing it back on line without conflicts increases. With Queued Updating
the conflict view only lets you view conflicts, not resolve them.
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1D2A989A-5347-4E74-AAD6-707E9EC9CE70@.microsoft.com...
> Hi All,
> We have setup Transactional Replication with queued updating subscribers
option. Our Servers are in Failover cluster with windows 2000 AS. We are
doing Full and Transactional log backups as usual. Can any one suggest what
are the recovery scenarios, in case of Publisher (if it is completely down,
I mean all clusters are down) and User interactions to Subscriber
immediately, so that data is more than of Publisher db.
> Please provide us valuable suggestions.
> Thanks,
> John.
>
|||The best suggestion I have is to look in BOL for the article about the
"synch with backup" option that can be used. This will not only walk you
through these scenarios, but explain how to create coherent, multi-server
backups.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Backup/restore to different servers

Hi,
Is it possible to specify a server in a backup script & likewise specify a
restore to a different server e.g.
BACKUP DATABASE 'LIVESERVER..' + @.DBName
TO DISK = @.Path
Where LIVESERVER is the server you want to backup from?
Is this possible or must you backup & restore from the server you are in?
Many thanks for your help in advance
AntIt can only be a local database.
If you have configured a linked server, then you can use sp_executesql to execute the backup command
on the remote server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> Hi,
> Is it possible to specify a server in a backup script & likewise specify a
> restore to a different server e.g.
> BACKUP DATABASE 'LIVESERVER..' + @.DBName
> TO DISK = @.Path
> Where LIVESERVER is the server you want to backup from?
> Is this possible or must you backup & restore from the server you are in?
> Many thanks for your help in advance
> Ant|||Oh well,
Thanks very much none the less Tibor
Ant
"Tibor Karaszi" wrote:
> It can only be a local database.
> If you have configured a linked server, then you can use sp_executesql to execute the backup command
> on the remote server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Ant" <Ant@.discussions.microsoft.com> wrote in message
> news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> > Hi,
> > Is it possible to specify a server in a backup script & likewise specify a
> > restore to a different server e.g.
> >
> > BACKUP DATABASE 'LIVESERVER..' + @.DBName
> > TO DISK = @.Path
> >
> > Where LIVESERVER is the server you want to backup from?
> >
> > Is this possible or must you backup & restore from the server you are in?
> >
> > Many thanks for your help in advance
> >
> > Ant
>
>|||But you can always do it remotely from a client utility using osql or sqlcmd
and direct the backup file to a network drive. If you want to manage multiple
server instances, T-SQL may not be the best tool. A scripting language or
even a batch file would be more convenient.
Linchi
"Ant" wrote:
> Oh well,
> Thanks very much none the less Tibor
> Ant
> "Tibor Karaszi" wrote:
> > It can only be a local database.
> >
> > If you have configured a linked server, then you can use sp_executesql to execute the backup command
> > on the remote server.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://sqlblog.com/blogs/tibor_karaszi
> >
> >
> > "Ant" <Ant@.discussions.microsoft.com> wrote in message
> > news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> > > Hi,
> > > Is it possible to specify a server in a backup script & likewise specify a
> > > restore to a different server e.g.
> > >
> > > BACKUP DATABASE 'LIVESERVER..' + @.DBName
> > > TO DISK = @.Path
> > >
> > > Where LIVESERVER is the server you want to backup from?
> > >
> > > Is this possible or must you backup & restore from the server you are in?
> > >
> > > Many thanks for your help in advance
> > >
> > > Ant
> >
> >
> >|||"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> Hi,
> Is it possible to specify a server in a backup script & likewise specify a
> restore to a different server e.g.
> BACKUP DATABASE 'LIVESERVER..' + @.DBName
> TO DISK = @.Path
> Where LIVESERVER is the server you want to backup from?
> Is this possible or must you backup & restore from the server you are in?
> Many thanks for your help in advance
> Ant
You can't quite do that.
But you can do
BACKUP DATABASE FOO to DISK ='\\otherserver\backup\backup.bkf'
Assuming you have share permissions setup correctly.
You can then on otherserver do
RESTORE DATABASE FOO from DISK='c:\backup\backup.bkf'
Or variations thereof.
And if you're really fancy, you can have a backup job on one server that
when it's done with its backup fires off a job ON the other server to do a
restore.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi greg,
That's pretty much what I'm after, I created a share folder & it backusp ok
but when it tries to restore it comes up with a device offline error:
Below is the sql for it: ( I removed the .bak extension off the finlesname
but didn't seem to make a differnce)
ALTER PROC MyBackupLiveData
@.Office NVARCHAR(4),
@.SecmanDB NVARCHAR(20),
@.ERPEDB NVARCHAR(20),
@.ControlDB NVARCHAR(20),
@.CompanyDB NVARCHAR(20)
AS
DECLARE @.FilePath NVARCHAR(60)
DECLARE @.FullPath NVARCHAR(60)
DECLARE @.DatePart CHAR(8)
DECLARE @.DBName NVARCHAR(30)
-- CREATE DATE TO APPEND TO BACKUP NAME
SET@.DatePart = '_' + CONVERT(NVARCHAR, DATEPART(yyyy,GETDATE()))+
CONVERT(NVARCHAR, DATEPART(mm,GETDATE())) +
CONVERT(NVARCHAR, DATEPART(dd,GETDATE()))
-- TEMP TBL TO STORE DB NAMES TO BE BACKED UP
CREATE Table #Databases(DBName NVARCHAR(20))
-- INSERT ALL TABLES PASSED INTO PROC
INSERT #Databases VALUES (@.SecmanDB)
INSERT #Databases VALUES (@.ERPDB)
INSERT #Databases VALUES (@.ControlDB)
INSERT #Databases VALUES (@.CompanyDB)
-- CREATE CURSOR
DECLARE TablesCursor CURSOR
FOR
SELECT DBName FROM #Databases
OPEN TablesCursor
FETCH NEXT FROM TablesCursor INTO @.DBName
WHILE @.@.FETCH_STATUS = 0
BEGIN
-- SET PATH & FILENAME OF BACKUP FILE
SET @.FilePath = @.Office + '\' + @.DBName + @.DatePart + '.bak'
SET @.FullPath = 'C:\Backups\' + @.FilePath
-- PERFORM BACKUP FROM LIVE SERVER
BACKUP DATABASE @.DBName
TO DISK = @.FullPath
-- PERFORM RESTORE TO TEST SERVER
SET @.FullPath = '\\etestsql\Backups\' + @.FilePath
RESTORE DATABASE @.DBName
FROM DISK = @.FullPath
FETCH NEXT FROM TablesCursor INTO @.DBName
END
-- REMOVE ALL OBJECTS
CLOSE TablesCursor
DEALLOCATE TablesCursor
DROP TABLE #Databases
-- Thanks very much for your time on this
Ant
"Greg D. Moore (Strider)" wrote:
>
> "Ant" <Ant@.discussions.microsoft.com> wrote in message
> news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> > Hi,
> > Is it possible to specify a server in a backup script & likewise specify a
> > restore to a different server e.g.
> >
> > BACKUP DATABASE 'LIVESERVER..' + @.DBName
> > TO DISK = @.Path
> >
> > Where LIVESERVER is the server you want to backup from?
> >
> > Is this possible or must you backup & restore from the server you are in?
> >
> > Many thanks for your help in advance
> >
> > Ant
> You can't quite do that.
> But you can do
> BACKUP DATABASE FOO to DISK ='\\otherserver\backup\backup.bkf'
> Assuming you have share permissions setup correctly.
> You can then on otherserver do
> RESTORE DATABASE FOO from DISK='c:\backup\backup.bkf'
> Or variations thereof.
> And if you're really fancy, you can have a backup job on one server that
> when it's done with its backup fires off a job ON the other server to do a
> restore.
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>|||"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:06B83767-9E27-4B0A-979F-C9CB6F398EA1@.microsoft.com...
> Hi greg,
> That's pretty much what I'm after, I created a share folder & it backusp
> ok
> but when it tries to restore it comes up with a device offline error:
Make sure the box doing the restore has access to \\etestsql\Backups\.
Remember, this needs to be in the context that the SQL Server engine runs
in.
> Below is the sql for it: ( I removed the .bak extension off the finlesname
> but didn't seem to make a differnce)
> ALTER PROC MyBackupLiveData
> @.Office NVARCHAR(4),
> @.SecmanDB NVARCHAR(20),
> @.ERPEDB NVARCHAR(20),
> @.ControlDB NVARCHAR(20),
> @.CompanyDB NVARCHAR(20)
> AS
> DECLARE @.FilePath NVARCHAR(60)
> DECLARE @.FullPath NVARCHAR(60)
> DECLARE @.DatePart CHAR(8)
> DECLARE @.DBName NVARCHAR(30)
>
> -- CREATE DATE TO APPEND TO BACKUP NAME
> SET@.DatePart = '_' + CONVERT(NVARCHAR, DATEPART(yyyy,GETDATE()))+
> CONVERT(NVARCHAR, DATEPART(mm,GETDATE())) +
> CONVERT(NVARCHAR, DATEPART(dd,GETDATE()))
>
> -- TEMP TBL TO STORE DB NAMES TO BE BACKED UP
> CREATE Table #Databases(DBName NVARCHAR(20))
>
> -- INSERT ALL TABLES PASSED INTO PROC
> INSERT #Databases VALUES (@.SecmanDB)
> INSERT #Databases VALUES (@.ERPDB)
> INSERT #Databases VALUES (@.ControlDB)
> INSERT #Databases VALUES (@.CompanyDB)
>
> -- CREATE CURSOR
> DECLARE TablesCursor CURSOR
> FOR
> SELECT DBName FROM #Databases
>
> OPEN TablesCursor
> FETCH NEXT FROM TablesCursor INTO @.DBName
>
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> -- SET PATH & FILENAME OF BACKUP FILE
> SET @.FilePath = @.Office + '\' + @.DBName + @.DatePart + '.bak'
> SET @.FullPath = 'C:\Backups\' + @.FilePath
>
> -- PERFORM BACKUP FROM LIVE SERVER
> BACKUP DATABASE @.DBName
> TO DISK = @.FullPath
>
> -- PERFORM RESTORE TO TEST SERVER
> SET @.FullPath = '\\etestsql\Backups\' + @.FilePath
> RESTORE DATABASE @.DBName
> FROM DISK = @.FullPath
>
> FETCH NEXT FROM TablesCursor INTO @.DBName
> END
>
> -- REMOVE ALL OBJECTS
> CLOSE TablesCursor
> DEALLOCATE TablesCursor
> DROP TABLE #Databases
>
> -- Thanks very much for your time on this
> Ant
>
>
>
> "Greg D. Moore (Strider)" wrote:
>>
>> "Ant" <Ant@.discussions.microsoft.com> wrote in message
>> news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
>> > Hi,
>> > Is it possible to specify a server in a backup script & likewise
>> > specify a
>> > restore to a different server e.g.
>> >
>> > BACKUP DATABASE 'LIVESERVER..' + @.DBName
>> > TO DISK = @.Path
>> >
>> > Where LIVESERVER is the server you want to backup from?
>> >
>> > Is this possible or must you backup & restore from the server you are
>> > in?
>> >
>> > Many thanks for your help in advance
>> >
>> > Ant
>> You can't quite do that.
>> But you can do
>> BACKUP DATABASE FOO to DISK ='\\otherserver\backup\backup.bkf'
>> Assuming you have share permissions setup correctly.
>> You can then on otherserver do
>> RESTORE DATABASE FOO from DISK='c:\backup\backup.bkf'
>> Or variations thereof.
>> And if you're really fancy, you can have a backup job on one server that
>> when it's done with its backup fires off a job ON the other server to do
>> a
>> restore.
>>
>>
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com
>> http://www.greenms.com/sqlserver.html
>>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi Greg,
Many thanks for your help. Your answer was in fact what helped me out here.
Much Appreciated
"Greg D. Moore (Strider)" wrote:
> "Ant" <Ant@.discussions.microsoft.com> wrote in message
> news:06B83767-9E27-4B0A-979F-C9CB6F398EA1@.microsoft.com...
> > Hi Greg,
> >
> > That's pretty much what I'm after, I created a share folder & it backusp
> > ok
> > but when it tries to restore it comes up with a device offline error:
> Make sure the box doing the restore has access to \\etestsql\Backups\.
> Remember, this needs to be in the context that the SQL Server engine runs
> in.
>
>
> >
> > Below is the sql for it: ( I removed the .bak extension off the finlesname
> > but didn't seem to make a differnce)
> >
> > ALTER PROC MyBackupLiveData
> >
> > @.Office NVARCHAR(4),
> > @.SecmanDB NVARCHAR(20),
> > @.ERPEDB NVARCHAR(20),
> > @.ControlDB NVARCHAR(20),
> > @.CompanyDB NVARCHAR(20)
> >
> > AS
> >
> > DECLARE @.FilePath NVARCHAR(60)
> > DECLARE @.FullPath NVARCHAR(60)
> > DECLARE @.DatePart CHAR(8)
> > DECLARE @.DBName NVARCHAR(30)
> >
> >
> >
> > -- CREATE DATE TO APPEND TO BACKUP NAME
> > SET@.DatePart = '_' + CONVERT(NVARCHAR, DATEPART(yyyy,GETDATE()))+
> > CONVERT(NVARCHAR, DATEPART(mm,GETDATE())) +
> > CONVERT(NVARCHAR, DATEPART(dd,GETDATE()))
> >
> >
> >
> > -- TEMP TBL TO STORE DB NAMES TO BE BACKED UP
> > CREATE Table #Databases(DBName NVARCHAR(20))
> >
> >
> >
> > -- INSERT ALL TABLES PASSED INTO PROC
> > INSERT #Databases VALUES (@.SecmanDB)
> > INSERT #Databases VALUES (@.ERPDB)
> > INSERT #Databases VALUES (@.ControlDB)
> > INSERT #Databases VALUES (@.CompanyDB)
> >
> >
> > -- CREATE CURSOR
> > DECLARE TablesCursor CURSOR
> > FOR
> > SELECT DBName FROM #Databases
> >
> >
> >
> > OPEN TablesCursor
> >
> > FETCH NEXT FROM TablesCursor INTO @.DBName
> >
> >
> > WHILE @.@.FETCH_STATUS = 0
> > BEGIN
> > -- SET PATH & FILENAME OF BACKUP FILE
> > SET @.FilePath = @.Office + '\' + @.DBName + @.DatePart + '.bak'
> >
> > SET @.FullPath = 'C:\Backups\' + @.FilePath
> >
> >
> > -- PERFORM BACKUP FROM LIVE SERVER
> > BACKUP DATABASE @.DBName
> > TO DISK = @.FullPath
> >
> >
> > -- PERFORM RESTORE TO TEST SERVER
> >
> > SET @.FullPath = '\\etestsql\Backups\' + @.FilePath
> >
> > RESTORE DATABASE @.DBName
> > FROM DISK = @.FullPath
> >
> >
> > FETCH NEXT FROM TablesCursor INTO @.DBName
> > END
> >
> >
> > -- REMOVE ALL OBJECTS
> >
> > CLOSE TablesCursor
> > DEALLOCATE TablesCursor
> >
> > DROP TABLE #Databases
> >
> >
> > -- Thanks very much for your time on this
> >
> > Ant
> >
> >
> >
> >
> >
> >
> > "Greg D. Moore (Strider)" wrote:
> >
> >>
> >>
> >> "Ant" <Ant@.discussions.microsoft.com> wrote in message
> >> news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> >> > Hi,
> >> > Is it possible to specify a server in a backup script & likewise
> >> > specify a
> >> > restore to a different server e.g.
> >> >
> >> > BACKUP DATABASE 'LIVESERVER..' + @.DBName
> >> > TO DISK = @.Path
> >> >
> >> > Where LIVESERVER is the server you want to backup from?
> >> >
> >> > Is this possible or must you backup & restore from the server you are
> >> > in?
> >> >
> >> > Many thanks for your help in advance
> >> >
> >> > Ant
> >>
> >> You can't quite do that.
> >>
> >> But you can do
> >>
> >> BACKUP DATABASE FOO to DISK ='\\otherserver\backup\backup.bkf'
> >>
> >> Assuming you have share permissions setup correctly.
> >>
> >> You can then on otherserver do
> >>
> >> RESTORE DATABASE FOO from DISK='c:\backup\backup.bkf'
> >>
> >> Or variations thereof.
> >>
> >> And if you're really fancy, you can have a backup job on one server that
> >> when it's done with its backup fires off a job ON the other server to do
> >> a
> >> restore.
> >>
> >>
> >>
> >>
> >> --
> >> Greg Moore
> >> SQL Server DBA Consulting Remote and Onsite available!
> >> Email: sql (at) greenms.com
> >> http://www.greenms.com/sqlserver.html
> >>
> >>
> >>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>

Backup/restore to different servers

Hi,
Is it possible to specify a server in a backup script & likewise specify a
restore to a different server e.g.
BACKUP DATABASE 'LIVESERVER..' + @.DBName
TO DISK = @.Path
Where LIVESERVER is the server you want to backup from?
Is this possible or must you backup & restore from the server you are in?
Many thanks for your help in advance
Ant
Oh well,
Thanks very much none the less Tibor
Ant
"Tibor Karaszi" wrote:

> It can only be a local database.
> If you have configured a linked server, then you can use sp_executesql to execute the backup command
> on the remote server.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Ant" <Ant@.discussions.microsoft.com> wrote in message
> news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
>
>
|||But you can always do it remotely from a client utility using osql or sqlcmd
and direct the backup file to a network drive. If you want to manage multiple
server instances, T-SQL may not be the best tool. A scripting language or
even a batch file would be more convenient.
Linchi
"Ant" wrote:
[vbcol=seagreen]
> Oh well,
> Thanks very much none the less Tibor
> Ant
> "Tibor Karaszi" wrote:
|||"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> Hi,
> Is it possible to specify a server in a backup script & likewise specify a
> restore to a different server e.g.
> BACKUP DATABASE 'LIVESERVER..' + @.DBName
> TO DISK = @.Path
> Where LIVESERVER is the server you want to backup from?
> Is this possible or must you backup & restore from the server you are in?
> Many thanks for your help in advance
> Ant
You can't quite do that.
But you can do
BACKUP DATABASE FOO to DISK ='\\otherserver\backup\backup.bkf'
Assuming you have share permissions setup correctly.
You can then on otherserver do
RESTORE DATABASE FOO from DISK='c:\backup\backup.bkf'
Or variations thereof.
And if you're really fancy, you can have a backup job on one server that
when it's done with its backup fires off a job ON the other server to do a
restore.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hi greg,
That's pretty much what I'm after, I created a share folder & it backusp ok
but when it tries to restore it comes up with a device offline error:
Below is the sql for it: ( I removed the .bak extension off the finlesname
but didn't seem to make a differnce)
ALTER PROC MyBackupLiveData
@.Office NVARCHAR(4),
@.SecmanDB NVARCHAR(20),
@.ERPEDB NVARCHAR(20),
@.ControlDB NVARCHAR(20),
@.CompanyDB NVARCHAR(20)
AS
DECLARE @.FilePath NVARCHAR(60)
DECLARE @.FullPath NVARCHAR(60)
DECLARE @.DatePart CHAR(8)
DECLARE @.DBName NVARCHAR(30)
-- CREATE DATE TO APPEND TO BACKUP NAME
SET@.DatePart = '_' + CONVERT(NVARCHAR, DATEPART(yyyy,GETDATE()))+
CONVERT(NVARCHAR, DATEPART(mm,GETDATE())) +
CONVERT(NVARCHAR, DATEPART(dd,GETDATE()))
-- TEMP TBL TO STORE DB NAMES TO BE BACKED UP
CREATE Table #Databases(DBName NVARCHAR(20))
-- INSERT ALL TABLES PASSED INTO PROC
INSERT #Databases VALUES (@.SecmanDB)
INSERT #Databases VALUES (@.ERPDB)
INSERT #Databases VALUES (@.ControlDB)
INSERT #Databases VALUES (@.CompanyDB)
-- CREATE CURSOR
DECLARE TablesCursor CURSOR
FOR
SELECT DBName FROM #Databases
OPEN TablesCursor
FETCH NEXT FROM TablesCursor INTO @.DBName
WHILE @.@.FETCH_STATUS = 0
BEGIN
-- SET PATH & FILENAME OF BACKUP FILE
SET @.FilePath = @.Office + '\' + @.DBName + @.DatePart + '.bak'
SET @.FullPath = 'C:\Backups\' + @.FilePath
-- PERFORM BACKUP FROM LIVE SERVER
BACKUP DATABASE @.DBName
TO DISK = @.FullPath
-- PERFORM RESTORE TO TEST SERVER
SET @.FullPath = '\\etestsql\Backups\' + @.FilePath
RESTORE DATABASE @.DBName
FROM DISK = @.FullPath
FETCH NEXT FROM TablesCursor INTO @.DBName
END
-- REMOVE ALL OBJECTS
CLOSE TablesCursor
DEALLOCATE TablesCursor
DROP TABLE #Databases
-- Thanks very much for your time on this
Ant
"Greg D. Moore (Strider)" wrote:

>
> "Ant" <Ant@.discussions.microsoft.com> wrote in message
> news:F0107985-322B-40C5-91B7-E25A6EE76FA6@.microsoft.com...
> You can't quite do that.
> But you can do
> BACKUP DATABASE FOO to DISK ='\\otherserver\backup\backup.bkf'
> Assuming you have share permissions setup correctly.
> You can then on otherserver do
> RESTORE DATABASE FOO from DISK='c:\backup\backup.bkf'
> Or variations thereof.
> And if you're really fancy, you can have a backup job on one server that
> when it's done with its backup fires off a job ON the other server to do a
> restore.
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
|||"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:06B83767-9E27-4B0A-979F-C9CB6F398EA1@.microsoft.com...
> Hi greg,
> That's pretty much what I'm after, I created a share folder & it backusp
> ok
> but when it tries to restore it comes up with a device offline error:
Make sure the box doing the restore has access to \\etestsql\Backups\.
Remember, this needs to be in the context that the SQL Server engine runs
in.
[vbcol=seagreen]
> Below is the sql for it: ( I removed the .bak extension off the finlesname
> but didn't seem to make a differnce)
> ALTER PROC MyBackupLiveData
> @.Office NVARCHAR(4),
> @.SecmanDB NVARCHAR(20),
> @.ERPEDB NVARCHAR(20),
> @.ControlDB NVARCHAR(20),
> @.CompanyDB NVARCHAR(20)
> AS
> DECLARE @.FilePath NVARCHAR(60)
> DECLARE @.FullPath NVARCHAR(60)
> DECLARE @.DatePart CHAR(8)
> DECLARE @.DBName NVARCHAR(30)
>
> -- CREATE DATE TO APPEND TO BACKUP NAME
> SET@.DatePart = '_' + CONVERT(NVARCHAR, DATEPART(yyyy,GETDATE()))+
> CONVERT(NVARCHAR, DATEPART(mm,GETDATE())) +
> CONVERT(NVARCHAR, DATEPART(dd,GETDATE()))
>
> -- TEMP TBL TO STORE DB NAMES TO BE BACKED UP
> CREATE Table #Databases(DBName NVARCHAR(20))
>
> -- INSERT ALL TABLES PASSED INTO PROC
> INSERT #Databases VALUES (@.SecmanDB)
> INSERT #Databases VALUES (@.ERPDB)
> INSERT #Databases VALUES (@.ControlDB)
> INSERT #Databases VALUES (@.CompanyDB)
>
> -- CREATE CURSOR
> DECLARE TablesCursor CURSOR
> FOR
> SELECT DBName FROM #Databases
>
> OPEN TablesCursor
> FETCH NEXT FROM TablesCursor INTO @.DBName
>
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> -- SET PATH & FILENAME OF BACKUP FILE
> SET @.FilePath = @.Office + '\' + @.DBName + @.DatePart + '.bak'
> SET @.FullPath = 'C:\Backups\' + @.FilePath
>
> -- PERFORM BACKUP FROM LIVE SERVER
> BACKUP DATABASE @.DBName
> TO DISK = @.FullPath
>
> -- PERFORM RESTORE TO TEST SERVER
> SET @.FullPath = '\\etestsql\Backups\' + @.FilePath
> RESTORE DATABASE @.DBName
> FROM DISK = @.FullPath
>
> FETCH NEXT FROM TablesCursor INTO @.DBName
> END
>
> -- REMOVE ALL OBJECTS
> CLOSE TablesCursor
> DEALLOCATE TablesCursor
> DROP TABLE #Databases
>
> -- Thanks very much for your time on this
> Ant
>
>
>
> "Greg D. Moore (Strider)" wrote:
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hi Greg,
Many thanks for your help. Your answer was in fact what helped me out here.
Much Appreciated
"Greg D. Moore (Strider)" wrote:

> "Ant" <Ant@.discussions.microsoft.com> wrote in message
> news:06B83767-9E27-4B0A-979F-C9CB6F398EA1@.microsoft.com...
> Make sure the box doing the restore has access to \\etestsql\Backups\.
> Remember, this needs to be in the context that the SQL Server engine runs
> in.
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>

backup/recovery strategy

Currently we have about 60 SQL Servers all shape and size (the biggest is
payroll dbs 20gb). I would like very much to standartize backup and recovery
procedure for all servers and dbs. Pls, fellows, help with advice for
procedures, 3rd party tools, backup devices and so on...
I will be grateful if you share your experience...
Hi,
See the below URL's
http://www.microsoft.com/technet/pro...ackuprest.mspx
http://www1.us.dell.com/content/topi...555&l=en&s=biz
http://vyaskn.tripod.com/sql_server_..._practices.htm
Thanks
Hari
SQL Server MVP
"Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
news:8F912D14-F11A-4693-89D2-23B50213ED02@.microsoft.com...
> Currently we have about 60 SQL Servers all shape and size (the biggest is
> payroll dbs 20gb). I would like very much to standartize backup and
> recovery
> procedure for all servers and dbs. Pls, fellows, help with advice for
> procedures, 3rd party tools, backup devices and so on...
> I will be grateful if you share your experience...

backup/recovery strategy

Currently we have about 60 SQL Servers all shape and size (the biggest is
payroll dbs 20gb). I would like very much to standartize backup and recovery
procedure for all servers and dbs. Pls, fellows, help with advice for
procedures, 3rd party tools, backup devices and so on...
I will be grateful if you share your experience...Hi,
See the below URL's
http://www.microsoft.com/technet/pr...
555&l=en&s=biz
http://vyaskn.tripod.com/ sql_serve...ices
.htm
Thanks
Hari
SQL Server MVP
"Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
news:8F912D14-F11A-4693-89D2-23B50213ED02@.microsoft.com...
> Currently we have about 60 SQL Servers all shape and size (the biggest is
> payroll dbs 20gb). I would like very much to standartize backup and
> recovery
> procedure for all servers and dbs. Pls, fellows, help with advice for
> procedures, 3rd party tools, backup devices and so on...
> I will be grateful if you share your experience...

backup/recovery strategy

Currently we have about 60 SQL Servers all shape and size (the biggest is
payroll dbs 20gb). I would like very much to standartize backup and recovery
procedure for all servers and dbs. Pls, fellows, help with advice for
procedures, 3rd party tools, backup devices and so on...
I will be grateful if you share your experience...Hi,
See the below URL's
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlbackuprest.mspx
http://www1.us.dell.com/content/topics/global.aspx/power/en/ps4q00_martin?c=us&cs=555&l=en&s=biz
http://vyaskn.tripod.com/sql_server_administration_best_practices.htm
Thanks
Hari
SQL Server MVP
"Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
news:8F912D14-F11A-4693-89D2-23B50213ED02@.microsoft.com...
> Currently we have about 60 SQL Servers all shape and size (the biggest is
> payroll dbs 20gb). I would like very much to standartize backup and
> recovery
> procedure for all servers and dbs. Pls, fellows, help with advice for
> procedures, 3rd party tools, backup devices and so on...
> I will be grateful if you share your experience...

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