Cannot restore database: backups

Showing posts with label backups. Show all posts

Sunday, March 25, 2012

Can't attach database after server crash?

Hi...
I have a database I was working on a few months ago. The server it was on
crashed before I could get backups of it but I managed to get the original
database
file before anything happened to it. When the server was redone, the
usernames were changed a little and I now have a different windows username.
I wouldn't
think this would matter since the sql server uses windows security to sign
in anyways. Either way, I have tried to attach the database and I keep
getting
this error:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
The file "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
compressed but does not reside in a read-only database or filegroup. The
file must be
decompressed.
Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
(Microsoft SQL
Server, Error: 5118)
Any ideas how to fix this? I suppose I can redo if I had to since there was
only 3 tables in there but it is annoying that I have to redo the whole
thing
anytime something small happens...> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
NTFS compressed files on writable file groups are not supported, hence the
error.
Try decompressing the file. Navigate to the mdf file using Windows Explorer
and select Properties-->Advanced and uncheck the compress option. Same with
the log file (ldf).
Hope this helps.
Dan Guzman
SQL Server MVP
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
> Hi...
> I have a database I was working on a few months ago. The server it was on
> crashed before I could get backups of it but I managed to get the original
> database
> file before anything happened to it. When the server was redone, the
> usernames were changed a little and I now have a different windows
> username. I wouldn't
> think this would matter since the sql server uses windows security to sign
> in anyways. Either way, I have tried to attach the database and I keep
> getting
> this error:
> Attach database failed for Server 'ANDY\SQLEXPRESS'.
> (Microsoft.SqlServer.Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
> Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
> (Microsoft SQL
> Server, Error: 5118)
> Any ideas how to fix this? I suppose I can redo if I had to since there
> was only 3 tables in there but it is annoying that I have to redo the
> whole thing
> anytime something small happens...
>|||I will check it out and let you know what happens. You might have saved my
neck...
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
> NTFS compressed files on writable file groups are not supported, hence the
> error.
> Try decompressing the file. Navigate to the mdf file using Windows
> Explorer and select Properties-->Advanced and uncheck the compress option.
> Same with the log file (ldf).
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was on
>> crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since there
>> was only 3 tables in there but it is annoying that I have to redo the
>> whole thing
>> anytime something small happens...
>>
>|||Hi... I tried your idea of unchecking the compress this file box in the
database file and its log file. I tried to attach it again and I get the
following message:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
One or more files do not match the primary file of the database. If you are
attempting to attach
a database, retry the operation with the correct files. If this is an
existing database, the file may
be corrupted and should be restored from a backup. (Microsoft SQL Server,
Error: 5173)
Does this mean I have to redo my database by hand? I don't have any backup
of it and I have no idea what is wrong now. Any ideas?
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>I will check it out and let you know what happens. You might have saved my
>neck...
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence
>> the error.
>> Try decompressing the file. Navigate to the mdf file using Windows
>> Explorer and select Properties-->Advanced and uncheck the compress
>> option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was
>> on crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since there
>> was only 3 tables in there but it is annoying that I have to redo the
>> whole thing
>> anytime something small happens...
>>
>|||You can try sp_attach_db and specify the path & file name for *all* the database files (mdf, ldf and
possibly ndf). If you are sure you got the path correct and still get some strange error, you are
most probably in trouble. Attaching is only supported if you did a clean detach first, if you
didn't, well, these things can happen.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
> Hi... I tried your idea of unchecking the compress this file box in the database file and its log
> file. I tried to attach it again and I get the following message:
> Attach database failed for Server 'ANDY\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> One or more files do not match the primary file of the database. If you are attempting to attach
> a database, retry the operation with the correct files. If this is an existing database, the file
> may
> be corrupted and should be restored from a backup. (Microsoft SQL Server, Error: 5173)
> Does this mean I have to redo my database by hand? I don't have any backup of it and I have no
> idea what is wrong now. Any ideas?
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>>I will check it out and let you know what happens. You might have saved my neck...
>>
>> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
>> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence the error.
>> Try decompressing the file. Navigate to the mdf file using Windows Explorer and select
>> Properties-->Advanced and uncheck the compress option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was on crashed before I
>> could get backups of it but I managed to get the original database
>> file before anything happened to it. When the server was redone, the usernames were changed a
>> little and I now have a different windows username. I wouldn't
>> think this would matter since the sql server uses windows security to sign in anyways. Either
>> way, I have tried to attach the database and I keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since there was only 3 tables in
>> there but it is annoying that I have to redo the whole thing
>> anytime something small happens...
>>
>>
>|||Guess it's back to the drawing board then...sigh... At least the DB wasn't
very huge...grin
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
> You can try sp_attach_db and specify the path & file name for *all* the
> database files (mdf, ldf and possibly ndf). If you are sure you got the
> path correct and still get some strange error, you are most probably in
> trouble. Attaching is only supported if you did a clean detach first, if
> you didn't, well, these things can happen.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
>> Hi... I tried your idea of unchecking the compress this file box in the
>> database file and its log file. I tried to attach it again and I get the
>> following message:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> One or more files do not match the primary file of the database. If you
>> are attempting to attach
>> a database, retry the operation with the correct files. If this is an
>> existing database, the file may
>> be corrupted and should be restored from a backup. (Microsoft SQL Server,
>> Error: 5173)
>> Does this mean I have to redo my database by hand? I don't have any
>> backup of it and I have no idea what is wrong now. Any ideas?
>>
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>>I will check it out and let you know what happens. You might have saved
>>my neck...
>>
>> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
>> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence
>> the error.
>> Try decompressing the file. Navigate to the mdf file using Windows
>> Explorer and select Properties-->Advanced and uncheck the compress
>> option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was
>> on crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or
>> batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since
>> there was only 3 tables in there but it is annoying that I have to
>> redo the whole thing
>> anytime something small happens...
>>
>>
>>
>|||... and you now know to do your backups regularly... ;-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:%23V$7AlC4HHA.484@.TK2MSFTNGP06.phx.gbl...
> Guess it's back to the drawing board then...sigh... At least the DB wasn't
> very huge...grin
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
>> You can try sp_attach_db and specify the path & file name for *all* the
>> database files (mdf, ldf and possibly ndf). If you are sure you got the
>> path correct and still get some strange error, you are most probably in
>> trouble. Attaching is only supported if you did a clean detach first, if
>> you didn't, well, these things can happen.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
>> Hi... I tried your idea of unchecking the compress this file box in the
>> database file and its log file. I tried to attach it again and I get the
>> following message:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> One or more files do not match the primary file of the database. If you
>> are attempting to attach
>> a database, retry the operation with the correct files. If this is an
>> existing database, the file may
>> be corrupted and should be restored from a backup. (Microsoft SQL Server,
>> Error: 5173)
>> Does this mean I have to redo my database by hand? I don't have any
>> backup of it and I have no idea what is wrong now. Any ideas?
>>
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>>I will check it out and let you know what happens. You might have saved
>>my neck...
>>
>> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
>> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence
>> the error.
>> Try decompressing the file. Navigate to the mdf file using Windows
>> Explorer and select Properties-->Advanced and uncheck the compress
>> option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was
>> on crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or
>> batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since
>> there was only 3 tables in there but it is annoying that I have to
>> redo the whole thing
>> anytime something small happens...
>>
>>
>>
>>
>sql

Can't attach database after server crash?

cant append multiple Diff backups to same file?...

I run two different types of backups on the same database.
A monthly full and nightly diffs appending to the same full file - file 'A'
A weekly full with 10 min trans log backups appending to same file - file
'B'- during working hours.
2 strategies, 2 backup files.
These are new strats that have gone live this week - tuesday in fact. The
monthly and weekly both ran fine on tuesday as did the nightly diff and all
the TS backups througout the day. last night - Weds - the nightly diff faile
d
with the following error:
"
Executed as user: <USERNAME>. Cannot perform a differential backup for
database "objectstore", because a current database backup does not exist.
Perform a full database backup by reissuing BACKUP DATABASE, omitting the
WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035) BACKUP DATABASE
is
terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
"
Whilst the error is perfectly legible I dont understand what its implying -
cant I add multiple Diff backups to the same full backup OR is my weekly / 1
0
mins on the same database (but to a diff backup file) ballsing things up for
me somehow? If this is the case how come everything ran fine on tuesday nigh
t?
Any help gets beers.
THanks
Alastair Jones.I shoudl add that the chronology of the backups is as follows:
monthly init @. 7am first tues of month to file A
weekly init @. 7.30 Am tuesdays to file B
nightly diff to file A @. 2215 nightly
TL backups to file B every 10 mins
"Methodology" wrote:

