Backup Problem

Hello Everyone,
We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
Windows 2003 Ent) from one subnet to another. Everything went well
(apparently) until we realized that our backups are failing (both the
existing jobs and manual backups) after the change in ip/subnet was
done. All backup attempts return with errrors similar to these:
===
18204 :
BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
failed to open. Operating system error = 32(The process cannot access
the file because it is being used by another process.).
===
3041 :
BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
===
When the manual backup is initiated without Verification, no (popup)
error is generated (but the error above is still logged on the event
log) and the backup says it ran successfully. When the backup file is
checked, the size is Zero (0) kb.
There is no apparent problem in connecting to both the two instances
of the server and applications are working okay, it's just the backup
problem that is bugging us.
drive Q = quorum
drive F = one of the shared drives with 20Gb+ remaining
The database that we are attempting to backup is just about 11Gb in
size.
Any help is appreciated.
Thanks.
AramidJust a quick question - were you backing up to a shared network drive
previously? What if you try backing up to the fully qualified UNC Path
instead?
"aramid" <aramid@.hotmail.com> wrote in message
news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.
4ax.com...
> Hello Everyone,
> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
> Windows 2003 Ent) from one subnet to another. Everything went well
> (apparently) until we realized that our backups are failing (both the
> existing jobs and manual backups) after the change in ip/subnet was
> done. All backup attempts return with errrors similar to these:
> ===
> 18204 :
> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
> failed to open. Operating system error = 32(The process cannot access
> the file because it is being used by another process.).
> ===
> 3041 :
> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
> ===
>
> When the manual backup is initiated without Verification, no (popup)
> error is generated (but the error above is still logged on the event
> log) and the backup says it ran successfully. When the backup file is
> checked, the size is Zero (0) kb.
> There is no apparent problem in connecting to both the two instances
> of the server and applications are working okay, it's just the backup
> problem that is bugging us.
> drive Q = quorum
> drive F = one of the shared drives with 20Gb+ remaining
> The database that we are attempting to backup is just about 11Gb in
> size.
>
> Any help is appreciated.
> Thanks.
>
> Aramid
>|||Thanks for your reply, Michael.
We are not backing up to any shared network drive, just to this drive,
which is one of the logical drives on an external disk array attached
to the cluster.
Aramid
On Sun, 10 Apr 2005 23:56:13 -0400, "Michael C#" <xyz@.abcdef.com>
wrote:

>Just a quick question - were you backing up to a shared network drive
>previously? What if you try backing up to the fully qualified UNC Path
>instead?
>"aramid" <aramid@.hotmail.com> wrote in message
> news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.
4ax.com...
>|||aramid
It seems that is permission or OS issue . We have recently moved to the
cluster and what i did in the backup script only changed the D:\ Driver
path to N:\ driver path. Run SQL Server Profile to see what is going on.
Have you searched on internet for those errors?
"aramid" <aramid@.hotmail.com> wrote in message
news:0ouj51dm2esqntk6pegt6f37m36f4g8brj@.
4ax.com...
> Thanks for your reply, Michael.
> We are not backing up to any shared network drive, just to this drive,
> which is one of the logical drives on an external disk array attached
> to the cluster.
> Aramid
> On Sun, 10 Apr 2005 23:56:13 -0400, "Michael C#" <xyz@.abcdef.com>
> wrote:
>
>|||SQL Server say that the backup file is used by some other process. I'd get a
tool with which I can
check who is using the file...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"aramid" <aramid@.hotmail.com> wrote in message news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.
4ax.c
om...
> Hello Everyone,
> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
> Windows 2003 Ent) from one subnet to another. Everything went well
> (apparently) until we realized that our backups are failing (both the
> existing jobs and manual backups) after the change in ip/subnet was
> done. All backup attempts return with errrors similar to these:
> ===
> 18204 :
> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
> failed to open. Operating system error = 32(The process cannot access
> the file because it is being used by another process.).
> ===
> 3041 :
> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
> ===
>
> When the manual backup is initiated without Verification, no (popup)
> error is generated (but the error above is still logged on the event
> log) and the backup says it ran successfully. When the backup file is
> checked, the size is Zero (0) kb.
> There is no apparent problem in connecting to both the two instances
> of the server and applications are working okay, it's just the backup
> problem that is bugging us.
> drive Q = quorum
> drive F = one of the shared drives with 20Gb+ remaining
> The database that we are attempting to backup is just about 11Gb in
> size.
>
> Any help is appreciated.
> Thanks.
>
> Aramid
>

