Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts

Tuesday, March 27, 2012

BACKUP failed to complete the command sp_prepexec;1

One of my SQL Servers (SQL 2000 SP4) is reporting this error in the Maintenance Plan. But shortly after it shows this error is does successfully backup my Databases (per log history), however the plan is indicating "failure".

I have no idea how to resolve this nor why it is happening.

Rob.

Hi,

it seems, that an t-sql statement is blocking.

Use the profiler and filter by object name = sp_prepexec and SPID.

actual in the KB:

HOW TO: Troubleshoot Application Performance Issues

How to monitor SQL Server 2000 blocking

tosc

BACKUP failed to complete the command sp_prepexec;1

One of my SQL Servers (SQL 2000 SP4) is reporting this error in the Maintenance Plan. But shortly after it shows this error is does successfully backup my Databases (per log history), however the plan is indicating "failure".

I have no idea how to resolve this nor why it is happening.

Rob.

Hi,

it seems, that an t-sql statement is blocking.

Use the profiler and filter by object name = sp_prepexec and SPID.

actual in the KB:

HOW TO: Troubleshoot Application Performance Issues

How to monitor SQL Server 2000 blocking

tosc

Sunday, March 25, 2012

Backup Exec and MDAC update

I have a client in a Windows 2000 SP4 network environment
that is using Backup Exec 9.0 with a remote agent for
Exchange and a remote server. They ran the Windows
Updates last Friday and now they are receiving errors on
their backup job when it tries to back up the server that
they updated. The event id in the event viewer is 34323
and reads as follows:
Update to catalog file Catalog index database failed.
Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]
Violation of PRIMARY KEY
constraint 'PK_CatMedia_68487DD7'. Cannot insert dupl
cat_RecordSet:Reopen[]
d:\be\tybee\4367r\becat\server\dll\catme
dia.cpp[753]
I also get the following event id 34338 in conjunction
with the above error:
Backup Exec Alert: Catalog Error
[Server:"servername"]ODBC access error. Possible lost
connection to database or unsuccessful access to catalog
index in the database.
I have submitted this to Veritas forum as well but if
anyone has any ideas, I would appreciate it. The Windows
Update apparently applied KB832483 which is an MDAC
update. I don't see where I can roll this back either.
Thanks. DeannaDeanna,
did you ever figure out a solution to this problem? i'm experiencing
the same thing in the same type of environment.
thank you,
Lenny.
Deanna wrote:
> *I have a client in a Windows 2000 SP4 network environment
> that is using Backup Exec 9.0 with a remote agent for
> Exchange and a remote server. They ran the Windows
> Updates last Friday and now they are receiving errors on
> their backup job when it tries to back up the server that
> they updated. The event id in the event viewer is 34323
> and reads as follows:
> Update to catalog file Catalog index database failed.
> Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]
> Violation of PRIMARY KEY
> constraint 'PK_CatMedia_68487DD7'. Cannot insert dupl
> cat_RecordSet:Reopen[]
> d:\be\tybee\4367r\becat\server\dll\catme
dia.cpp[753]
> I also get the following event id 34338 in conjunction
> with the above error:
> Backup Exec Alert: Catalog Error
> [Server:"servername"]ODBC access error. Possible lost
> connection to database or unsuccessful access to catalog
> index in the database.
> I have submitted this to Veritas forum as well but if
> anyone has any ideas, I would appreciate it. The Windows
> Update apparently applied KB832483 which is an MDAC
> update. I don't see where I can roll this back either.
> Thanks. Deanna *
lennyi
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message422513.html

backup error - single user mode needed?

Hi Everyone,
One of my clients is running SQL 2000 SP4 and the Data Maintenance Plan
logs shows a log with...
Database master: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC
SQL Server Driver][SQL Server]Repair statement not processed. Database
needs to be in single user mode.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
processed. Database needs to be in single user mode.
** Execution Time: 0 hrs, 0 mins, 1 secs **
...
[5] Database master: Database Backup...
The backup was not performed since data verification errors were found.

There are similar messages for databases model and msdb.
Questions:
- should master, model and msdb be included in the daily backup?
- how does one get into single user mode and repair this?
Thanks
Richard
Hi,
In your maintenance plan, uncheck the Attempt to repair minor problems
checkbox in Integrity tab.
With that checkbox unchecked, integrity checks will be still done on the
databases and as a good practice verify your maintenance logs
for any integroty errors. If there is any error you could manually correct
it.
Thanks
Hari
SQL Server MVP
"Richard Fagen" <no_spam@.aol.com> wrote in message
news:O3JolEukFHA.2792@.TK2MSFTNGP10.phx.gbl...
> Hi Everyone,
> One of my clients is running SQL 2000 SP4 and the Data Maintenance Plan
> logs shows a log with...
> --
> Database master: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC
> SQL Server Driver][SQL Server]Repair statement not processed. Database
> needs to be in single user mode.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
> processed. Database needs to be in single user mode.
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> ...
> [5] Database master: Database Backup...
> The backup was not performed since data verification errors were
> found.
>
> --
> There are similar messages for databases model and msdb.
> Questions:
> - should master, model and msdb be included in the daily backup?
> - how does one get into single user mode and repair this?
> Thanks
> Richard
|||hi Richard,
Richard Fagen wrote:
is the disk damaged?

> Questions:
> - should master, model and msdb be included in the daily backup?
usually not.. only when server modifications occur, like implementing new
jobs, alerts, logins and so on...

> - how does one get into single user mode and repair this?
http://msdn.microsoft.com/library/de...start_4nhh.asp
http://msdn.microsoft.com/library/de...kprst_4g4w.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea Montanari wrote:
> hi Richard,
> Richard Fagen wrote:
> is the disk damaged?
always forget the Maintenance Plan is that intrusive (and bugged ) ..
always prefer self written jobs :D
yep.. Hari is right
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Hari,
I'll uncheck the box and try it again.
I use SQL as part of SBS 2000/2003 and that seems to go against what
I've read in books. All the books say be sure to check that box
However, since your both SQL MVPs and Andrea has helped me out before,
I'll go with your recommendations.
Richard
p.s. the one who says to check it, Harry Brelsford, is an MVP too, but
of SBS not SQL
Hari Prasad wrote:
> Hi,
> In your maintenance plan, uncheck the Attempt to repair minor problems
> checkbox in Integrity tab.
> With that checkbox unchecked, integrity checks will be still done on the
> databases and as a good practice verify your maintenance logs
> for any integroty errors. If there is any error you could manually correct
> it.
> Thanks
> Hari
> SQL Server MVP
>
> "Richard Fagen" <no_spam@.aol.com> wrote in message
> news:O3JolEukFHA.2792@.TK2MSFTNGP10.phx.gbl...
>
>
|||Hi Andrea,

> is the disk damaged?
Not that I know of. Besides, I remotely logged into a few SBS clients
to test the data maintenance plan with backing up master, model and msdb
and they all had the same error messages.
I guess it wouldn't hurt to have everyone run a scandisk (I try to get
them to do it on their own, but they never remember) and doublecheck.

> usually not.. only when server modifications occur, like implementing new
> jobs, alerts, logins and so on...
I can manually backup master, model and msdb via the Enterprise Manager,
just not via the maintenance plan.
I hope they fix this in SQL 2005