> I run two different types of backups on the same database.
> A monthly full and nightly diffs appending to the same full file - file 'A
'
> A weekly full with 10 min trans log backups appending to same file - file
> 'B'- during working hours.
> 2 strategies, 2 backup files.
> These are new strats that have gone live this week - tuesday in fact. The
> monthly and weekly both ran fine on tuesday as did the nightly diff and al
l
> the TS backups througout the day. last night - Weds - the nightly diff fai
led
> with the following error:
> "
> Executed as user: <USERNAME>. Cannot perform a differential backup for
> database "objectstore", because a current database backup does not exist.
> Perform a full database backup by reissuing BACKUP DATABASE, omitting the
> WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035) BACKUP DATABA
SE is
> terminating abnormally. [SQLSTATE 42000] (Error 3013). The step faile
d.
> "
>
> Whilst the error is perfectly legible I dont understand what its implying
-
> cant I add multiple Diff backups to the same full backup OR is my weekly /
10
> mins on the same database (but to a diff backup file) ballsing things up f
or
> me somehow? If this is the case how come everything ran fine on tuesday ni
ght?
> Any help gets beers.
> THanks
> Alastair Jones.
>

cant append multiple Diff backups to same file?...

I run two different types of backups on the same database.
A monthly full and nightly diffs appending to the same full file - file 'A'
A weekly full with 10 min trans log backups appending to same file - file
'B'- during working hours.
2 strategies, 2 backup files.
These are new strats that have gone live this week - tuesday in fact. The
monthly and weekly both ran fine on tuesday as did the nightly diff and all
the TS backups througout the day. last night - Weds - the nightly diff failed
with the following error:
"
Executed as user: <USERNAME>. Cannot perform a differential backup for
database "objectstore", because a current database backup does not exist.
Perform a full database backup by reissuing BACKUP DATABASE, omitting the
WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035) BACKUP DATABASE is
terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
"
Whilst the error is perfectly legible I dont understand what its implying -
cant I add multiple Diff backups to the same full backup OR is my weekly / 10
mins on the same database (but to a diff backup file) ballsing things up for
me somehow? If this is the case how come everything ran fine on tuesday night?
Any help gets beers.
THanks
Alastair Jones.I shoudl add that the chronology of the backups is as follows:
monthly init @. 7am first tues of month to file A
weekly init @. 7.30 Am tuesdays to file B
nightly diff to file A @. 2215 nightly
TL backups to file B every 10 mins
"Methodology" wrote:
> I run two different types of backups on the same database.
> A monthly full and nightly diffs appending to the same full file - file 'A'
> A weekly full with 10 min trans log backups appending to same file - file
> 'B'- during working hours.
> 2 strategies, 2 backup files.
> These are new strats that have gone live this week - tuesday in fact. The
> monthly and weekly both ran fine on tuesday as did the nightly diff and all
> the TS backups througout the day. last night - Weds - the nightly diff failed
> with the following error:
> "
> Executed as user: <USERNAME>. Cannot perform a differential backup for
> database "objectstore", because a current database backup does not exist.
> Perform a full database backup by reissuing BACKUP DATABASE, omitting the
> WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035) BACKUP DATABASE is
> terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
> "
>
> Whilst the error is perfectly legible I dont understand what its implying -
> cant I add multiple Diff backups to the same full backup OR is my weekly / 10
> mins on the same database (but to a diff backup file) ballsing things up for
> me somehow? If this is the case how come everything ran fine on tuesday night?
> Any help gets beers.
> THanks
> Alastair Jones.
>