Backup Problem

Hello Everyone,
We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
Windows 2003 Ent) from one subnet to another. Everything went well
(apparently) until we realized that our backups are failing (both the
existing jobs and manual backups) after the change in ip/subnet was
done. All backup attempts return with errrors similar to these:
=== 18204 :
BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
failed to open. Operating system error = 32(The process cannot access
the file because it is being used by another process.).
=== 3041 :
BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
===
When the manual backup is initiated without Verification, no (popup)
error is generated (but the error above is still logged on the event
log) and the backup says it ran successfully. When the backup file is
checked, the size is Zero (0) kb.
There is no apparent problem in connecting to both the two instances
of the server and applications are working okay, it's just the backup
problem that is bugging us.
drive Q = quorum
drive F = one of the shared drives with 20Gb+ remaining
The database that we are attempting to backup is just about 11Gb in
size.
Any help is appreciated.
Thanks.
AramidJust a quick question - were you backing up to a shared network drive
previously? What if you try backing up to the fully qualified UNC Path
instead?
"aramid" <aramid@.hotmail.com> wrote in message
news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.4ax.com...
> Hello Everyone,
> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
> Windows 2003 Ent) from one subnet to another. Everything went well
> (apparently) until we realized that our backups are failing (both the
> existing jobs and manual backups) after the change in ip/subnet was
> done. All backup attempts return with errrors similar to these:
> ===> 18204 :
> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
> failed to open. Operating system error = 32(The process cannot access
> the file because it is being used by another process.).
> ===> 3041 :
> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
> ===>
> When the manual backup is initiated without Verification, no (popup)
> error is generated (but the error above is still logged on the event
> log) and the backup says it ran successfully. When the backup file is
> checked, the size is Zero (0) kb.
> There is no apparent problem in connecting to both the two instances
> of the server and applications are working okay, it's just the backup
> problem that is bugging us.
> drive Q = quorum
> drive F = one of the shared drives with 20Gb+ remaining
> The database that we are attempting to backup is just about 11Gb in
> size.
>
> Any help is appreciated.
> Thanks.
>
> Aramid
>|||Thanks for your reply, Michael.
We are not backing up to any shared network drive, just to this drive,
which is one of the logical drives on an external disk array attached
to the cluster.
Aramid
On Sun, 10 Apr 2005 23:56:13 -0400, "Michael C#" <xyz@.abcdef.com>
wrote:
>Just a quick question - were you backing up to a shared network drive
>previously? What if you try backing up to the fully qualified UNC Path
>instead?
>"aramid" <aramid@.hotmail.com> wrote in message
>news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.4ax.com...
>> Hello Everyone,
>> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
>> Windows 2003 Ent) from one subnet to another. Everything went well
>> (apparently) until we realized that our backups are failing (both the
>> existing jobs and manual backups) after the change in ip/subnet was
>> done. All backup attempts return with errrors similar to these:
>> ===>> 18204 :
>> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
>> failed to open. Operating system error = 32(The process cannot access
>> the file because it is being used by another process.).
>> ===>> 3041 :
>> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
>> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
>> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
>> ===>>
>> When the manual backup is initiated without Verification, no (popup)
>> error is generated (but the error above is still logged on the event
>> log) and the backup says it ran successfully. When the backup file is
>> checked, the size is Zero (0) kb.
>> There is no apparent problem in connecting to both the two instances
>> of the server and applications are working okay, it's just the backup
>> problem that is bugging us.
>> drive Q = quorum
>> drive F = one of the shared drives with 20Gb+ remaining
>> The database that we are attempting to backup is just about 11Gb in
>> size.
>>
>> Any help is appreciated.
>> Thanks.
>>
>> Aramid
>>
>|||aramid
It seems that is permission or OS issue . We have recently moved to the
cluster and what i did in the backup script only changed the D:\ Driver
path to N:\ driver path. Run SQL Server Profile to see what is going on.
Have you searched on internet for those errors?
"aramid" <aramid@.hotmail.com> wrote in message
news:0ouj51dm2esqntk6pegt6f37m36f4g8brj@.4ax.com...
> Thanks for your reply, Michael.
> We are not backing up to any shared network drive, just to this drive,
> which is one of the logical drives on an external disk array attached
> to the cluster.
> Aramid
> On Sun, 10 Apr 2005 23:56:13 -0400, "Michael C#" <xyz@.abcdef.com>
> wrote:
> >Just a quick question - were you backing up to a shared network drive
> >previously? What if you try backing up to the fully qualified UNC Path
> >instead?
> >
> >"aramid" <aramid@.hotmail.com> wrote in message
> >news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.4ax.com...
> >> Hello Everyone,
> >>
> >> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
> >> Windows 2003 Ent) from one subnet to another. Everything went well
> >> (apparently) until we realized that our backups are failing (both the
> >> existing jobs and manual backups) after the change in ip/subnet was
> >> done. All backup attempts return with errrors similar to these:
> >>
> >> ===> >> 18204 :
> >> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
> >> failed to open. Operating system error = 32(The process cannot access
> >> the file because it is being used by another process.).
> >> ===> >> 3041 :
> >> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
> >> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
> >> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
> >> ===> >>
> >>
> >> When the manual backup is initiated without Verification, no (popup)
> >> error is generated (but the error above is still logged on the event
> >> log) and the backup says it ran successfully. When the backup file is
> >> checked, the size is Zero (0) kb.
> >>
> >> There is no apparent problem in connecting to both the two instances
> >> of the server and applications are working okay, it's just the backup
> >> problem that is bugging us.
> >>
> >> drive Q = quorum
> >> drive F = one of the shared drives with 20Gb+ remaining
> >>
> >> The database that we are attempting to backup is just about 11Gb in
> >> size.
> >>
> >>
> >> Any help is appreciated.
> >>
> >> Thanks.
> >>
> >>
> >> Aramid
> >>
> >>
> >
>|||SQL Server say that the backup file is used by some other process. I'd get a tool with which I can
check who is using the file...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"aramid" <aramid@.hotmail.com> wrote in message news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.4ax.com...
> Hello Everyone,
> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
> Windows 2003 Ent) from one subnet to another. Everything went well
> (apparently) until we realized that our backups are failing (both the
> existing jobs and manual backups) after the change in ip/subnet was
> done. All backup attempts return with errrors similar to these:
> ===> 18204 :
> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
> failed to open. Operating system error = 32(The process cannot access
> the file because it is being used by another process.).
> ===> 3041 :
> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
> ===>
> When the manual backup is initiated without Verification, no (popup)
> error is generated (but the error above is still logged on the event
> log) and the backup says it ran successfully. When the backup file is
> checked, the size is Zero (0) kb.
> There is no apparent problem in connecting to both the two instances
> of the server and applications are working okay, it's just the backup
> problem that is bugging us.
> drive Q = quorum
> drive F = one of the shared drives with 20Gb+ remaining
> The database that we are attempting to backup is just about 11Gb in
> size.
>
> Any help is appreciated.
> Thanks.
>
> Aramid
>