> http://msdn.microsoft.com/library/de...start_4nhh.asp
> http://msdn.microsoft.com/library/de...kprst_4g4w.asp
Thanks for the links
Richard
|||hi Richard,
Richard Fagen wrote:
> Hi Andrea,
> Not that I know of. Besides, I remotely logged into a few SBS clients
> to test the data maintenance plan with backing up master, model and
> msdb and they all had the same error messages.
see Hari post... Maintenance Plan is "intrusive" by default and tryes to
perform activities requiring single user access...

> I guess it wouldn't hurt to have everyone run a scandisk (I try to get
> them to do it on their own, but they never remember) and doublecheck.
but ok. checking disk integrity is always neat :D

> I can manually backup master, model and msdb via the Enterprise
> Manager, just not via the maintenance plan.
again, see Hari answer...

> I hope they fix this in SQL 2005
SQLExpress will not include the Agent, so no Maintenance Plan at all... but
worse, no jobs at all, and that includes both admin/house keeping jobs as
other dataload,dml jobs
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||From Microsoft Article 290622:
BUG: Databse Manintenance Plan on System Databases faile on Intergrity
Check if "Attempt to repair minor problems" is Selected
... The database maintenance plan attempts to place the system databases
in the single user mode in order to execute CkDBRepair. However the
Master and MSDB databases cannot be placed in single user mode because of
constantly running system processes like LAZYWRITER, LOG WRITER, SQL
Agent... The repair step fails to run and the job reports a failure...
There is no fix for tis bug as yet. The workaround is to disable the
"Attempt to repair any minor problems" option in your maintenance plan.
Lyle
In article <O3JolEukFHA.2792@.TK2MSFTNGP10.phx.gbl>, no_spam@.aol.com
says...
> Hi Everyone,
> One of my clients is running SQL 2000 SP4 and the Data Maintenance Plan
> logs shows a log with...
> --
> Database master: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC
> SQL Server Driver][SQL Server]Repair statement not processed. Database
> needs to be in single user mode.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
> processed. Database needs to be in single user mode.
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> ...
> [5] Database master: Database Backup...
> The backup was not performed since data verification errors were found.
>
> --
> There are similar messages for databases model and msdb.
> Questions:
> - should master, model and msdb be included in the daily backup?
> - how does one get into single user mode and repair this?
> Thanks
> Richard
>
|||Hi Lyle,
Thanks for the article. Finally, a great explanation
Richard
Lyle wrote:

> From Microsoft Article 290622:
> BUG: Databse Manintenance Plan on System Databases faile on Intergrity
> Check if "Attempt to repair minor problems" is Selected
> ... The database maintenance plan attempts to place the system databases
> in the single user mode in order to execute CkDBRepair. However the
> Master and MSDB databases cannot be placed in single user mode because of
> constantly running system processes like LAZYWRITER, LOG WRITER, SQL
> Agent... The repair step fails to run and the job reports a failure...
> There is no fix for tis bug as yet. The workaround is to disable the
> "Attempt to repair any minor problems" option in your maintenance plan.
> Lyle
sql

Monday, March 19, 2012

Backup Databases

I am running SQL2000 SP4 on a Win2000 server and getting following error when
trying to perform a backup of a database within Enterprise Manager.
"Error 22272: Cannot load the DLL xpstart.dll, or one of the DLL's it
references. Reason 127(The specified procedure could not be found.). I have
looked any references to this error message, but yet to find anything on it.
Wondering if someone can assist me.
thanks,
JayHi
If backing up the datrabase from a different PC works, then I would think
re-installing the client tools may help solve this.
John
"Jay" wrote:
> I am running SQL2000 SP4 on a Win2000 server and getting following error when
> trying to perform a backup of a database within Enterprise Manager.
> "Error 22272: Cannot load the DLL xpstart.dll, or one of the DLL's it
> references. Reason 127(The specified procedure could not be found.). I have
> looked any references to this error message, but yet to find anything on it.
> Wondering if someone can assist me.
> thanks,
> Jay
>|||Jay wrote:
> I am running SQL2000 SP4 on a Win2000 server and getting following error when
> trying to perform a backup of a database within Enterprise Manager.
> "Error 22272: Cannot load the DLL xpstart.dll, or one of the DLL's it
> references. Reason 127(The specified procedure could not be found.). I have
> looked any references to this error message, but yet to find anything on it.
> Wondering if someone can assist me.
> thanks,
> Jay
>
Open up Query Analyzer and use the T-SQL BACKUP command - does it work?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Backup Databases

I am running SQL2000 SP4 on a Win2000 server and getting following error whe
n
trying to perform a backup of a database within Enterprise Manager.
"Error 22272: Cannot load the DLL xpstart.dll, or one of the DLL's it
references. Reason 127(The specified procedure could not be found.). I have
looked any references to this error message, but yet to find anything on it.
Wondering if someone can assist me.
thanks,
JayHi
If backing up the datrabase from a different PC works, then I would think
re-installing the client tools may help solve this.
John
"Jay" wrote:

> I am running SQL2000 SP4 on a Win2000 server and getting following error w
hen
> trying to perform a backup of a database within Enterprise Manager.
> "Error 22272: Cannot load the DLL xpstart.dll, or one of the DLL's it
> references. Reason 127(The specified procedure could not be found.). I ha
ve
> looked any references to this error message, but yet to find anything on i
t.
> Wondering if someone can assist me.
> thanks,
> Jay
>|||Jay wrote:
> I am running SQL2000 SP4 on a Win2000 server and getting following error w
hen
> trying to perform a backup of a database within Enterprise Manager.
> "Error 22272: Cannot load the DLL xpstart.dll, or one of the DLL's it
> references. Reason 127(The specified procedure could not be found.). I ha
ve
> looked any references to this error message, but yet to find anything on i
t.
> Wondering if someone can assist me.
> thanks,
> Jay
>
Open up Query Analyzer and use the T-SQL BACKUP command - does it work?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Saturday, February 25, 2012

Backup and Restore Anomaly

SQL Server 2000 SP4 build 2187
Not sure what is happening with SQL Server backup Internals, I am hoping you
can answer.
A scheduled job backups up database named "Wells" to a device which points
to a physical file as step 1. Same schedule job, step 2, then restores to
database WELLSCopy. The WELLSCopy database has always existed. This has been
working for a very long time. Now, its generating the following error.
Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
Database' :
Began Executing 2006-10-19 00:59:34
Msg 3141, Sev 16: The database to be restored was named 'Wells'.
Reissue the statement using the WITH REPLACE option to overwrite the
'WELLScopy'
database. [SQLSTATE 42000]
Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE
42000]
Here is the backup command and restore command.
BACKUP DATABASE [Wells] TO Dbackup_WELLS
WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
restore database CHARITYDBCOPY
from dbackup_charitydb
with
move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
I tried to duplicate this issue in our test environment and it restored
successfully every time. I did manage to break it by creating a new database
with a totally different name then try to restore over it and received the
error message.
BOL says it performs a safety check if the REPLACE options is not used. If
so, why has the restore work for a very long time and now decide to break.
Also, why is it allowing me to restore successfully in test without using th
e
REPLACE option.
I am so confused...
BOL...
When the REPLACE option is not specified, a safety check occurs (which
prevents overwriting a different database by accident). The safety check
ensures that the RESTORE DATABASE statement will not restore the database to
the current server if:
The database named in the RESTORE statement already exists on the current
server, and
The database name is different from the database name recorded in the backup
set.I applogize, I pasted my test restore code. Here is the correct version
RESTORE DATABASE WELLScopy
FROM Dbackup_wells
with
MOVE 'Wells_Data' TO 'e:\data\mssql\data\WELLScopy_Data.MDF',
MOVE 'WELLS_Log' TO 'e:\data\mssql\data\WELLScopy_Log.LDF'
go
"FredG" wrote:

> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping y
ou
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has be
en
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTAT
E 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new databa
se
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using
the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database
to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the back
up
> set.
>|||A guess is that the source database has grown, so the backup need say 10GB f
or one of the database
files, but the existing database file only has, say, 8GB for that file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping y
ou
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has be
en
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTAT
E 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new databa
se
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using
the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database
to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the back
up
> set.
>|||Hi Tibor,
Thanks for the repsonse. We finally found the actual problem. Someone
restored the copy data outside of the normal job. Once we dropped and
recreated the job functioned as normal. Very strange behavior I must add.
"Tibor Karaszi" wrote:

> A guess is that the source database has grown, so the backup need say 10GB
for one of the database
> files, but the existing database file only has, say, 8GB for that file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
>

Backup and Restore Anomaly

SQL Server 2000 SP4 build 2187
Not sure what is happening with SQL Server backup Internals, I am hoping you
can answer.
A scheduled job backups up database named "Wells" to a device which points
to a physical file as step 1. Same schedule job, step 2, then restores to
database WELLSCopy. The WELLSCopy database has always existed. This has been
working for a very long time. Now, its generating the following error.
Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
Database' :
Began Executing 2006-10-19 00:59:34
Msg 3141, Sev 16: The database to be restored was named 'Wells'.
Reissue the statement using the WITH REPLACE option to overwrite the
'WELLScopy'
database. [SQLSTATE 42000]
Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
Here is the backup command and restore command.
BACKUP DATABASE [Wells] TO Dbackup_WELLS
WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
restore database CHARITYDBCOPY
from dbackup_charitydb
with
move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
I tried to duplicate this issue in our test environment and it restored
successfully every time. I did manage to break it by creating a new database
with a totally different name then try to restore over it and received the
error message.
BOL says it performs a safety check if the REPLACE options is not used. If
so, why has the restore work for a very long time and now decide to break.
Also, why is it allowing me to restore successfully in test without using the
REPLACE option.
I am so confused...
BOL...
When the REPLACE option is not specified, a safety check occurs (which
prevents overwriting a different database by accident). The safety check
ensures that the RESTORE DATABASE statement will not restore the database to
the current server if:
The database named in the RESTORE statement already exists on the current
server, and
The database name is different from the database name recorded in the backup
set.I applogize, I pasted my test restore code. Here is the correct version
RESTORE DATABASE WELLScopy
FROM Dbackup_wells
with
MOVE 'Wells_Data' TO 'e:\data\mssql\data\WELLScopy_Data.MDF',
MOVE 'WELLS_Log' TO 'e:\data\mssql\data\WELLScopy_Log.LDF'
go
"FredG" wrote:
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>|||A guess is that the source database has grown, so the backup need say 10GB for one of the database
files, but the existing database file only has, say, 8GB for that file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>|||Hi Tibor,
Thanks for the repsonse. We finally found the actual problem. Someone
restored the copy data outside of the normal job. Once we dropped and
recreated the job functioned as normal. Very strange behavior I must add.
"Tibor Karaszi" wrote:
> A guess is that the source database has grown, so the backup need say 10GB for one of the database
> files, but the existing database file only has, say, 8GB for that file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> > SQL Server 2000 SP4 build 2187
> >
> > Not sure what is happening with SQL Server backup Internals, I am hoping you
> > can answer.
> >
> > A scheduled job backups up database named "Wells" to a device which points
> > to a physical file as step 1. Same schedule job, step 2, then restores to
> > database WELLSCopy. The WELLSCopy database has always existed. This has been
> > working for a very long time. Now, its generating the following error.
> >
> > Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> > Database' :
> > Began Executing 2006-10-19 00:59:34
> > Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> > Reissue the statement using the WITH REPLACE option to overwrite the
> > 'WELLScopy'
> > database. [SQLSTATE 42000]
> > Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
> >
> >
> > Here is the backup command and restore command.
> > BACKUP DATABASE [Wells] TO Dbackup_WELLS
> > WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
> >
> >
> > restore database CHARITYDBCOPY
> > from dbackup_charitydb
> > with
> > move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> > move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
> >
> >
> > I tried to duplicate this issue in our test environment and it restored
> > successfully every time. I did manage to break it by creating a new database
> > with a totally different name then try to restore over it and received the
> > error message.
> >
> > BOL says it performs a safety check if the REPLACE options is not used. If
> > so, why has the restore work for a very long time and now decide to break.
> > Also, why is it allowing me to restore successfully in test without using the
> > REPLACE option.
> >
> > I am so confused...
> >
> > BOL...
> > When the REPLACE option is not specified, a safety check occurs (which
> > prevents overwriting a different database by accident). The safety check
> > ensures that the RESTORE DATABASE statement will not restore the database to
> > the current server if:
> > The database named in the RESTORE statement already exists on the current
> > server, and
> > The database name is different from the database name recorded in the backup
> > set.
> >
>

Backup and Restore Anomaly

SQL Server 2000 SP4 build 2187
Not sure what is happening with SQL Server backup Internals, I am hoping you
can answer.
A scheduled job backups up database named "Wells" to a device which points
to a physical file as step 1. Same schedule job, step 2, then restores to
database WELLSCopy. The WELLSCopy database has always existed. This has been
working for a very long time. Now, its generating the following error.
Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
Database' :
Began Executing 2006-10-19 00:59:34
Msg 3141, Sev 16: The database to be restored was named 'Wells'.
Reissue the statement using the WITH REPLACE option to overwrite the
'WELLScopy'
database. [SQLSTATE 42000]
Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
Here is the backup command and restore command.
BACKUP DATABASE [Wells] TO Dbackup_WELLS
WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
restore database CHARITYDBCOPY
from dbackup_charitydb
with
move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
I tried to duplicate this issue in our test environment and it restored
successfully every time. I did manage to break it by creating a new database
with a totally different name then try to restore over it and received the
error message.
BOL says it performs a safety check if the REPLACE options is not used. If
so, why has the restore work for a very long time and now decide to break.
Also, why is it allowing me to restore successfully in test without using the
REPLACE option.
I am so confused...
BOL...
When the REPLACE option is not specified, a safety check occurs (which
prevents overwriting a different database by accident). The safety check
ensures that the RESTORE DATABASE statement will not restore the database to
the current server if:
The database named in the RESTORE statement already exists on the current
server, and
The database name is different from the database name recorded in the backup
set.
I applogize, I pasted my test restore code. Here is the correct version
RESTORE DATABASE WELLScopy
FROM Dbackup_wells
with
MOVE 'Wells_Data' TO 'e:\data\mssql\data\WELLScopy_Data.MDF',
MOVE 'WELLS_Log' TO 'e:\data\mssql\data\WELLScopy_Log.LDF'
go
"FredG" wrote:

> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>
|||A guess is that the source database has grown, so the backup need say 10GB for one of the database
files, but the existing database file only has, say, 8GB for that file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>
|||Hi Tibor,
Thanks for the repsonse. We finally found the actual problem. Someone
restored the copy data outside of the normal job. Once we dropped and
recreated the job functioned as normal. Very strange behavior I must add.
"Tibor Karaszi" wrote:

> A guess is that the source database has grown, so the backup need say 10GB for one of the database
> files, but the existing database file only has, say, 8GB for that file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
>

Backup and restore

Hi,
When I tried to restore a database backup that was created by SQL Server
2000 / SP3a installation into a SQL Server 2000 / SP4, I got the following
error message -
Microsoft SQL-DMO (ODBC SQLState: 42000)
The file on device 'D:\Program Files\Microsoft SQL
Server\MSSQL\Data\<DATABASE_NAME>.dbk' is not a valid Microsoft Tape Format
backup set.
RESTORE DATABASE is terminating abnormally.
OK
Hence my following queries -
1) Can I restore a backup
MBS Axapta - MVP
http://www.harishm.com/
Somehow I must have pressed the 'enter' key before writing my earlier post!!
Here are my actual queries -
1) Can I backup/restore from SQL servers with different SPs?
2) If I can, could someone please tell me what the error is all about? Apart
from the SP difference, both systems are identical in all aspects including
network protocols (TCP/IP).
Many thanks in advance,
Harish Mohanbabu
MBS Axapta - MVP
http://www.harishm.com/
"Harish Mohanbabu" wrote:
> Hi,
> When I tried to restore a database backup that was created by SQL Server
> 2000 / SP3a installation into a SQL Server 2000 / SP4, I got the following
> error message -
> --
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> --
> The file on device 'D:\Program Files\Microsoft SQL
> Server\MSSQL\Data\<DATABASE_NAME>.dbk' is not a valid Microsoft Tape Format
> backup set.
> RESTORE DATABASE is terminating abnormally.
> --
> OK
> --
> Hence my following queries -
> 1) Can I restore a backup
|||could you try running restore filelistonly and restore headeronly...
and could you post the output...

>From my initial toughts, it looks like your bkup is corrupt.. cant be
sure yet..
|||Hi,
There shall not be problem to restore user databases between different SPs.
It is more like backup corruption. You may want to try to install a test
machine with SP3a to make sure it is not the cause of the problem. Or, you
may try to restore to other sql server to test.
Thanks & Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Shadow" <dinu_babu@.yahoo.com>
>Newsgroups: microsoft.public.sqlserver.server
>Subject: Re: Backup and restore
>Date: 1 Feb 2006 04:58:37 -0800
>Organization: http://groups.google.com
>Lines: 6
>Message-ID: <1138798716.749411.122180@.g43g2000cwa.googlegroups .com>
>References: <A9767E10-89BD-44BE-805F-06DBDFEE7FA2@.microsoft.com>
> <376FB79B-EC2D-4520-A7B8-F20D4A3CEBC9@.microsoft.com>
>NNTP-Posting-Host: 207.46.50.70
>Mime-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1138798722 18121 127.0.0.1 (1 Feb 2006
12:58:42 GMT)
>X-Complaints-To: groups-abuse@.google.com
>NNTP-Posting-Date: Wed, 1 Feb 2006 12:58:42 +0000 (UTC)
>In-Reply-To: <376FB79B-EC2D-4520-A7B8-F20D4A3CEBC9@.microsoft.com>
>User-Agent: G2/0.2
>X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1),gzip(gfe),gzip(gfe)
>X-HTTP-Via: 1.0 APS-PRXY-01
>Complaints-To: groups-abuse@.google.com
>Injection-Info: g43g2000cwa.googlegroups.com; posting-host=207.46.50.70;
> posting-account=kL0mBg0AAABi9x5I5akt-eVvS_W0s-_U
>Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfee d00.sul.t-online.de!t-onli
ne.de!news.glorb.com!postnews.google.com!g43g2000c wa.googlegroups.com!not-fo
r-mail
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419694
>X-Tomcat-NG: microsoft.public.sqlserver.server
>could you try running restore filelistonly and restore headeronly...
>and could you post the output...
>sure yet..
>
|||Thanks for your posts :-)
You are right Peter - the backup was corrupted. Copied it once again and it
works like a charm!
Cheers,
Harish Mohanbabu
MBS Axapta - MVP
http://www.harishm.com/
"Peter Yang [MSFT]" wrote:

> Hi,
> There shall not be problem to restore user databases between different SPs.
> It is more like backup corruption. You may want to try to install a test
> machine with SP3a to make sure it is not the cause of the problem. Or, you
> may try to restore to other sql server to test.
> Thanks & Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
|||Hello Harish,
Welcome! :-)
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Backup and restore
>thread-index: AcYoIJrluIUoFfrTQRWeqgnU3F5b4w==
>X-WBNR-Posting-Host: 217.15.170.246
>From: "=?Utf-8?B?SGFyaXNoIE1vaGFuYmFidQ==?=" <Axapta@.online.nospam>
>References: <A9767E10-89BD-44BE-805F-06DBDFEE7FA2@.microsoft.com>
<376FB79B-EC2D-4520-A7B8-F20D4A3CEBC9@.microsoft.com>
<1138798716.749411.122180@.g43g2000cwa.googlegroups .com>
<TbHbgt5JGHA.3152@.TK2MSFTNGXA02.phx.gbl>
>Subject: Re: Backup and restore
>Date: Thu, 2 Feb 2006 09:46:32 -0800
>Lines: 30
>Message-ID: <BCC389C0-3828-4BED-B7EA-4DED3B7B6CFC@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419873
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Thanks for your posts :-)
>You are right Peter - the backup was corrupted. Copied it once again and
it[vbcol=seagreen]
>works like a charm!
>Cheers,
>Harish Mohanbabu
>--
>MBS Axapta - MVP
>http://www.harishm.com/
>"Peter Yang [MSFT]" wrote:
SPs.[vbcol=seagreen]
you
>

Backup and restore