cant append multiple Diff backups to same file?...

I run two different types of backups on the same database.
A monthly full and nightly diffs appending to the same full file - file 'A'
A weekly full with 10 min trans log backups appending to same file - file
'B'- during working hours.
2 strategies, 2 backup files.
These are new strats that have gone live this week - tuesday in fact. The
monthly and weekly both ran fine on tuesday as did the nightly diff and all
the TS backups througout the day. last night - Weds - the nightly diff failed
with the following error:
"
Executed as user: <USERNAME>. Cannot perform a differential backup for
database "objectstore", because a current database backup does not exist.
Perform a full database backup by reissuing BACKUP DATABASE, omitting the
WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035) BACKUP DATABASE is
terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
"
Whilst the error is perfectly legible I dont understand what its implying -
cant I add multiple Diff backups to the same full backup OR is my weekly / 10
mins on the same database (but to a diff backup file) ballsing things up for
me somehow? If this is the case how come everything ran fine on tuesday night?
Any help gets beers.
THanks
Alastair Jones.
I shoudl add that the chronology of the backups is as follows:
monthly init @. 7am first tues of month to file A
weekly init @. 7.30 Am tuesdays to file B
nightly diff to file A @. 2215 nightly
TL backups to file B every 10 mins
"Methodology" wrote:

> I run two different types of backups on the same database.
> A monthly full and nightly diffs appending to the same full file - file 'A'
> A weekly full with 10 min trans log backups appending to same file - file
> 'B'- during working hours.
> 2 strategies, 2 backup files.
> These are new strats that have gone live this week - tuesday in fact. The
> monthly and weekly both ran fine on tuesday as did the nightly diff and all
> the TS backups througout the day. last night - Weds - the nightly diff failed
> with the following error:
> "
> Executed as user: <USERNAME>. Cannot perform a differential backup for
> database "objectstore", because a current database backup does not exist.
> Perform a full database backup by reissuing BACKUP DATABASE, omitting the
> WITH DIFFERENTIAL option. [SQLSTATE 42000] (Error 3035) BACKUP DATABASE is
> terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
> "
>
> Whilst the error is perfectly legible I dont understand what its implying -
> cant I add multiple Diff backups to the same full backup OR is my weekly / 10
> mins on the same database (but to a diff backup file) ballsing things up for
> me somehow? If this is the case how come everything ran fine on tuesday night?
> Any help gets beers.
> THanks
> Alastair Jones.
>