Backup Problem

Hello Everyone,
We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
Windows 2003 Ent) from one subnet to another. Everything went well
(apparently) until we realized that our backups are failing (both the
existing jobs and manual backups) after the change in ip/subnet was
done. All backup attempts return with errrors similar to these:
===
18204 :
BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
failed to open. Operating system error = 32(The process cannot access
the file because it is being used by another process.).
===
3041 :
BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
===
When the manual backup is initiated without Verification, no (popup)
error is generated (but the error above is still logged on the event
log) and the backup says it ran successfully. When the backup file is
checked, the size is Zero (0) kb.
There is no apparent problem in connecting to both the two instances
of the server and applications are working okay, it's just the backup
problem that is bugging us.
drive Q = quorum
drive F = one of the shared drives with 20Gb+ remaining
The database that we are attempting to backup is just about 11Gb in
size.
Any help is appreciated.
Thanks.
Aramid
Just a quick question - were you backing up to a shared network drive
previously? What if you try backing up to the fully qualified UNC Path
instead?
"aramid" <aramid@.hotmail.com> wrote in message
news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.4ax.com...
> Hello Everyone,
> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
> Windows 2003 Ent) from one subnet to another. Everything went well
> (apparently) until we realized that our backups are failing (both the
> existing jobs and manual backups) after the change in ip/subnet was
> done. All backup attempts return with errrors similar to these:
> ===
> 18204 :
> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
> failed to open. Operating system error = 32(The process cannot access
> the file because it is being used by another process.).
> ===
> 3041 :
> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
> ===
>
> When the manual backup is initiated without Verification, no (popup)
> error is generated (but the error above is still logged on the event
> log) and the backup says it ran successfully. When the backup file is
> checked, the size is Zero (0) kb.
> There is no apparent problem in connecting to both the two instances
> of the server and applications are working okay, it's just the backup
> problem that is bugging us.
> drive Q = quorum
> drive F = one of the shared drives with 20Gb+ remaining
> The database that we are attempting to backup is just about 11Gb in
> size.
>
> Any help is appreciated.
> Thanks.
>
> Aramid
>
|||Thanks for your reply, Michael.
We are not backing up to any shared network drive, just to this drive,
which is one of the logical drives on an external disk array attached
to the cluster.
Aramid
On Sun, 10 Apr 2005 23:56:13 -0400, "Michael C#" <xyz@.abcdef.com>
wrote:

