Hi,
we maintain several databases which must run in Compatibility Mode 7.0.
How can I create a non script-based Maintenance Plan for these databases
in SQL Server 2005 (DBs don't show up in the Wizard).
Regards
Axel Bender> How can I create a non script-based Maintenance Plan for these databases in SQL Server 200
5 (DBs
> don't show up in the Wizard).
Short answer: you can't. A database need to be in 2005 compat mode in order
for most (all?) maint
tasks to be available.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel_bender@.t-online.de> wrote in message news:einlo5$bsr$01$1@.news.t-online.
com...
> Hi,
> we maintain several databases which must run in Compatibility Mode 7.0. Ho
w can I create a non
> script-based Maintenance Plan for these databases in SQL Server 2005 (DBs
don't show up in the
> Wizard).
> Regards
> Axel Bender|||Tibor Karaszi wrote:
> Short answer: you can't. A database need to be in 2005 compat mode in
> order for most (all?) maint tasks to be available.
>
Thanks so far, Tibor,
is there possibly a workaround?
Remark: MPs also work with CM 80 databases.
Kind regards
Axel|||> is there possibly a workaround?
I guess that would be to up the compat level to 80 or 90, but your apps need
to support that of
course.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel.bender@.cip-kommunal.de> wrote in message
news:%23hhV%23UkAHHA.204@.TK2MSFTNGP04.phx.gbl...
> Tibor Karaszi wrote:
> Thanks so far, Tibor,
> is there possibly a workaround?
> Remark: MPs also work with CM 80 databases.
> Kind regards
> Axel|||Hi Tibor,
unfortunately this is not a solution; due to the changes MS made to the
parser in SQL 2000, we (until we're able to redesign our app) need to
run in CM 70. Is there - to your knowledge - any reason for MS not to
support MPs on SQL 2005?
Kind regards
Axel|||> Is there - to your knowledge - any reason for MS not to support MPs on SQL
2005?
I don't know. Perhaps one of the priority things that we all have to deal wi
th in out projects?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel.bender@.cip-kommunal.de> wrote in message
news:ujhfvonAHHA.4256@.TK2MSFTNGP04.phx.gbl...
> Hi Tibor,
> unfortunately this is not a solution; due to the changes MS made to the pa
rser in SQL 2000, we
> (until we're able to redesign our app) need to run in CM 70. Is there - to
your knowledge - any
> reason for MS not to support MPs on SQL 2005?
> Kind regards
> Axel
Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts
Friday, March 30, 2012
Maintenance Plan for Compatibility Mode 7.0 databases
Hi,
we maintain several databases which must run in Compatibility Mode 7.0.
How can I create a non script-based Maintenance Plan for these databases
in SQL Server 2005 (DBs don't show up in the Wizard).
Regards
Axel Bender> How can I create a non script-based Maintenance Plan for these databases in SQL Server 2005 (DBs
> don't show up in the Wizard).
Short answer: you can't. A database need to be in 2005 compat mode in order for most (all?) maint
tasks to be available.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel_bender@.t-online.de> wrote in message news:einlo5$bsr$01$1@.news.t-online.com...
> Hi,
> we maintain several databases which must run in Compatibility Mode 7.0. How can I create a non
> script-based Maintenance Plan for these databases in SQL Server 2005 (DBs don't show up in the
> Wizard).
> Regards
> Axel Bender|||Tibor Karaszi wrote:
>> How can I create a non script-based Maintenance Plan for these
>> databases in SQL Server 2005 (DBs don't show up in the Wizard).
> Short answer: you can't. A database need to be in 2005 compat mode in
> order for most (all?) maint tasks to be available.
>
Thanks so far, Tibor,
is there possibly a workaround?
Remark: MPs also work with CM 80 databases.
Kind regards
Axel|||> is there possibly a workaround?
I guess that would be to up the compat level to 80 or 90, but your apps need to support that of
course.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel.bender@.cip-kommunal.de> wrote in message
news:%23hhV%23UkAHHA.204@.TK2MSFTNGP04.phx.gbl...
> Tibor Karaszi wrote:
>> How can I create a non script-based Maintenance Plan for these databases in SQL Server 2005 (DBs
>> don't show up in the Wizard).
>> Short answer: you can't. A database need to be in 2005 compat mode in order for most (all?) maint
>> tasks to be available.
> Thanks so far, Tibor,
> is there possibly a workaround?
> Remark: MPs also work with CM 80 databases.
> Kind regards
> Axel|||Hi Tibor,
unfortunately this is not a solution; due to the changes MS made to the
parser in SQL 2000, we (until we're able to redesign our app) need to
run in CM 70. Is there - to your knowledge - any reason for MS not to
support MPs on SQL 2005?
Kind regards
Axel|||> Is there - to your knowledge - any reason for MS not to support MPs on SQL 2005?
I don't know. Perhaps one of the priority things that we all have to deal with in out projects?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel.bender@.cip-kommunal.de> wrote in message
news:ujhfvonAHHA.4256@.TK2MSFTNGP04.phx.gbl...
> Hi Tibor,
> unfortunately this is not a solution; due to the changes MS made to the parser in SQL 2000, we
> (until we're able to redesign our app) need to run in CM 70. Is there - to your knowledge - any
> reason for MS not to support MPs on SQL 2005?
> Kind regards
> Axel
we maintain several databases which must run in Compatibility Mode 7.0.
How can I create a non script-based Maintenance Plan for these databases
in SQL Server 2005 (DBs don't show up in the Wizard).
Regards
Axel Bender> How can I create a non script-based Maintenance Plan for these databases in SQL Server 2005 (DBs
> don't show up in the Wizard).
Short answer: you can't. A database need to be in 2005 compat mode in order for most (all?) maint
tasks to be available.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel_bender@.t-online.de> wrote in message news:einlo5$bsr$01$1@.news.t-online.com...
> Hi,
> we maintain several databases which must run in Compatibility Mode 7.0. How can I create a non
> script-based Maintenance Plan for these databases in SQL Server 2005 (DBs don't show up in the
> Wizard).
> Regards
> Axel Bender|||Tibor Karaszi wrote:
>> How can I create a non script-based Maintenance Plan for these
>> databases in SQL Server 2005 (DBs don't show up in the Wizard).
> Short answer: you can't. A database need to be in 2005 compat mode in
> order for most (all?) maint tasks to be available.
>
Thanks so far, Tibor,
is there possibly a workaround?
Remark: MPs also work with CM 80 databases.
Kind regards
Axel|||> is there possibly a workaround?
I guess that would be to up the compat level to 80 or 90, but your apps need to support that of
course.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel.bender@.cip-kommunal.de> wrote in message
news:%23hhV%23UkAHHA.204@.TK2MSFTNGP04.phx.gbl...
> Tibor Karaszi wrote:
>> How can I create a non script-based Maintenance Plan for these databases in SQL Server 2005 (DBs
>> don't show up in the Wizard).
>> Short answer: you can't. A database need to be in 2005 compat mode in order for most (all?) maint
>> tasks to be available.
> Thanks so far, Tibor,
> is there possibly a workaround?
> Remark: MPs also work with CM 80 databases.
> Kind regards
> Axel|||Hi Tibor,
unfortunately this is not a solution; due to the changes MS made to the
parser in SQL 2000, we (until we're able to redesign our app) need to
run in CM 70. Is there - to your knowledge - any reason for MS not to
support MPs on SQL 2005?
Kind regards
Axel|||> Is there - to your knowledge - any reason for MS not to support MPs on SQL 2005?
I don't know. Perhaps one of the priority things that we all have to deal with in out projects?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Axel Bender" <axel.bender@.cip-kommunal.de> wrote in message
news:ujhfvonAHHA.4256@.TK2MSFTNGP04.phx.gbl...
> Hi Tibor,
> unfortunately this is not a solution; due to the changes MS made to the parser in SQL 2000, we
> (until we're able to redesign our app) need to run in CM 70. Is there - to your knowledge - any
> reason for MS not to support MPs on SQL 2005?
> Kind regards
> Axel
maintenance plan for all databases
Hi,
I would like to know if its better to create ONE maintenance plan for all
databases or create a maint plan for every database.
Thanks,
Ramu
Ramu,
It depends on whether every database should have the same maintenance plan.
Don't make more plans than you need, that just adds more work for you to set
up and maintain, but don't try to cram everything into a single plan if they
should be treated differently.
I have 3 to 5 maintenance plans per server, depending on the class of
individual databases.
RLF
"Ramu" <Ramu@.discussions.microsoft.com> wrote in message
news:6B7A5A16-CC9C-4B3C-A1DC-19BFF4DD3AAF@.microsoft.com...
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
>
|||On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
Often times I like to simply separate my base maintenance plans into
one that works on the system tables, while the other works on the user
tables.
sql
I would like to know if its better to create ONE maintenance plan for all
databases or create a maint plan for every database.
Thanks,
Ramu
Ramu,
It depends on whether every database should have the same maintenance plan.
Don't make more plans than you need, that just adds more work for you to set
up and maintain, but don't try to cram everything into a single plan if they
should be treated differently.
I have 3 to 5 maintenance plans per server, depending on the class of
individual databases.
RLF
"Ramu" <Ramu@.discussions.microsoft.com> wrote in message
news:6B7A5A16-CC9C-4B3C-A1DC-19BFF4DD3AAF@.microsoft.com...
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
>
|||On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
Often times I like to simply separate my base maintenance plans into
one that works on the system tables, while the other works on the user
tables.
sql
maintenance plan for all databases
Hi,
I would like to know if its better to create ONE maintenance plan for all
databases or create a maint plan for every database.
Thanks,
RamuRamu,
It depends on whether every database should have the same maintenance plan.
Don't make more plans than you need, that just adds more work for you to set
up and maintain, but don't try to cram everything into a single plan if they
should be treated differently.
I have 3 to 5 maintenance plans per server, depending on the class of
individual databases.
RLF
"Ramu" <Ramu@.discussions.microsoft.com> wrote in message
news:6B7A5A16-CC9C-4B3C-A1DC-19BFF4DD3AAF@.microsoft.com...
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
>|||On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
Often times I like to simply separate my base maintenance plans into
one that works on the system tables, while the other works on the user
tables.|||I do a plan for production (user databases), one for system, and if
needed one for transaction logs. I like to separate them. I don't
think SQL cares but it seems neater to me.
acorcoran wrote:
> On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
>> Hi,
>> I would like to know if its better to create ONE maintenance plan for all
>> databases or create a maint plan for every database.
>> Thanks,
>> Ramu
> Often times I like to simply separate my base maintenance plans into
> one that works on the system tables, while the other works on the user
> tables.
>
I would like to know if its better to create ONE maintenance plan for all
databases or create a maint plan for every database.
Thanks,
RamuRamu,
It depends on whether every database should have the same maintenance plan.
Don't make more plans than you need, that just adds more work for you to set
up and maintain, but don't try to cram everything into a single plan if they
should be treated differently.
I have 3 to 5 maintenance plans per server, depending on the class of
individual databases.
RLF
"Ramu" <Ramu@.discussions.microsoft.com> wrote in message
news:6B7A5A16-CC9C-4B3C-A1DC-19BFF4DD3AAF@.microsoft.com...
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
>|||On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
Often times I like to simply separate my base maintenance plans into
one that works on the system tables, while the other works on the user
tables.|||I do a plan for production (user databases), one for system, and if
needed one for transaction logs. I like to separate them. I don't
think SQL cares but it seems neater to me.
acorcoran wrote:
> On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
>> Hi,
>> I would like to know if its better to create ONE maintenance plan for all
>> databases or create a maint plan for every database.
>> Thanks,
>> Ramu
> Often times I like to simply separate my base maintenance plans into
> one that works on the system tables, while the other works on the user
> tables.
>
maintenance plan for all databases
Hi,
I would like to know if its better to create ONE maintenance plan for all
databases or create a maint plan for every database.
Thanks,
RamuRamu,
It depends on whether every database should have the same maintenance plan.
Don't make more plans than you need, that just adds more work for you to set
up and maintain, but don't try to cram everything into a single plan if they
should be treated differently.
I have 3 to 5 maintenance plans per server, depending on the class of
individual databases.
RLF
"Ramu" <Ramu@.discussions.microsoft.com> wrote in message
news:6B7A5A16-CC9C-4B3C-A1DC-19BFF4DD3AAF@.microsoft.com...
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
>|||On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
Often times I like to simply separate my base maintenance plans into
one that works on the system tables, while the other works on the user
tables.|||I do a plan for production (user databases), one for system, and if
needed one for transaction logs. I like to separate them. I don't
think SQL cares but it seems neater to me.
acorcoran wrote:
> On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Often times I like to simply separate my base maintenance plans into
> one that works on the system tables, while the other works on the user
> tables.
>
I would like to know if its better to create ONE maintenance plan for all
databases or create a maint plan for every database.
Thanks,
RamuRamu,
It depends on whether every database should have the same maintenance plan.
Don't make more plans than you need, that just adds more work for you to set
up and maintain, but don't try to cram everything into a single plan if they
should be treated differently.
I have 3 to 5 maintenance plans per server, depending on the class of
individual databases.
RLF
"Ramu" <Ramu@.discussions.microsoft.com> wrote in message
news:6B7A5A16-CC9C-4B3C-A1DC-19BFF4DD3AAF@.microsoft.com...
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
>|||On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Hi,
> I would like to know if its better to create ONE maintenance plan for all
> databases or create a maint plan for every database.
> Thanks,
> Ramu
Often times I like to simply separate my base maintenance plans into
one that works on the system tables, while the other works on the user
tables.|||I do a plan for production (user databases), one for system, and if
needed one for transaction logs. I like to separate them. I don't
think SQL cares but it seems neater to me.
acorcoran wrote:
> On Aug 9, 10:46 am, Ramu <R...@.discussions.microsoft.com> wrote:
> Often times I like to simply separate my base maintenance plans into
> one that works on the system tables, while the other works on the user
> tables.
>
Maintenance Plan Failed SQL2005
I am trying to create a simple Maintenance Plan using the Wizard to
backup my databases. When I click finish everything works fine apart
from the last step, "Saving Maintenance Plan". The report I get is
this
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Success)
- Adding tasks to the maintenance plan (Success)
- Adding scheduling options (Success)
- Adding reporting options (Success)
- Saving maintenance plan "MaintenancePlan" (Error)
Messages
Saving maintenance plan failed.
ADDITIONAL INFORMATION:
Class not registered
Class not registered
I have a standard installation of SQL2005 Enterprise and have made sure
SSIS is installed and running. Any ideas on what Class is not
registered and how to fix this would be greatly appreciated.Although I haven't fixed the problem or found out which class it is
looking for I have found that this is only happening on 1 workstation.
backup my databases. When I click finish everything works fine apart
from the last step, "Saving Maintenance Plan". The report I get is
this
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Success)
- Adding tasks to the maintenance plan (Success)
- Adding scheduling options (Success)
- Adding reporting options (Success)
- Saving maintenance plan "MaintenancePlan" (Error)
Messages
Saving maintenance plan failed.
ADDITIONAL INFORMATION:
Class not registered
Class not registered
I have a standard installation of SQL2005 Enterprise and have made sure
SSIS is installed and running. Any ideas on what Class is not
registered and how to fix this would be greatly appreciated.Although I haven't fixed the problem or found out which class it is
looking for I have found that this is only happening on 1 workstation.
Maintenance Plan Failed SQL2005
I am trying to create a simple Maintenance Plan using the Wizard to
backup my databases. When I click finish everything works fine apart
from the last step, "Saving Maintenance Plan". The report I get is
this
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Success)
- Adding tasks to the maintenance plan (Success)
- Adding scheduling options (Success)
- Adding reporting options (Success)
- Saving maintenance plan "MaintenancePlan" (Error)
Messages
Saving maintenance plan failed.
ADDITIONAL INFORMATION:
Class not registered
Class not registered
I have a standard installation of SQL2005 Enterprise and have made sure
SSIS is installed and running. Any ideas on what Class is not
registered and how to fix this would be greatly appreciated.
Although I haven't fixed the problem or found out which class it is
looking for I have found that this is only happening on 1 workstation.
backup my databases. When I click finish everything works fine apart
from the last step, "Saving Maintenance Plan". The report I get is
this
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Success)
- Adding tasks to the maintenance plan (Success)
- Adding scheduling options (Success)
- Adding reporting options (Success)
- Saving maintenance plan "MaintenancePlan" (Error)
Messages
Saving maintenance plan failed.
ADDITIONAL INFORMATION:
Class not registered
Class not registered
I have a standard installation of SQL2005 Enterprise and have made sure
SSIS is installed and running. Any ideas on what Class is not
registered and how to fix this would be greatly appreciated.
Although I haven't fixed the problem or found out which class it is
looking for I have found that this is only happening on 1 workstation.
Maintenance Plan Failed SQL2005
I am trying to create a simple Maintenance Plan using the Wizard to
backup my databases. When I click finish everything works fine apart
from the last step, "Saving Maintenance Plan". The report I get is
this
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Success)
- Adding tasks to the maintenance plan (Success)
- Adding scheduling options (Success)
- Adding reporting options (Success)
- Saving maintenance plan "MaintenancePlan" (Error)
Messages
Saving maintenance plan failed.
--
ADDITIONAL INFORMATION:
Class not registered
--
Class not registered
I have a standard installation of SQL2005 Enterprise and have made sure
SSIS is installed and running. Any ideas on what Class is not
registered and how to fix this would be greatly appreciated.Although I haven't fixed the problem or found out which class it is
looking for I have found that this is only happening on 1 workstation.
backup my databases. When I click finish everything works fine apart
from the last step, "Saving Maintenance Plan". The report I get is
this
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Success)
- Adding tasks to the maintenance plan (Success)
- Adding scheduling options (Success)
- Adding reporting options (Success)
- Saving maintenance plan "MaintenancePlan" (Error)
Messages
Saving maintenance plan failed.
--
ADDITIONAL INFORMATION:
Class not registered
--
Class not registered
I have a standard installation of SQL2005 Enterprise and have made sure
SSIS is installed and running. Any ideas on what Class is not
registered and how to fix this would be greatly appreciated.Although I haven't fixed the problem or found out which class it is
looking for I have found that this is only happening on 1 workstation.
Monday, March 26, 2012
Maintenance Plan backup fails for large databases
Hi everyone,
I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
are all hosted on Windows 2000 Advanced Server. I have about 20
databases in all spread out among the 3 servers, ranging from 10MB to
100GB in size. I've had the same maintenance plans in place for at
least a year, and I'm having some trouble now.
In my maintenance plans, I do a nightly full backup of each database to
a network location. All 3 SQL servers back up to the same network
fileserver, via UNC. Until recently, everything was working fine, but
now it seems my 3 largest databases (all 10GB or larger) are showing a
failure in the maintenance plan history. The backups themselves are
completing fine, though, and I did a test restore from them to confirm
that. But the maintenance plan is returning the following errors:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
abnormally.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Obviously, because this is affecting all 3 of my SQL servers, it most
likely has something to do with the destination server. From what I
can tell, somewhere near the end of the backup of the large databases,
the destination server becomes unavailable to the SQL server. I
disabled all other services on that server (Antivirus, Tape Backup
services, etc) and did another test, but with the same results. I
installed updated NIC drivers and RAID controller drivers as well. I
can manually copy large files over the network to this location with no
problems.
Does anyone have any suggestions? I am baffled. Thank you.
george sarlas
gsarlas@.yahoo.com
A few more details I forgot to post...
All SQL Server services are running under a Windows account with full
permissions to the UNC. Also, all databases in question are set to
FULL recovery mode. We are successfully doing transaction log backups
via log shipping plans. Thanks.
george sarlas
gsarlas@.yahoo.com
|||C:\>net helpmsg 64
The specified network name is no longer available.
I have found it mostly to be one of 2 issues:
1. Network communication problems with switches/routers.
2. The destination server is not able to contact the domain controller, as
all of it's bandwidth is being used by the servers backing up to it, so it
aborts the connection.
#2 is solved by having a dedicated network over which backups are copied,
and not over the network interface that is used by SQL Clients and general
domain chatter.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<gsarlas@.yahoo.com> wrote in message
news:1123704481.634460.129430@.z14g2000cwz.googlegr oups.com...
> Hi everyone,
> I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
> are all hosted on Windows 2000 Advanced Server. I have about 20
> databases in all spread out among the 3 servers, ranging from 10MB to
> 100GB in size. I've had the same maintenance plans in place for at
> least a year, and I'm having some trouble now.
> In my maintenance plans, I do a nightly full backup of each database to
> a network location. All 3 SQL servers back up to the same network
> fileserver, via UNC. Until recently, everything was working fine, but
> now it seems my 3 largest databases (all 10GB or larger) are showing a
> failure in the maintenance plan history. The backups themselves are
> completing fine, though, and I did a test restore from them to confirm
> that. But the maintenance plan is returning the following errors:
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
> SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
> abnormally.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
> SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
> Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
> See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
>
> Obviously, because this is affecting all 3 of my SQL servers, it most
> likely has something to do with the destination server. From what I
> can tell, somewhere near the end of the backup of the large databases,
> the destination server becomes unavailable to the SQL server. I
> disabled all other services on that server (Antivirus, Tape Backup
> services, etc) and did another test, but with the same results. I
> installed updated NIC drivers and RAID controller drivers as well. I
> can manually copy large files over the network to this location with no
> problems.
> Does anyone have any suggestions? I am baffled. Thank you.
> --
> george sarlas
> gsarlas@.yahoo.com
>
sql
I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
are all hosted on Windows 2000 Advanced Server. I have about 20
databases in all spread out among the 3 servers, ranging from 10MB to
100GB in size. I've had the same maintenance plans in place for at
least a year, and I'm having some trouble now.
In my maintenance plans, I do a nightly full backup of each database to
a network location. All 3 SQL servers back up to the same network
fileserver, via UNC. Until recently, everything was working fine, but
now it seems my 3 largest databases (all 10GB or larger) are showing a
failure in the maintenance plan history. The backups themselves are
completing fine, though, and I did a test restore from them to confirm
that. But the maintenance plan is returning the following errors:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
abnormally.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Obviously, because this is affecting all 3 of my SQL servers, it most
likely has something to do with the destination server. From what I
can tell, somewhere near the end of the backup of the large databases,
the destination server becomes unavailable to the SQL server. I
disabled all other services on that server (Antivirus, Tape Backup
services, etc) and did another test, but with the same results. I
installed updated NIC drivers and RAID controller drivers as well. I
can manually copy large files over the network to this location with no
problems.
Does anyone have any suggestions? I am baffled. Thank you.
george sarlas
gsarlas@.yahoo.com
A few more details I forgot to post...
All SQL Server services are running under a Windows account with full
permissions to the UNC. Also, all databases in question are set to
FULL recovery mode. We are successfully doing transaction log backups
via log shipping plans. Thanks.
george sarlas
gsarlas@.yahoo.com
|||C:\>net helpmsg 64
The specified network name is no longer available.
I have found it mostly to be one of 2 issues:
1. Network communication problems with switches/routers.
2. The destination server is not able to contact the domain controller, as
all of it's bandwidth is being used by the servers backing up to it, so it
aborts the connection.
#2 is solved by having a dedicated network over which backups are copied,
and not over the network interface that is used by SQL Clients and general
domain chatter.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<gsarlas@.yahoo.com> wrote in message
news:1123704481.634460.129430@.z14g2000cwz.googlegr oups.com...
> Hi everyone,
> I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
> are all hosted on Windows 2000 Advanced Server. I have about 20
> databases in all spread out among the 3 servers, ranging from 10MB to
> 100GB in size. I've had the same maintenance plans in place for at
> least a year, and I'm having some trouble now.
> In my maintenance plans, I do a nightly full backup of each database to
> a network location. All 3 SQL servers back up to the same network
> fileserver, via UNC. Until recently, everything was working fine, but
> now it seems my 3 largest databases (all 10GB or larger) are showing a
> failure in the maintenance plan history. The backups themselves are
> completing fine, though, and I did a test restore from them to confirm
> that. But the maintenance plan is returning the following errors:
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
> SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
> abnormally.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
> SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
> Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
> See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
>
> Obviously, because this is affecting all 3 of my SQL servers, it most
> likely has something to do with the destination server. From what I
> can tell, somewhere near the end of the backup of the large databases,
> the destination server becomes unavailable to the SQL server. I
> disabled all other services on that server (Antivirus, Tape Backup
> services, etc) and did another test, but with the same results. I
> installed updated NIC drivers and RAID controller drivers as well. I
> can manually copy large files over the network to this location with no
> problems.
> Does anyone have any suggestions? I am baffled. Thank you.
> --
> george sarlas
> gsarlas@.yahoo.com
>
sql
Maintenance Plan backup fails for large databases
Hi everyone,
I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
are all hosted on Windows 2000 Advanced Server. I have about 20
databases in all spread out among the 3 servers, ranging from 10MB to
100GB in size. I've had the same maintenance plans in place for at
least a year, and I'm having some trouble now.
In my maintenance plans, I do a nightly full backup of each database to
a network location. All 3 SQL servers back up to the same network
fileserver, via UNC. Until recently, everything was working fine, but
now it seems my 3 largest databases (all 10GB or larger) are showing a
failure in the maintenance plan history. The backups themselves are
completing fine, though, and I did a test restore from them to confirm
that. But the maintenance plan is returning the following errors:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
abnormally.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Obviously, because this is affecting all 3 of my SQL servers, it most
likely has something to do with the destination server. From what I
can tell, somewhere near the end of the backup of the large databases,
the destination server becomes unavailable to the SQL server. I
disabled all other services on that server (Antivirus, Tape Backup
services, etc) and did another test, but with the same results. I
installed updated NIC drivers and RAID controller drivers as well. I
can manually copy large files over the network to this location with no
problems.
Does anyone have any suggestions? I am baffled. Thank you.
--
george sarlas
gsarlas@.yahoo.comA few more details I forgot to post...
All SQL Server services are running under a Windows account with full
permissions to the UNC. Also, all databases in question are set to
FULL recovery mode. We are successfully doing transaction log backups
via log shipping plans. Thanks.
--
george sarlas
gsarlas@.yahoo.com|||C:\>net helpmsg 64
The specified network name is no longer available.
I have found it mostly to be one of 2 issues:
1. Network communication problems with switches/routers.
2. The destination server is not able to contact the domain controller, as
all of it's bandwidth is being used by the servers backing up to it, so it
aborts the connection.
#2 is solved by having a dedicated network over which backups are copied,
and not over the network interface that is used by SQL Clients and general
domain chatter.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<gsarlas@.yahoo.com> wrote in message
news:1123704481.634460.129430@.z14g2000cwz.googlegroups.com...
> Hi everyone,
> I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
> are all hosted on Windows 2000 Advanced Server. I have about 20
> databases in all spread out among the 3 servers, ranging from 10MB to
> 100GB in size. I've had the same maintenance plans in place for at
> least a year, and I'm having some trouble now.
> In my maintenance plans, I do a nightly full backup of each database to
> a network location. All 3 SQL servers back up to the same network
> fileserver, via UNC. Until recently, everything was working fine, but
> now it seems my 3 largest databases (all 10GB or larger) are showing a
> failure in the maintenance plan history. The backups themselves are
> completing fine, though, and I did a test restore from them to confirm
> that. But the maintenance plan is returning the following errors:
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
> SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
> abnormally.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
> SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
> Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
> See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
>
> Obviously, because this is affecting all 3 of my SQL servers, it most
> likely has something to do with the destination server. From what I
> can tell, somewhere near the end of the backup of the large databases,
> the destination server becomes unavailable to the SQL server. I
> disabled all other services on that server (Antivirus, Tape Backup
> services, etc) and did another test, but with the same results. I
> installed updated NIC drivers and RAID controller drivers as well. I
> can manually copy large files over the network to this location with no
> problems.
> Does anyone have any suggestions? I am baffled. Thank you.
> --
> george sarlas
> gsarlas@.yahoo.com
>
I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
are all hosted on Windows 2000 Advanced Server. I have about 20
databases in all spread out among the 3 servers, ranging from 10MB to
100GB in size. I've had the same maintenance plans in place for at
least a year, and I'm having some trouble now.
In my maintenance plans, I do a nightly full backup of each database to
a network location. All 3 SQL servers back up to the same network
fileserver, via UNC. Until recently, everything was working fine, but
now it seems my 3 largest databases (all 10GB or larger) are showing a
failure in the maintenance plan history. The backups themselves are
completing fine, though, and I did a test restore from them to confirm
that. But the maintenance plan is returning the following errors:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
abnormally.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Obviously, because this is affecting all 3 of my SQL servers, it most
likely has something to do with the destination server. From what I
can tell, somewhere near the end of the backup of the large databases,
the destination server becomes unavailable to the SQL server. I
disabled all other services on that server (Antivirus, Tape Backup
services, etc) and did another test, but with the same results. I
installed updated NIC drivers and RAID controller drivers as well. I
can manually copy large files over the network to this location with no
problems.
Does anyone have any suggestions? I am baffled. Thank you.
--
george sarlas
gsarlas@.yahoo.comA few more details I forgot to post...
All SQL Server services are running under a Windows account with full
permissions to the UNC. Also, all databases in question are set to
FULL recovery mode. We are successfully doing transaction log backups
via log shipping plans. Thanks.
--
george sarlas
gsarlas@.yahoo.com|||C:\>net helpmsg 64
The specified network name is no longer available.
I have found it mostly to be one of 2 issues:
1. Network communication problems with switches/routers.
2. The destination server is not able to contact the domain controller, as
all of it's bandwidth is being used by the servers backing up to it, so it
aborts the connection.
#2 is solved by having a dedicated network over which backups are copied,
and not over the network interface that is used by SQL Clients and general
domain chatter.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<gsarlas@.yahoo.com> wrote in message
news:1123704481.634460.129430@.z14g2000cwz.googlegroups.com...
> Hi everyone,
> I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
> are all hosted on Windows 2000 Advanced Server. I have about 20
> databases in all spread out among the 3 servers, ranging from 10MB to
> 100GB in size. I've had the same maintenance plans in place for at
> least a year, and I'm having some trouble now.
> In my maintenance plans, I do a nightly full backup of each database to
> a network location. All 3 SQL servers back up to the same network
> fileserver, via UNC. Until recently, everything was working fine, but
> now it seems my 3 largest databases (all 10GB or larger) are showing a
> failure in the maintenance plan history. The backups themselves are
> completing fine, though, and I did a test restore from them to confirm
> that. But the maintenance plan is returning the following errors:
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC
> SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
> abnormally.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
> SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
> Backups\LW1SQL1\MyDatabase_db_200508090449.BAK' failed, status = 64.
> See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
>
> Obviously, because this is affecting all 3 of my SQL servers, it most
> likely has something to do with the destination server. From what I
> can tell, somewhere near the end of the backup of the large databases,
> the destination server becomes unavailable to the SQL server. I
> disabled all other services on that server (Antivirus, Tape Backup
> services, etc) and did another test, but with the same results. I
> installed updated NIC drivers and RAID controller drivers as well. I
> can manually copy large files over the network to this location with no
> problems.
> Does anyone have any suggestions? I am baffled. Thank you.
> --
> george sarlas
> gsarlas@.yahoo.com
>
Maintenance Plan backup fails for large databases
Hi everyone,
I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
are all hosted on Windows 2000 Advanced Server. I have about 20
databases in all spread out among the 3 servers, ranging from 10MB to
100GB in size. I've had the same maintenance plans in place for at
least a year, and I'm having some trouble now.
In my maintenance plans, I do a nightly full backup of each database to
a network location. All 3 SQL servers back up to the same network
fileserver, via UNC. Until recently, everything was working fine, but
now it seems my 3 largest databases (all 10GB or larger) are showing a
failure in the maintenance plan history. The backups themselves are
completing fine, though, and I did a test restore from them to confirm
that. But the maintenance plan is returning the following errors:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft]&#
91;ODBC
SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
abnormally.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft]&#
91;ODBC
SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
Backups\LW1SQL1\MyDatabase_db_2005080904
49.BAK' failed, status = 64.
See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE i
s
terminating abnormally.
Obviously, because this is affecting all 3 of my SQL servers, it most
likely has something to do with the destination server. From what I
can tell, somewhere near the end of the backup of the large databases,
the destination server becomes unavailable to the SQL server. I
disabled all other services on that server (Antivirus, Tape Backup
services, etc) and did another test, but with the same results. I
installed updated NIC drivers and RAID controller drivers as well. I
can manually copy large files over the network to this location with no
problems.
Does anyone have any suggestions? I am baffled. Thank you.
george sarlas
gsarlas@.yahoo.comA few more details I forgot to post...
All SQL Server services are running under a Windows account with full
permissions to the UNC. Also, all databases in question are set to
FULL recovery mode. We are successfully doing transaction log backups
via log shipping plans. Thanks.
george sarlas
gsarlas@.yahoo.com|||C:\>net helpmsg 64
The specified network name is no longer available.
I have found it mostly to be one of 2 issues:
1. Network communication problems with switches/routers.
2. The destination server is not able to contact the domain controller, as
all of it's bandwidth is being used by the servers backing up to it, so it
aborts the connection.
#2 is solved by having a dedicated network over which backups are copied,
and not over the network interface that is used by SQL Clients and general
domain chatter.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<gsarlas@.yahoo.com> wrote in message
news:1123704481.634460.129430@.z14g2000cwz.googlegroups.com...
> Hi everyone,
> I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
> are all hosted on Windows 2000 Advanced Server. I have about 20
> databases in all spread out among the 3 servers, ranging from 10MB to
> 100GB in size. I've had the same maintenance plans in place for at
> least a year, and I'm having some trouble now.
> In my maintenance plans, I do a nightly full backup of each database to
> a network location. All 3 SQL servers back up to the same network
> fileserver, via UNC. Until recently, everything was working fine, but
> now it seems my 3 largest databases (all 10GB or larger) are showing a
> failure in the maintenance plan history. The backups themselves are
> completing fine, though, and I did a test restore from them to confirm
> that. But the maintenance plan is returning the following errors:
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft]
[ODBC
> SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
> abnormally.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft]
[ODBC
> SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQ
L
> Backups\LW1SQL1\MyDatabase_db_2005080904
49.BAK' failed, status = 64.
> See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE
is
> terminating abnormally.
>
> Obviously, because this is affecting all 3 of my SQL servers, it most
> likely has something to do with the destination server. From what I
> can tell, somewhere near the end of the backup of the large databases,
> the destination server becomes unavailable to the SQL server. I
> disabled all other services on that server (Antivirus, Tape Backup
> services, etc) and did another test, but with the same results. I
> installed updated NIC drivers and RAID controller drivers as well. I
> can manually copy large files over the network to this location with no
> problems.
> Does anyone have any suggestions? I am baffled. Thank you.
> --
> george sarlas
> gsarlas@.yahoo.com
>
I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
are all hosted on Windows 2000 Advanced Server. I have about 20
databases in all spread out among the 3 servers, ranging from 10MB to
100GB in size. I've had the same maintenance plans in place for at
least a year, and I'm having some trouble now.
In my maintenance plans, I do a nightly full backup of each database to
a network location. All 3 SQL servers back up to the same network
fileserver, via UNC. Until recently, everything was working fine, but
now it seems my 3 largest databases (all 10GB or larger) are showing a
failure in the maintenance plan history. The backups themselves are
completing fine, though, and I did a test restore from them to confirm
that. But the maintenance plan is returning the following errors:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft]&#
91;ODBC
SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
abnormally.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft]&#
91;ODBC
SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQL
Backups\LW1SQL1\MyDatabase_db_2005080904
49.BAK' failed, status = 64.
See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE i
s
terminating abnormally.
Obviously, because this is affecting all 3 of my SQL servers, it most
likely has something to do with the destination server. From what I
can tell, somewhere near the end of the backup of the large databases,
the destination server becomes unavailable to the SQL server. I
disabled all other services on that server (Antivirus, Tape Backup
services, etc) and did another test, but with the same results. I
installed updated NIC drivers and RAID controller drivers as well. I
can manually copy large files over the network to this location with no
problems.
Does anyone have any suggestions? I am baffled. Thank you.
george sarlas
gsarlas@.yahoo.comA few more details I forgot to post...
All SQL Server services are running under a Windows account with full
permissions to the UNC. Also, all databases in question are set to
FULL recovery mode. We are successfully doing transaction log backups
via log shipping plans. Thanks.
george sarlas
gsarlas@.yahoo.com|||C:\>net helpmsg 64
The specified network name is no longer available.
I have found it mostly to be one of 2 issues:
1. Network communication problems with switches/routers.
2. The destination server is not able to contact the domain controller, as
all of it's bandwidth is being used by the servers backing up to it, so it
aborts the connection.
#2 is solved by having a dedicated network over which backups are copied,
and not over the network interface that is used by SQL Clients and general
domain chatter.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<gsarlas@.yahoo.com> wrote in message
news:1123704481.634460.129430@.z14g2000cwz.googlegroups.com...
> Hi everyone,
> I have 3 different SQL Servers, all running SQL Server 2000 SP3a. They
> are all hosted on Windows 2000 Advanced Server. I have about 20
> databases in all spread out among the 3 servers, ranging from 10MB to
> 100GB in size. I've had the same maintenance plans in place for at
> least a year, and I'm having some trouble now.
> In my maintenance plans, I do a nightly full backup of each database to
> a network location. All 3 SQL servers back up to the same network
> fileserver, via UNC. Until recently, everything was working fine, but
> now it seems my 3 largest databases (all 10GB or larger) are showing a
> failure in the maintenance plan history. The backups themselves are
> completing fine, though, and I did a test restore from them to confirm
> that. But the maintenance plan is returning the following errors:
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft]
[ODBC
> SQL Server Driver][SQL Server]BACKUP DATABASE is terminating
> abnormally.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft]
[ODBC
> SQL Server Driver][SQL Server]Write on '\\backup-server\Data-Backup\SQ
L
> Backups\LW1SQL1\MyDatabase_db_2005080904
49.BAK' failed, status = 64.
> See the SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE
is
> terminating abnormally.
>
> Obviously, because this is affecting all 3 of my SQL servers, it most
> likely has something to do with the destination server. From what I
> can tell, somewhere near the end of the backup of the large databases,
> the destination server becomes unavailable to the SQL server. I
> disabled all other services on that server (Antivirus, Tape Backup
> services, etc) and did another test, but with the same results. I
> installed updated NIC drivers and RAID controller drivers as well. I
> can manually copy large files over the network to this location with no
> problems.
> Does anyone have any suggestions? I am baffled. Thank you.
> --
> george sarlas
> gsarlas@.yahoo.com
>
maintenance plan and sub-directory
Hello there,
We have a maintenance plan to backup five user databases, we select "create
a sub-directory" and backup file to "d:\sql\backup", one of database backup
files did go to subdirectory of "d:\sql\backup", system put backup files in
"d:\sql\backup",
Anybody has idea? I appreciate your reply
Thanks very much
LionelHi
It's not clear if these are different database in the same job or different
locations for the same database!!
I would expect the location to be consistent for each database within a
given job, therefore all full backups are either in one directory or each
sub-directory and the transaction log backups are either in one directory or
one sub-directory for each database.
You may also want to check the dates and times one the files.
John
"lionel" wrote:
> Hello there,
> We have a maintenance plan to backup five user databases, we select "creat
e
> a sub-directory" and backup file to "d:\sql\backup", one of database backu
p
> files did go to subdirectory of "d:\sql\backup", system put backup files i
n
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>|||Does the folder exist for that specific db? I have seen issues where when
the MP can not get access to the specified folder it uses the next level up
instead. Another reason why I hate MP's.
Andrew J. Kelly SQL MVP
"lionel" <lionel@.discussions.microsoft.com> wrote in message
news:CFB6734A-EEC3-4707-A47E-F4F399E12746@.microsoft.com...
> Hello there,
> We have a maintenance plan to backup five user databases, we select
> "create
> a sub-directory" and backup file to "d:\sql\backup", one of database
> backup
> files did go to subdirectory of "d:\sql\backup", system put backup files
> in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>
We have a maintenance plan to backup five user databases, we select "create
a sub-directory" and backup file to "d:\sql\backup", one of database backup
files did go to subdirectory of "d:\sql\backup", system put backup files in
"d:\sql\backup",
Anybody has idea? I appreciate your reply
Thanks very much
LionelHi
It's not clear if these are different database in the same job or different
locations for the same database!!
I would expect the location to be consistent for each database within a
given job, therefore all full backups are either in one directory or each
sub-directory and the transaction log backups are either in one directory or
one sub-directory for each database.
You may also want to check the dates and times one the files.
John
"lionel" wrote:
> Hello there,
> We have a maintenance plan to backup five user databases, we select "creat
e
> a sub-directory" and backup file to "d:\sql\backup", one of database backu
p
> files did go to subdirectory of "d:\sql\backup", system put backup files i
n
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>|||Does the folder exist for that specific db? I have seen issues where when
the MP can not get access to the specified folder it uses the next level up
instead. Another reason why I hate MP's.
Andrew J. Kelly SQL MVP
"lionel" <lionel@.discussions.microsoft.com> wrote in message
news:CFB6734A-EEC3-4707-A47E-F4F399E12746@.microsoft.com...
> Hello there,
> We have a maintenance plan to backup five user databases, we select
> "create
> a sub-directory" and backup file to "d:\sql\backup", one of database
> backup
> files did go to subdirectory of "d:\sql\backup", system put backup files
> in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>
maintenance plan and sub-directory
Hello there,
We have a maintenance plan to backup five user databases, we select "create
a sub-directory" and backup file to "d:\sql\backup", one of database backup
files did go to subdirectory of "d:\sql\backup", system put backup files in
"d:\sql\backup",
Anybody has idea? I appreciate your reply
Thanks very much
Lionel
Hi
It's not clear if these are different database in the same job or different
locations for the same database!!
I would expect the location to be consistent for each database within a
given job, therefore all full backups are either in one directory or each
sub-directory and the transaction log backups are either in one directory or
one sub-directory for each database.
You may also want to check the dates and times one the files.
John
"lionel" wrote:
> Hello there,
> We have a maintenance plan to backup five user databases, we select "create
> a sub-directory" and backup file to "d:\sql\backup", one of database backup
> files did go to subdirectory of "d:\sql\backup", system put backup files in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>
|||Does the folder exist for that specific db? I have seen issues where when
the MP can not get access to the specified folder it uses the next level up
instead. Another reason why I hate MP's.
Andrew J. Kelly SQL MVP
"lionel" <lionel@.discussions.microsoft.com> wrote in message
news:CFB6734A-EEC3-4707-A47E-F4F399E12746@.microsoft.com...
> Hello there,
> We have a maintenance plan to backup five user databases, we select
> "create
> a sub-directory" and backup file to "d:\sql\backup", one of database
> backup
> files did go to subdirectory of "d:\sql\backup", system put backup files
> in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>
We have a maintenance plan to backup five user databases, we select "create
a sub-directory" and backup file to "d:\sql\backup", one of database backup
files did go to subdirectory of "d:\sql\backup", system put backup files in
"d:\sql\backup",
Anybody has idea? I appreciate your reply
Thanks very much
Lionel
Hi
It's not clear if these are different database in the same job or different
locations for the same database!!
I would expect the location to be consistent for each database within a
given job, therefore all full backups are either in one directory or each
sub-directory and the transaction log backups are either in one directory or
one sub-directory for each database.
You may also want to check the dates and times one the files.
John
"lionel" wrote:
> Hello there,
> We have a maintenance plan to backup five user databases, we select "create
> a sub-directory" and backup file to "d:\sql\backup", one of database backup
> files did go to subdirectory of "d:\sql\backup", system put backup files in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>
|||Does the folder exist for that specific db? I have seen issues where when
the MP can not get access to the specified folder it uses the next level up
instead. Another reason why I hate MP's.
Andrew J. Kelly SQL MVP
"lionel" <lionel@.discussions.microsoft.com> wrote in message
news:CFB6734A-EEC3-4707-A47E-F4F399E12746@.microsoft.com...
> Hello there,
> We have a maintenance plan to backup five user databases, we select
> "create
> a sub-directory" and backup file to "d:\sql\backup", one of database
> backup
> files did go to subdirectory of "d:\sql\backup", system put backup files
> in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>
maintenance plan and sub-directory
Hello there,
We have a maintenance plan to backup five user databases, we select "create
a sub-directory" and backup file to "d:\sql\backup", one of database backup
files did go to subdirectory of "d:\sql\backup", system put backup files in
"d:\sql\backup",
Anybody has idea? I appreciate your reply
Thanks very much
LionelHi
It's not clear if these are different database in the same job or different
locations for the same database!!
I would expect the location to be consistent for each database within a
given job, therefore all full backups are either in one directory or each
sub-directory and the transaction log backups are either in one directory or
one sub-directory for each database.
You may also want to check the dates and times one the files.
John
"lionel" wrote:
> Hello there,
> We have a maintenance plan to backup five user databases, we select "create
> a sub-directory" and backup file to "d:\sql\backup", one of database backup
> files did go to subdirectory of "d:\sql\backup", system put backup files in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>|||Does the folder exist for that specific db? I have seen issues where when
the MP can not get access to the specified folder it uses the next level up
instead. Another reason why I hate MP's.
--
Andrew J. Kelly SQL MVP
"lionel" <lionel@.discussions.microsoft.com> wrote in message
news:CFB6734A-EEC3-4707-A47E-F4F399E12746@.microsoft.com...
> Hello there,
> We have a maintenance plan to backup five user databases, we select
> "create
> a sub-directory" and backup file to "d:\sql\backup", one of database
> backup
> files did go to subdirectory of "d:\sql\backup", system put backup files
> in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>sql
We have a maintenance plan to backup five user databases, we select "create
a sub-directory" and backup file to "d:\sql\backup", one of database backup
files did go to subdirectory of "d:\sql\backup", system put backup files in
"d:\sql\backup",
Anybody has idea? I appreciate your reply
Thanks very much
LionelHi
It's not clear if these are different database in the same job or different
locations for the same database!!
I would expect the location to be consistent for each database within a
given job, therefore all full backups are either in one directory or each
sub-directory and the transaction log backups are either in one directory or
one sub-directory for each database.
You may also want to check the dates and times one the files.
John
"lionel" wrote:
> Hello there,
> We have a maintenance plan to backup five user databases, we select "create
> a sub-directory" and backup file to "d:\sql\backup", one of database backup
> files did go to subdirectory of "d:\sql\backup", system put backup files in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>|||Does the folder exist for that specific db? I have seen issues where when
the MP can not get access to the specified folder it uses the next level up
instead. Another reason why I hate MP's.
--
Andrew J. Kelly SQL MVP
"lionel" <lionel@.discussions.microsoft.com> wrote in message
news:CFB6734A-EEC3-4707-A47E-F4F399E12746@.microsoft.com...
> Hello there,
> We have a maintenance plan to backup five user databases, we select
> "create
> a sub-directory" and backup file to "d:\sql\backup", one of database
> backup
> files did go to subdirectory of "d:\sql\backup", system put backup files
> in
> "d:\sql\backup",
> Anybody has idea? I appreciate your reply
> Thanks very much
> Lionel
>sql
Maintenance Plan 2005 invalid argument
trying to create an mp and i can't get past this failure (regardless of
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!
can you list the repro steps here.
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegr oups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>
sql
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!
can you list the repro steps here.
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegr oups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>
sql
Maintenance Plan 2005 invalid argument
trying to create an mp and i can't get past this failure (regardless of
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!can you list the repro steps here.
--
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegroups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!can you list the repro steps here.
--
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegroups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>
Maintenance Plan 2005 invalid argument
trying to create an mp and i can't get past this failure (regardless of
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!can you list the repro steps here.
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegroups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!can you list the repro steps here.
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegroups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>
Friday, March 23, 2012
Maintenance Plan
Good morning,
I have created a Maintenance Plan with four subplans. The databases are
backed up to disk and each subplan, I have set up the BackUp Set to
expire: After (in days) 3. However, when I go to the disk, I noticed
that all the backups are still there since I set up the maintenance plan
(which was last week). I would have expected to see some of Sep 24, Sep
25, Sep 26, some of Sep 27. Please advise.
Thanks,
Audrey
*** Sent via Developersdex http://www.developersdex.com ***Hello Audrey,
"Expire" does not mean "delete old files". It specifies when the backup set
for this backup can be overwritten.
If you want to delete old backup files using Maintenance Plan, then use
"Maintenance Cleanup Task"
Ekrem Önsoy
"Audrey Ng" <odd26uk@.yahoo.co.uk> wrote in message
news:%23H4J2eRAIHA.320@.TK2MSFTNGP04.phx.gbl...
> Good morning,
> I have created a Maintenance Plan with four subplans. The databases are
> backed up to disk and each subplan, I have set up the BackUp Set to
> expire: After (in days) 3. However, when I go to the disk, I noticed
> that all the backups are still there since I set up the maintenance plan
> (which was last week). I would have expected to see some of Sep 24, Sep
> 25, Sep 26, some of Sep 27. Please advise.
> Thanks,
> Audrey
>
> *** Sent via Developersdex http://www.developersdex.com ***sql
I have created a Maintenance Plan with four subplans. The databases are
backed up to disk and each subplan, I have set up the BackUp Set to
expire: After (in days) 3. However, when I go to the disk, I noticed
that all the backups are still there since I set up the maintenance plan
(which was last week). I would have expected to see some of Sep 24, Sep
25, Sep 26, some of Sep 27. Please advise.
Thanks,
Audrey
*** Sent via Developersdex http://www.developersdex.com ***Hello Audrey,
"Expire" does not mean "delete old files". It specifies when the backup set
for this backup can be overwritten.
If you want to delete old backup files using Maintenance Plan, then use
"Maintenance Cleanup Task"
Ekrem Önsoy
"Audrey Ng" <odd26uk@.yahoo.co.uk> wrote in message
news:%23H4J2eRAIHA.320@.TK2MSFTNGP04.phx.gbl...
> Good morning,
> I have created a Maintenance Plan with four subplans. The databases are
> backed up to disk and each subplan, I have set up the BackUp Set to
> expire: After (in days) 3. However, when I go to the disk, I noticed
> that all the backups are still there since I set up the maintenance plan
> (which was last week). I would have expected to see some of Sep 24, Sep
> 25, Sep 26, some of Sep 27. Please advise.
> Thanks,
> Audrey
>
> *** Sent via Developersdex http://www.developersdex.com ***sql
Maintenance Plan
I'm running an SBS2000 server with SQL serving up about 20 small databases.
I have a maintenance plan in place that runs every night backing up each of
the databases to a folder which in turn gets backed up by tape two hours
later. I have the plan configured to delete transaction logs and database
files older than 2 days. The backups are running fine, but the plan is not
deleting the old backup files and transaction logs.I have had that issue in the past and found that the
backups don't always complete at the same time. If you
setup a maintenance plan to remove backups older than 1
day and you do the following;
You had the 1st backup run and complete at 12:04.
The next day, the backup is a little quicker and finished
at 12:03. The backup from the previous day won't be
deleted as a FULL 24 hours haven't passed. I modified my
setting to delete after 23 hours.
Hope this helps.
Thanks
Fred
>--Original Message--
>I'm running an SBS2000 server with SQL serving up about
20 small databases.
>I have a maintenance plan in place that runs every night
backing up each of
>the databases to a folder which in turn gets backed up by
tape two hours
>later. I have the plan configured to delete transaction
logs and database
>files older than 2 days. The backups are running fine,
but the plan is not
>deleting the old backup files and transaction logs.
>.
>|||Could be that you have included databases for log backup that are in simple
recovery mode.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"RScott" <anonymous@.discussions.microsoft.com> wrote in message
news:0E5C4CEC-1C97-4ADB-8D5E-97F549E0C495@.microsoft.com...
> I'm running an SBS2000 server with SQL serving up about 20 small
databases.
> I have a maintenance plan in place that runs every night backing up each
of
> the databases to a folder which in turn gets backed up by tape two hours
> later. I have the plan configured to delete transaction logs and database
> files older than 2 days. The backups are running fine, but the plan is
not
> deleting the old backup files and transaction logs.sql
I have a maintenance plan in place that runs every night backing up each of
the databases to a folder which in turn gets backed up by tape two hours
later. I have the plan configured to delete transaction logs and database
files older than 2 days. The backups are running fine, but the plan is not
deleting the old backup files and transaction logs.I have had that issue in the past and found that the
backups don't always complete at the same time. If you
setup a maintenance plan to remove backups older than 1
day and you do the following;
You had the 1st backup run and complete at 12:04.
The next day, the backup is a little quicker and finished
at 12:03. The backup from the previous day won't be
deleted as a FULL 24 hours haven't passed. I modified my
setting to delete after 23 hours.
Hope this helps.
Thanks
Fred
>--Original Message--
>I'm running an SBS2000 server with SQL serving up about
20 small databases.
>I have a maintenance plan in place that runs every night
backing up each of
>the databases to a folder which in turn gets backed up by
tape two hours
>later. I have the plan configured to delete transaction
logs and database
>files older than 2 days. The backups are running fine,
but the plan is not
>deleting the old backup files and transaction logs.
>.
>|||Could be that you have included databases for log backup that are in simple
recovery mode.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"RScott" <anonymous@.discussions.microsoft.com> wrote in message
news:0E5C4CEC-1C97-4ADB-8D5E-97F549E0C495@.microsoft.com...
> I'm running an SBS2000 server with SQL serving up about 20 small
databases.
> I have a maintenance plan in place that runs every night backing up each
of
> the databases to a folder which in turn gets backed up by tape two hours
> later. I have the plan configured to delete transaction logs and database
> files older than 2 days. The backups are running fine, but the plan is
not
> deleting the old backup files and transaction logs.sql
Maintenance Job not working properly
Hi,
I an new to the forum.
I am having some problems where my maintenance job is not backing up the user databases in SQL2000. Unfortunately, I found out the hard way as my payroll in GP did not run properly and I had to do a restore from the BAK file.
I am receiving the following error msg in the event log
Status: Failed - Invoked on: 2006-04-11 22:00:02 - Message: The job failed. The owner () of job DB Backup Job for DB Maintenance Plan 'Daily Backup of User Databases' does not have server access.
I cannot find where and how the user permission was chmaged on this job. I would like some assistance with this problem.
thanks
Raymond
Hi,
Go to Jobs list under SQL Server Agent in the Enterprise Manager.
Find the job for the maintenance plan you have created. Name of the job will include the name of the maintenance plan.
If you open the job properties screen and activate the Steps tab. You will see the "run as user" in the advanced tab of the edit job steps screen.
Check this user for necessary credentials.
Also control the owner of the job in the main job properties screen.
Eralper
Subscribe to:
Posts (Atom)