Hi,
When I tried to restore a database backup that was created by SQL Server
2000 / SP3a installation into a SQL Server 2000 / SP4, I got the following
error message -
--
Microsoft SQL-DMO (ODBC SQLState: 42000)
--
The file on device 'D:\Program Files\Microsoft SQL
Server\MSSQL\Data\<DATABASE_NAME>.dbk' is not a valid Microsoft Tape Format
backup set.
RESTORE DATABASE is terminating abnormally.
--
OK
--
Hence my following queries -
1) Can I restore a backup
--
MBS Axapta - MVP
http://www.harishm.com/Somehow I must have pressed the 'enter' key before writing my earlier post!!
Here are my actual queries -
1) Can I backup/restore from SQL servers with different SPs?
2) If I can, could someone please tell me what the error is all about? Apart
from the SP difference, both systems are identical in all aspects including
network protocols (TCP/IP).
Many thanks in advance,
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/
"Harish Mohanbabu" wrote:
> Hi,
> When I tried to restore a database backup that was created by SQL Server
> 2000 / SP3a installation into a SQL Server 2000 / SP4, I got the following
> error message -
> --
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> --
> The file on device 'D:\Program Files\Microsoft SQL
> Server\MSSQL\Data\<DATABASE_NAME>.dbk' is not a valid Microsoft Tape Format
> backup set.
> RESTORE DATABASE is terminating abnormally.
> --
> OK
> --
> Hence my following queries -
> 1) Can I restore a backup|||could you try running restore filelistonly and restore headeronly...
and could you post the output...
>From my initial toughts, it looks like your bkup is corrupt.. cant be
sure yet..|||Hi,
There shall not be problem to restore user databases between different SPs.
It is more like backup corruption. You may want to try to install a test
machine with SP3a to make sure it is not the cause of the problem. Or, you
may try to restore to other sql server to test.
Thanks & Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>From: "Shadow" <dinu_babu@.yahoo.com>
>Newsgroups: microsoft.public.sqlserver.server
>Subject: Re: Backup and restore
>Date: 1 Feb 2006 04:58:37 -0800
>Organization: http://groups.google.com
>Lines: 6
>Message-ID: <1138798716.749411.122180@.g43g2000cwa.googlegroups.com>
>References: <A9767E10-89BD-44BE-805F-06DBDFEE7FA2@.microsoft.com>
> <376FB79B-EC2D-4520-A7B8-F20D4A3CEBC9@.microsoft.com>
>NNTP-Posting-Host: 207.46.50.70
>Mime-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1138798722 18121 127.0.0.1 (1 Feb 2006
12:58:42 GMT)
>X-Complaints-To: groups-abuse@.google.com
>NNTP-Posting-Date: Wed, 1 Feb 2006 12:58:42 +0000 (UTC)
>In-Reply-To: <376FB79B-EC2D-4520-A7B8-F20D4A3CEBC9@.microsoft.com>
>User-Agent: G2/0.2
>X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1),gzip(gfe),gzip(gfe)
>X-HTTP-Via: 1.0 APS-PRXY-01
>Complaints-To: groups-abuse@.google.com
>Injection-Info: g43g2000cwa.googlegroups.com; posting-host=207.46.50.70;
> posting-account=kL0mBg0AAABi9x5I5akt-eVvS_W0s-_U
>Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!news.glorb.com!postnews.google.com!g43g2000cwa.googlegroups.com!not-fo
r-mail
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419694
>X-Tomcat-NG: microsoft.public.sqlserver.server
>could you try running restore filelistonly and restore headeronly...
>and could you post the output...
>>From my initial toughts, it looks like your bkup is corrupt.. cant be
>sure yet..
>|||Thanks for your posts :-)
You are right Peter - the backup was corrupted. Copied it once again and it
works like a charm!
Cheers,
Harish Mohanbabu
--
MBS Axapta - MVP
http://www.harishm.com/
"Peter Yang [MSFT]" wrote:
> Hi,
> There shall not be problem to restore user databases between different SPs.
> It is more like backup corruption. You may want to try to install a test
> machine with SP3a to make sure it is not the cause of the problem. Or, you
> may try to restore to other sql server to test.
> Thanks & Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.|||Hello Harish,
Welcome! :-)
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Backup and restore
>thread-index: AcYoIJrluIUoFfrTQRWeqgnU3F5b4w==>X-WBNR-Posting-Host: 217.15.170.246
>From: "=?Utf-8?B?SGFyaXNoIE1vaGFuYmFidQ==?=" <Axapta@.online.nospam>
>References: <A9767E10-89BD-44BE-805F-06DBDFEE7FA2@.microsoft.com>
<376FB79B-EC2D-4520-A7B8-F20D4A3CEBC9@.microsoft.com>
<1138798716.749411.122180@.g43g2000cwa.googlegroups.com>
<TbHbgt5JGHA.3152@.TK2MSFTNGXA02.phx.gbl>
>Subject: Re: Backup and restore
>Date: Thu, 2 Feb 2006 09:46:32 -0800
>Lines: 30
>Message-ID: <BCC389C0-3828-4BED-B7EA-4DED3B7B6CFC@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419873
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Thanks for your posts :-)
>You are right Peter - the backup was corrupted. Copied it once again and
it
>works like a charm!
>Cheers,
>Harish Mohanbabu
>--
>MBS Axapta - MVP
>http://www.harishm.com/
>"Peter Yang [MSFT]" wrote:
>> Hi,
>> There shall not be problem to restore user databases between different
SPs.
>> It is more like backup corruption. You may want to try to install a test
>> machine with SP3a to make sure it is not the cause of the problem. Or,
you
>> may try to restore to other sql server to test.
>> Thanks & Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>

Thursday, February 16, 2012

Backup

I'm not sure if I'm doing this correctly to ensure recovery in case of a
disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
attached to it. What I'm doing is during the night I run a backup through a
maintenance job in enterprise manager to the BACKUP directory in the SQL file
structure. On another server that has a tape drive I'm backing up this
BACKUP directory to tape. Should I be backing up anything else to ensure
disaster recovery.In summary, ensure that you are backing-up the system databases (there is an
option in the maintenance plan wizard to do this) as well as your user
databases. Make the maintenance plan for the system databases separate from
your plans for the user databases. Also ensure that if you are doing tran log
backups on the databases that have full recovery model, that you have the
backups for the simple model databases in a different plan or you will get an
error in the tran log backup job (even though the tran log backups will
succeed).
If you can backup to a remote server using UNC paths if your mssqlserver
service uses a service account (that has the necessary rights to the file
system on the remote server), that would be preferable. If you cannot
however, then your current backup strategy is adequate.
AndyP,
Sr. Database Administrator,
MCDBA 2003
"George Schneider" wrote:
> I'm not sure if I'm doing this correctly to ensure recovery in case of a
> disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> attached to it. What I'm doing is during the night I run a backup through a
> maintenance job in enterprise manager to the BACKUP directory in the SQL file
> structure. On another server that has a tape drive I'm backing up this
> BACKUP directory to tape. Should I be backing up anything else to ensure
> disaster recovery.
>|||I currently have all databses under on Maintenance plan. Why is it
neccessary to seperate the system and user db's into two?
"AndyP" wrote:
> In summary, ensure that you are backing-up the system databases (there is an
> option in the maintenance plan wizard to do this) as well as your user
> databases. Make the maintenance plan for the system databases separate from
> your plans for the user databases. Also ensure that if you are doing tran log
> backups on the databases that have full recovery model, that you have the
> backups for the simple model databases in a different plan or you will get an
> error in the tran log backup job (even though the tran log backups will
> succeed).
> If you can backup to a remote server using UNC paths if your mssqlserver
> service uses a service account (that has the necessary rights to the file
> system on the remote server), that would be preferable. If you cannot
> however, then your current backup strategy is adequate.
>
> --
> AndyP,
> Sr. Database Administrator,
> MCDBA 2003
>
> "George Schneider" wrote:
> > I'm not sure if I'm doing this correctly to ensure recovery in case of a
> > disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> > attached to it. What I'm doing is during the night I run a backup through a
> > maintenance job in enterprise manager to the BACKUP directory in the SQL file
> > structure. On another server that has a tape drive I'm backing up this
> > BACKUP directory to tape. Should I be backing up anything else to ensure
> > disaster recovery.
> >
> >|||Your plans will fail in an ungraceful manner if you have database in both full and simple recovery
mode and you try to do log backups in such a plan.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:0C3B4830-8855-45BF-8CC4-84C27E5EF174@.microsoft.com...
>I currently have all databses under on Maintenance plan. Why is it
> neccessary to seperate the system and user db's into two?
> "AndyP" wrote:
>> In summary, ensure that you are backing-up the system databases (there is an
>> option in the maintenance plan wizard to do this) as well as your user
>> databases. Make the maintenance plan for the system databases separate from
>> your plans for the user databases. Also ensure that if you are doing tran log
>> backups on the databases that have full recovery model, that you have the
>> backups for the simple model databases in a different plan or you will get an
>> error in the tran log backup job (even though the tran log backups will
>> succeed).
>> If you can backup to a remote server using UNC paths if your mssqlserver
>> service uses a service account (that has the necessary rights to the file
>> system on the remote server), that would be preferable. If you cannot
>> however, then your current backup strategy is adequate.
>>
>> --
>> AndyP,
>> Sr. Database Administrator,
>> MCDBA 2003
>>
>> "George Schneider" wrote:
>> > I'm not sure if I'm doing this correctly to ensure recovery in case of a
>> > disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
>> > attached to it. What I'm doing is during the night I run a backup through a
>> > maintenance job in enterprise manager to the BACKUP directory in the SQL file
>> > structure. On another server that has a tape drive I'm backing up this
>> > BACKUP directory to tape. Should I be backing up anything else to ensure
>> > disaster recovery.
>> >
>> >