>Just a quick question - were you backing up to a shared network drive
>previously? What if you try backing up to the fully qualified UNC Path
>instead?
>"aramid" <aramid@.hotmail.com> wrote in message
>news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.4ax.com.. .
>
|||aramid
It seems that is permission or OS issue . We have recently moved to the
cluster and what i did in the backup script only changed the D:\ Driver
path to N:\ driver path. Run SQL Server Profile to see what is going on.
Have you searched on internet for those errors?
"aramid" <aramid@.hotmail.com> wrote in message
news:0ouj51dm2esqntk6pegt6f37m36f4g8brj@.4ax.com...
> Thanks for your reply, Michael.
> We are not backing up to any shared network drive, just to this drive,
> which is one of the logical drives on an external disk array attached
> to the cluster.
> Aramid
> On Sun, 10 Apr 2005 23:56:13 -0400, "Michael C#" <xyz@.abcdef.com>
> wrote:
>
|||SQL Server say that the backup file is used by some other process. I'd get a tool with which I can
check who is using the file...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"aramid" <aramid@.hotmail.com> wrote in message news:s4rj511nm4jrf8at18grbsnio4jseoc7t8@.4ax.com...
> Hello Everyone,
> We were moving a 2-node DB cluster (Active/Active on SQL 2000 Ent /
> Windows 2003 Ent) from one subnet to another. Everything went well
> (apparently) until we realized that our backups are failing (both the
> existing jobs and manual backups) after the change in ip/subnet was
> done. All backup attempts return with errrors similar to these:
> ===
> 18204 :
> BackupDiskFile::OpenMedia: Backup device 'F:\temp\database_abc_041005'
> failed to open. Operating system error = 32(The process cannot access
> the file because it is being used by another process.).
> ===
> 3041 :
> BACKUP failed to complete the command BACKUP DATABASE [database_abcr]
> TO DISK = N'F:\temp\database_abc_041005' WITH NOINIT , NOUNLOAD ,
> NAME = N'database_abc backup', NOSKIP , STATS = 10, NOFORMAT
> ===
>
> When the manual backup is initiated without Verification, no (popup)
> error is generated (but the error above is still logged on the event
> log) and the backup says it ran successfully. When the backup file is
> checked, the size is Zero (0) kb.
> There is no apparent problem in connecting to both the two instances
> of the server and applications are working okay, it's just the backup
> problem that is bugging us.
> drive Q = quorum
> drive F = one of the shared drives with 20Gb+ remaining
> The database that we are attempting to backup is just about 11Gb in
> size.
>
> Any help is appreciated.
> Thanks.
>
> Aramid
>

Backup of active log after db failure

Greetings,
I am seeking information related to this subject.