Thursday, March 22, 2012

Can't achieve backups with SQL Server 7.00.1063 on Win2k

Good morning,
On a brand new powerful server, I've had this intermittent problem with
the following message for over a week, when I tried to make a manual or
scheduled backup. I get this message instantly when I start the backup as a
pop-up in Enterprise Manager and in the SQL Server logs.
BackupMedium::ReportIoError: write failure on backup device
'd:\MSSQL7\BACKUP\FmdtestPascal.BAK'. Operating system error
1453(Insufficient quota to complete the requested service.).
The backup to be made is on a small 1.5 gb database. On the array, there's
about 189 Gb of free space on the hard drive. It behaves like a hardware
problem
Hi
Check that disk quotas are not enabled for the destination drive at OS level.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Pascal" wrote:

> Good morning,
> On a brand new powerful server, I've had this intermittent problem with
> the following message for over a week, when I tried to make a manual or
> scheduled backup. I get this message instantly when I start the backup as a
> pop-up in Enterprise Manager and in the SQL Server logs.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\MSSQL7\BACKUP\FmdtestPascal.BAK'. Operating system error
> 1453(Insufficient quota to complete the requested service.).
> The backup to be made is on a small 1.5 gb database. On the array, there's
> about 189 Gb of free space on the hard drive. It behaves like a hardware
> problem

Can't achieve backups with SQL Server 7.00.1063 on Win2k

Good morning,
On a brand new powerful server, I've had this intermittent problem with
the following message for over a week, when I tried to make a manual or
scheduled backup. I get this message instantly when I start the backup as a
pop-up in Enterprise Manager and in the SQL Server logs.
BackupMedium::ReportIoError: write failure on backup device
'd:\MSSQL7\BACKUP\FmdtestPascal.BAK'. Operating system error
1453(Insufficient quota to complete the requested service.).
The backup to be made is on a small 1.5 gb database. On the array, there's
about 189 Gb of free space on the hard drive. It behaves like a hardware
problemHi
Check that disk quotas are not enabled for the destination drive at OS level.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Pascal" wrote:
> Good morning,
> On a brand new powerful server, I've had this intermittent problem with
> the following message for over a week, when I tried to make a manual or
> scheduled backup. I get this message instantly when I start the backup as a
> pop-up in Enterprise Manager and in the SQL Server logs.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\MSSQL7\BACKUP\FmdtestPascal.BAK'. Operating system error
> 1453(Insufficient quota to complete the requested service.).
> The backup to be made is on a small 1.5 gb database. On the array, there's
> about 189 Gb of free space on the hard drive. It behaves like a hardware
> problem

Can't achieve backups with SQL Server 7.00.1063 on Win2k

Good morning,
On a brand new powerful server, I've had this intermittent problem with
the following message for over a week, when I tried to make a manual or
scheduled backup. I get this message instantly when I start the backup as a
pop-up in Enterprise Manager and in the SQL Server logs.
BackupMedium::ReportIoError: write failure on backup device
'd:\MSSQL7\BACKUP\FmdtestPascal.BAK'. Operating system error
1453(Insufficient quota to complete the requested service.).
The backup to be made is on a small 1.5 gb database. On the array, there's
about 189 Gb of free space on the hard drive. It behaves like a hardware
problemHi
Check that disk quotas are not enabled for the destination drive at OS level
.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Pascal" wrote:

> Good morning,
> On a brand new powerful server, I've had this intermittent problem with
> the following message for over a week, when I tried to make a manual or
> scheduled backup. I get this message instantly when I start the backup as
a
> pop-up in Enterprise Manager and in the SQL Server logs.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\MSSQL7\BACKUP\FmdtestPascal.BAK'. Operating system error
> 1453(Insufficient quota to complete the requested service.).
> The backup to be made is on a small 1.5 gb database. On the array, there'
s
> about 189 Gb of free space on the hard drive. It behaves like a hardware
> problemsql

Sunday, March 25, 2012

Can't attach database after server crash?

Can't attach database after server crash?

Can't attach database after server crash?

cant append multiple Diff backups to same file?...

cant append multiple Diff backups to same file?...

cant append multiple Diff backups to same file?...

Thursday, March 22, 2012

Can't achieve backups with SQL Server 7.00.1063 on Win2k

Can't achieve backups with SQL Server 7.00.1063 on Win2k

Can't achieve backups with SQL Server 7.00.1063 on Win2k

Cannot restore database

Blog Archive

About Me