Tuesday, February 14, 2012

Backup

I'm not sure if I'm doing this correctly to ensure recovery in case of a
disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
attached to it. What I'm doing is during the night I run a backup through
a
maintenance job in enterprise manager to the BACKUP directory in the SQL fil
e
structure. On another server that has a tape drive I'm backing up this
BACKUP directory to tape. Should I be backing up anything else to ensure
disaster recovery.In summary, ensure that you are backing-up the system databases (there is an
option in the maintenance plan wizard to do this) as well as your user
databases. Make the maintenance plan for the system databases separate from
your plans for the user databases. Also ensure that if you are doing tran lo
g
backups on the databases that have full recovery model, that you have the
backups for the simple model databases in a different plan or you will get a
n
error in the tran log backup job (even though the tran log backups will
succeed).
If you can backup to a remote server using UNC paths if your mssqlserver
service uses a service account (that has the necessary rights to the file
system on the remote server), that would be preferable. If you cannot
however, then your current backup strategy is adequate.
AndyP,
Sr. Database Administrator,
MCDBA 2003
"George Schneider" wrote:

> I'm not sure if I'm doing this correctly to ensure recovery in case of a
> disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> attached to it. What I'm doing is during the night I run a backup throug
h a
> maintenance job in enterprise manager to the BACKUP directory in the SQL f
ile
> structure. On another server that has a tape drive I'm backing up this
> BACKUP directory to tape. Should I be backing up anything else to ensure
> disaster recovery.
>|||I currently have all databses under on Maintenance plan. Why is it
neccessary to seperate the system and user db's into two?
"AndyP" wrote:
[vbcol=seagreen]
> In summary, ensure that you are backing-up the system databases (there is
an
> option in the maintenance plan wizard to do this) as well as your user
> databases. Make the maintenance plan for the system databases separate fro
m
> your plans for the user databases. Also ensure that if you are doing tran
log
> backups on the databases that have full recovery model, that you have the
> backups for the simple model databases in a different plan or you will get
an
> error in the tran log backup job (even though the tran log backups will
> succeed).
> If you can backup to a remote server using UNC paths if your mssqlserver
> service uses a service account (that has the necessary rights to the file
> system on the remote server), that would be preferable. If you cannot
> however, then your current backup strategy is adequate.
>
> --
> AndyP,
> Sr. Database Administrator,
> MCDBA 2003
>
> "George Schneider" wrote:
>|||Your plans will fail in an ungraceful manner if you have database in both fu
ll and simple recovery
mode and you try to do log backups in such a plan.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:0C3B4830-8855-45BF-8CC4-84C27E5EF174@.microsoft.com...[vbcol=seagreen]
>I currently have all databses under on Maintenance plan. Why is it
> neccessary to seperate the system and user db's into two?
> "AndyP" wrote:
>

Backup

I'm not sure if I'm doing this correctly to ensure recovery in case of a
disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
attached to it. What I'm doing is during the night I run a backup through a
maintenance job in enterprise manager to the BACKUP directory in the SQL file
structure. On another server that has a tape drive I'm backing up this
BACKUP directory to tape. Should I be backing up anything else to ensure
disaster recovery.
In summary, ensure that you are backing-up the system databases (there is an
option in the maintenance plan wizard to do this) as well as your user
databases. Make the maintenance plan for the system databases separate from
your plans for the user databases. Also ensure that if you are doing tran log
backups on the databases that have full recovery model, that you have the
backups for the simple model databases in a different plan or you will get an
error in the tran log backup job (even though the tran log backups will
succeed).
If you can backup to a remote server using UNC paths if your mssqlserver
service uses a service account (that has the necessary rights to the file
system on the remote server), that would be preferable. If you cannot
however, then your current backup strategy is adequate.
AndyP,
Sr. Database Administrator,
MCDBA 2003
"George Schneider" wrote:

> I'm not sure if I'm doing this correctly to ensure recovery in case of a
> disaster. I have a SQL 2000 Sp4 server, this server has not tape drive
> attached to it. What I'm doing is during the night I run a backup through a
> maintenance job in enterprise manager to the BACKUP directory in the SQL file
> structure. On another server that has a tape drive I'm backing up this
> BACKUP directory to tape. Should I be backing up anything else to ensure
> disaster recovery.
>
|||I currently have all databses under on Maintenance plan. Why is it
neccessary to seperate the system and user db's into two?
"AndyP" wrote:
[vbcol=seagreen]
> In summary, ensure that you are backing-up the system databases (there is an
> option in the maintenance plan wizard to do this) as well as your user
> databases. Make the maintenance plan for the system databases separate from
> your plans for the user databases. Also ensure that if you are doing tran log
> backups on the databases that have full recovery model, that you have the
> backups for the simple model databases in a different plan or you will get an
> error in the tran log backup job (even though the tran log backups will
> succeed).
> If you can backup to a remote server using UNC paths if your mssqlserver
> service uses a service account (that has the necessary rights to the file
> system on the remote server), that would be preferable. If you cannot
> however, then your current backup strategy is adequate.
>
> --
> AndyP,
> Sr. Database Administrator,
> MCDBA 2003
>
> "George Schneider" wrote:
|||Your plans will fail in an ungraceful manner if you have database in both full and simple recovery
mode and you try to do log backups in such a plan.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:0C3B4830-8855-45BF-8CC4-84C27E5EF174@.microsoft.com...[vbcol=seagreen]
>I currently have all databses under on Maintenance plan. Why is it
> neccessary to seperate the system and user db's into two?
> "AndyP" wrote:

Sunday, February 12, 2012

backup