BOL suggests backing up the active transaction log immediately after a
failure, so that the backup can be used in a recovery scenario if necessary.

This is the relevant text from BOL "Transaction Log Backup":

--//
The transaction log backup created at 8:00 P.M. contains transaction log
records from 4:00 P.M. through 8:00 P.M., spanning the time when the
database backup was created at 6:00 P.M. The sequence of transaction log
backups is continuous from the initial database backup created at 8:00 A.M.
to the last transaction log backup created at 8:00 P.M. The following
procedures can be used to restore the database to its state at 10:00 P.M.
(point of failure).

Restore the database using the last database backup created.

1.. Create a backup of the currently active transaction log.

--// end of excerpt

If the failure results in loss of the instance and/or the log's parent db,
how would we back up that log? Even if we could, what confidence would we
have that the backed up log was not corrupted at failure time?

Thanks,
PSGThe standard configuration when loss of transactions is unacceptable:
put the log disk on a separate disk from the data. And mirror the log disk.

You would have to trust (hope) that your log disk didn't suffer loss of
data. That's the point of the mirroring.

If the instance was lost, then you'd have to rebuild/restore master before
you'd be able to issue the
BACKUP LOG WITH NO_TRUNCATE to harvest the tail of the log.

"JustaCowboy" <ppgoodingNOSPAM@.rocketmail.com> wrote in message
news:blj1rd$v1g$0@.pita.alt.net...
<snip
> If the failure results in loss of the instance and/or the log's parent db,
> how would we back up that log? Even if we could, what confidence would we
> have that the backed up log was not corrupted at failure time?
> Thanks,
> PSG|||"Anonymous" <noone@.anon.com> wrote in message
news:3f7f1411$1@.news.microsoft.com...
> The standard configuration when loss of transactions is unacceptable:
> put the log disk on a separate disk from the data. And mirror the log
disk.

Yes.

> You would have to trust (hope) that your log disk didn't suffer loss of
> data. That's the point of the mirroring.

Yes.

> If the instance was lost, then you'd have to rebuild/restore master before
> you'd be able to issue the
> BACKUP LOG WITH NO_TRUNCATE to harvest the tail of the log.

Will SQL backup an unattached log file? If not, to what is the harvested
log attached? I am having trouble understanding the steps that would lead
to being able to backup that log unless SQL will back it up unattached.
Has anyone actually tried the scenario described in BOL?

A local has suggested to me that we frequently back up the log and copy the
backups (along with the preceeding full db backup) to disk or device
external to the subject server. If this log backup/copy were done every 15
mins, then presumably no more than 15 mins' work would be lost after a
failure. Our assumption right now is that the BOL suggestion just won't
work. We'd try simulating it if we thought the simulation were valid, but
that seems very doubtful.

thanks,
PG

backup issue

To all,
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
JosieJosie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

backup issue

To all,
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
Josie
Josie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

backup issue

To all,
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
JosieJosie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Backup Followed by Crash

Hi. I have a SQL Server 2000 server that runs backups
every night on a handful of not very active databases.
Recently, the server has crashed or hung each time,
following successful backup of all but the last database.
No error message, no warning. The system log shows a
successful completion of the next-to-last backup. About
six seconds later (usually) there is a system time stamp
in the security log. Then the system just checks out,
sometimes powered down, sometimes hung but still powered
on. I have to manually reboot the system.
Any suggestions on how to track down the problem?
Thanks!
Nora Miller
Portland OR
NMiller,
What's in your
* SQL Server error log
* Windows Appication event log
* Windows System event log
Post relevant entries here. Do you have enough disk space? Where are you
backing up to? It could be a driver problem if using a tape device.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
NMiller wrote:
> Hi. I have a SQL Server 2000 server that runs backups
> every night on a handful of not very active databases.
> Recently, the server has crashed or hung each time,
> following successful backup of all but the last database.
> No error message, no warning. The system log shows a
> successful completion of the next-to-last backup. About
> six seconds later (usually) there is a system time stamp
> in the security log. Then the system just checks out,
> sometimes powered down, sometimes hung but still powered
> on. I have to manually reboot the system.
> Any suggestions on how to track down the problem?
> Thanks!
> Nora Miller
> Portland OR