Good evening!
Rookie question regarding backups. Windows Server 2003 SP2 running SQL 2000
SP4 with several databases.
Currently not using Backup Exec to back up the databases. Using the
Enterprise Manager to backup up each DB individually from within SQL.
However, and here comes the question, how do I schedule these backups from
within SQL?
Now, I see the "schedule" button (Console Root | Microsoft SQL Servers | SQL
Server Group | (local)(Windows NT) | Databases | db....right click the db,
select 'All tasks' and then select 'Backup Databases...". At the bottom of
General Tab I see the"Schedule" check box. However, whatever I set does not
stick! Or, does it and I just do not see it?
Additionally, I am also interested in selecting the "overwrite existing
media" and having it stick! It does not.
Am I doing something incorrectly?
I have set all of the DBs to be backed up to its own folder with the same
'parent' folder (E:\SQLBackups\ and then each DB has its own folder and .bkf
file).
I would like to next us NTBackup to backup the 'parent' folder
(E:\SQLBackups). However, that seems kinda pointless if I can not get some
sort of schedule going for each DB (some twice a week and some every day).
We are entertaining the thought of BackupAssistant but I would like to get
NTBackup going on its own...well, actually it is backup with SQL where I am
having the issue...
Thanks!
CaryHi Cary,
When you check the Schedule box on the Backup window you are creating and
scheduling a SQL Server job to do the backup. You can find these jobs in
Enterprise Manager, Management, SQL Server Agent and Jobs.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Cary Shultz" wrote:
> Good evening!
> Rookie question regarding backups. Windows Server 2003 SP2 running SQL 2000
> SP4 with several databases.
> Currently not using Backup Exec to back up the databases. Using the
> Enterprise Manager to backup up each DB individually from within SQL.
> However, and here comes the question, how do I schedule these backups from
> within SQL?
> Now, I see the "schedule" button (Console Root | Microsoft SQL Servers | SQL
> Server Group | (local)(Windows NT) | Databases | db....right click the db,
> select 'All tasks' and then select 'Backup Databases...". At the bottom of
> General Tab I see the"Schedule" check box. However, whatever I set does not
> stick! Or, does it and I just do not see it?
> Additionally, I am also interested in selecting the "overwrite existing
> media" and having it stick! It does not.
> Am I doing something incorrectly?
> I have set all of the DBs to be backed up to its own folder with the same
> 'parent' folder (E:\SQLBackups\ and then each DB has its own folder and .bkf
> file).
> I would like to next us NTBackup to backup the 'parent' folder
> (E:\SQLBackups). However, that seems kinda pointless if I can not get some
> sort of schedule going for each DB (some twice a week and some every day).
> We are entertaining the thought of BackupAssistant but I would like to get
> NTBackup going on its own...well, actually it is backup with SQL where I am
> having the issue...
> Thanks!
> Cary
>
>|||Brett,
Sounds like you are doing what I am trying to do (only will be using
NTBackup instead of Tivoli). I just did not know about the maintenance
plan. Thanks for the tip!
Cary
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:tbc9m31sdhmd823qon5bo73mm6bd06ur52@.4ax.com...
> Create a maintenance plan and that will let you schedule as well as
> other neat options.
> Most backup programs don't reliably backup mdf/ldf (the db and log
> files) as they are open so SQL Server is used to creat the backup
> files. We put the backup files in a backkup directory with a
> subdirectory for each database and then backup the backup directory
> and it's children (along with other stuff on the server) with Tivoli.
> On Sat, 15 Dec 2007 23:58:06 -0500, "Cary Shultz"
> <cshultz@.nospam.outsourceitcorp.com> wrote:
>>Good evening!
>>Rookie question regarding backups. Windows Server 2003 SP2 running SQL
>>2000
>>SP4 with several databases.
>>Currently not using Backup Exec to back up the databases. Using the
>>Enterprise Manager to backup up each DB individually from within SQL.
>>However, and here comes the question, how do I schedule these backups from
>>within SQL?
>>Now, I see the "schedule" button (Console Root | Microsoft SQL Servers |
>>SQL
>>Server Group | (local)(Windows NT) | Databases | db....right click the
>>db,
>>select 'All tasks' and then select 'Backup Databases...". At the bottom
>>of
>>General Tab I see the"Schedule" check box. However, whatever I set does
>>not
>>stick! Or, does it and I just do not see it?
>>Additionally, I am also interested in selecting the "overwrite existing
>>media" and having it stick! It does not.
>>Am I doing something incorrectly?
>>I have set all of the DBs to be backed up to its own folder with the same
>>'parent' folder (E:\SQLBackups\ and then each DB has its own folder and
>>.bkf
>>file).
>>I would like to next us NTBackup to backup the 'parent' folder
>>(E:\SQLBackups). However, that seems kinda pointless if I can not get
>>some
>>sort of schedule going for each DB (some twice a week and some every day).
>>We are entertaining the thought of BackupAssistant but I would like to get
>>NTBackup going on its own...well, actually it is backup with SQL where I
>>am
>>having the issue...
>>Thanks!
>>Cary|||Ben,
I did not look there...did not know to look there. Thanks for the tip!
Cary
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:C9D9326C-E2E5-4A9A-ACB1-14EB66076610@.microsoft.com...
> Hi Cary,
> When you check the Schedule box on the Backup window you are creating and
> scheduling a SQL Server job to do the backup. You can find these jobs in
> Enterprise Manager, Management, SQL Server Agent and Jobs.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Cary Shultz" wrote:
>> Good evening!
>> Rookie question regarding backups. Windows Server 2003 SP2 running SQL
>> 2000
>> SP4 with several databases.
>> Currently not using Backup Exec to back up the databases. Using the
>> Enterprise Manager to backup up each DB individually from within SQL.
>> However, and here comes the question, how do I schedule these backups
>> from
>> within SQL?
>> Now, I see the "schedule" button (Console Root | Microsoft SQL Servers |
>> SQL
>> Server Group | (local)(Windows NT) | Databases | db....right click the
>> db,
>> select 'All tasks' and then select 'Backup Databases...". At the bottom
>> of
>> General Tab I see the"Schedule" check box. However, whatever I set does
>> not
>> stick! Or, does it and I just do not see it?
>> Additionally, I am also interested in selecting the "overwrite existing
>> media" and having it stick! It does not.
>> Am I doing something incorrectly?
>> I have set all of the DBs to be backed up to its own folder with the same
>> 'parent' folder (E:\SQLBackups\ and then each DB has its own folder and
>> .bkf
>> file).
>> I would like to next us NTBackup to backup the 'parent' folder
>> (E:\SQLBackups). However, that seems kinda pointless if I can not get
>> some
>> sort of schedule going for each DB (some twice a week and some every
>> day).
>> We are entertaining the thought of BackupAssistant but I would like to
>> get
>> NTBackup going on its own...well, actually it is backup with SQL where I
>> am
>> having the issue...
>> Thanks!
>> Cary
>>|||Brett,
You raised some questions that I was going to ask...
I have things set up so that the "data" and the "logs" are backed up after
everyone has gone home (starting at 5:30PM). First the data is backed up to
the "DATA" folder for that specific Database and then, five minutes later,
the logs are backed up to the "LOG" folder for that specific Database. I
have this set up via maintenance plans (thanks for the tip there...I
eventually would have found it I am sure but it is nice to do things once or
twice instead of four or five times!
Now, I was going to ask the question how the restore in SQL works. I am
pretty familiar with how this works in Active Directory (system state) and
Exchange but have no idea in SQL. It *seems* like I would restore the data
as well as the log files (transaction logs)...you mentioned to a specific
point in time in your reply. Not sure if I want/need to play with that at
the moment. I would like to be able to restore it to "yesterday" (read:
yesterdays back up at 5:45PM...yes, they loose all the work from today...)
for the time being, not to "today at 10:45AM"...I have to crawl before I
can walk, right?!
Thanks,
Cary
PS..."MP way"? Might that be "multi-point" or "multiple points", as in
multiple points through out "today"?
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:ovlam3plllc7edmuhtd57d58391dpvrtkh@.4ax.com...
> You're welcome. There are lots of ways to do it but I like the MP way
> because of the flexibility. As someone else pointed out that in SQL
> 2000 these show up under the jobs. In SQL 2005 it's organized a
> little better - in my opinion <G>.
> Remember - the critical part of the backup is the restore plan - does
> it work! You should consider having a system where you can test
> restores.
> And then there is the question - do you want to backup the transaction
> logs so you can get to a point in time? I do on some of our systems -
> I run a full backup early in the morning and then before the users
> start hitting the database I start transaction logging until shortly
> after they go home.
> Also, you need to consider the recovey mode you want to use.
> On Sun, 16 Dec 2007 05:47:32 -0500, "Cary Shultz"
> <cshultz@.nospam.outsourceitcorp.com> wrote:
>>Brett,
>>Sounds like you are doing what I am trying to do (only will be using
>>NTBackup instead of Tivoli). I just did not know about the maintenance
>>plan. Thanks for the tip!
>>Cary
>>
>>"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
>>news:tbc9m31sdhmd823qon5bo73mm6bd06ur52@.4ax.com...
>> Create a maintenance plan and that will let you schedule as well as
>> other neat options.
>> Most backup programs don't reliably backup mdf/ldf (the db and log
>> files) as they are open so SQL Server is used to creat the backup
>> files. We put the backup files in a backkup directory with a
>> subdirectory for each database and then backup the backup directory
>> and it's children (along with other stuff on the server) with Tivoli.
>> On Sat, 15 Dec 2007 23:58:06 -0500, "Cary Shultz"
>> <cshultz@.nospam.outsourceitcorp.com> wrote:
>>Good evening!
>>Rookie question regarding backups. Windows Server 2003 SP2 running SQL
>>2000
>>SP4 with several databases.
>>Currently not using Backup Exec to back up the databases. Using the
>>Enterprise Manager to backup up each DB individually from within SQL.
>>However, and here comes the question, how do I schedule these backups
>>from
>>within SQL?
>>Now, I see the "schedule" button (Console Root | Microsoft SQL Servers |
>>SQL
>>Server Group | (local)(Windows NT) | Databases | db....right click the
>>db,
>>select 'All tasks' and then select 'Backup Databases...". At the bottom
>>of
>>General Tab I see the"Schedule" check box. However, whatever I set does
>>not
>>stick! Or, does it and I just do not see it?
>>Additionally, I am also interested in selecting the "overwrite existing
>>media" and having it stick! It does not.
>>Am I doing something incorrectly?
>>I have set all of the DBs to be backed up to its own folder with the
>>same
>>'parent' folder (E:\SQLBackups\ and then each DB has its own folder and
>>.bkf
>>file).
>>I would like to next us NTBackup to backup the 'parent' folder
>>(E:\SQLBackups). However, that seems kinda pointless if I can not get
>>some
>>sort of schedule going for each DB (some twice a week and some every
>>day).
>>We are entertaining the thought of BackupAssistant but I would like to
>>get
>>NTBackup going on its own...well, actually it is backup with SQL where I
>>am
>>having the issue...
>>Thanks!
>>Cary
>>|||Brett,
MP...so, it is not "Member of Parliment"? Drats!
I lieved in Germany for several years after I graduated from college, so
when I see "MP" I immediately think of Member of Parliment. Looks like I
need to relearn that!
And, thanks for your tips. I learn a lot in these news groups. In fact, I
used to be an MVP for Active Directory a few years back. In my current
position (which will hopefully stay 'current' for a really long time) I do a
lot of the AD stuff. At a few of the clients I am getting more and more
involved with applications that rely on SQL. I do not really speak SQL just
yet...so, I am taking the initiative and starting to learn (just like I did
with AD many moons ago). Backup and restores are hot topics right now so I
am trying to learn quickly.
You will problably be seeing more of me in these two or three news groups.
Hopefully the questions that I ask will not only help me, but all those who
have similar questions. When I first started in AD I looked at the
questions before looking at the replies and tried to figure out what was
going on and then tried to find an answer (without looking at the
reply/replies). That whole "road to discovery" was a fun ride...I hope
that others take it...and enjoy!
Thanks again,
Cary
PS. If you have any AD questions give a shout! Just remove the obvious
part from my e-mail address. I gladly help others when I can (and the
'when' part is the problem!) and will go out of my way to help those who
have helped me.
"Brett I. Holcomb" <brettholcomb@.bellsouth.net> wrote in message
news:iltam3pjoubfoc8ik1ge1sa3dmlqedlh3f@.4ax.com...
> Sorry - buzzword itis <G>. MP is Maintenance Plan
> I am not an expert by any means on SQL Server. I became a DBA because
> I'm the Windows Server Admin and we needed a DBA (there was none) last
> spring so it seemed like a good fit to management <G>. Actually, I
> love it and have been enjoying it. I'm learning by reading and doing
> what you are doing - asking questions here.
> Restores that I've done I've used the right click in Enterprise
> Manager (on the server) and chosen the restore option. Say you have
> a backup of the database at 0200 - you restore it first. Then you go
> through the transaction logs and restore them. You have to make sure
> that you select the option that leaves the database so it can have the
> next restore done.
> If you're going to be doing this routinely (and it sounds like it <G>)
> get Kalen Daleny's book on SQL 2000 Server. It's big but good reading
> and I used it as a reference a lot. I say used because now I'm moving
> to SQL 2005 and I have her five set book that she coauthored. It's
> worth the money. My Management purchased it for me but I'd buy it for
> myself if I had to.
> Also Books on Line (BOL) is another good reference source.
> Take it one step at a time. I'm still working on the list of "Things
> I want to try and learn" now. Some of it will happen because of
> things that happen to your databases so you'll learn on the job <G>.
> Also - DOCUMENT!! Our group, IT Operations, has a Wiki and I have a
> section for SQL Server where I document our procedures like how to
> create a MP, notes on stuff I thought was good to keep, SQL code,
> everything. Not only will it help if you leave but I find I need to
> refer to it.
>
> On Sun, 16 Dec 2007 13:17:39 -0500, "Cary Shultz"
> <cshultz@.nospam.outsourceitcorp.com> wrote:
>>Brett,
>>You raised some questions that I was going to ask...
>>I have things set up so that the "data" and the "logs" are backed up after
>>everyone has gone home (starting at 5:30PM). First the data is backed up
>>to
>>the "DATA" folder for that specific Database and then, five minutes later,
>>the logs are backed up to the "LOG" folder for that specific Database. I
>>have this set up via maintenance plans (thanks for the tip there...I
>>eventually would have found it I am sure but it is nice to do things once
>>or
>>twice instead of four or five times!
>>Now, I was going to ask the question how the restore in SQL works. I am
>>pretty familiar with how this works in Active Directory (system state) and
>>Exchange but have no idea in SQL. It *seems* like I would restore the
>>data
>>as well as the log files (transaction logs)...you mentioned to a specific
>>point in time in your reply. Not sure if I want/need to play with that at
>>the moment. I would like to be able to restore it to "yesterday" (read:
>>yesterdays back up at 5:45PM...yes, they loose all the work from
>>today...)
>>for the time being, not to "today at 10:45AM"...I have to crawl before I
>>can walk, right?!
>>Thanks,
>>Cary