He evryone
I need help about backup. I have a several questions about this
situation.
In Database Maintenance Plan i created plan for backup some database.
BackUp occurs every day at 01.00h, on disk to some directory on the
network. I checked option Remove files older then
(3 days). DMPlan created for me job that works backup. Job creates new
bak file every day and remove files older than 3 days. So, i always have
3 .bak files in the backup directory.
But if I create job by myself with standard backup statement (back up
database ...) , i can put with noinit option so i will append .bak file
to .bak file and i will have only one file in backup directory.
1) If i use the DMPlan how can i use with noinit option?
2) If i use BackUp Database statement how can i remove files older than
some days?
3) What is better solution, keep 3 or more diferent .bak files or only
one with noinit option?
Thanks
Alex
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!acko
http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1
--administaiting best practices
"acko bogicevic" <aconi2002@.yahoo.com> wrote in message
news:eDKcIMe#DHA.220@.TK2MSFTNGP09.phx.gbl...
> He evryone
> I need help about backup. I have a several questions about this
> situation.
> In Database Maintenance Plan i created plan for backup some database.
> BackUp occurs every day at 01.00h, on disk to some directory on the
> network. I checked option Remove files older then
> (3 days). DMPlan created for me job that works backup. Job creates new
> bak file every day and remove files older than 3 days. So, i always have
> 3 .bak files in the backup directory.
> But if I create job by myself with standard backup statement (back up
> database ...) , i can put with noinit option so i will append .bak file
> to .bak file and i will have only one file in backup directory.
> 1) If i use the DMPlan how can i use with noinit option?
> 2) If i use BackUp Database statement how can i remove files older than
> some days?
> 3) What is better solution, keep 3 or more diferent .bak files or only
> one with noinit option?
> Thanks
> Alex
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!
Showing posts with label situation. Show all posts
Showing posts with label situation. Show all posts
Tuesday, March 20, 2012
Sunday, March 11, 2012
backup problem 2
Has anyone encountered a situation where the backup process is still
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
AramidHi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:
> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
>Hi
>Run sp_who2 during the process. You will see if the backup is still running.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
>> Has anyone encountered a situation where the backup process is still
>> running but Enterprise Manager already says that it was finished and
>> was successful.
>> I initiated a backup to a UNC share (but the actual drive is directly
>> attached to the server) and the backup started. I see the size of the
>> backup file increasing (via Windows Explorer) so I assumed everything
>> is okay. After about 10% was done, EM suddenly showed me the usual
>> "The backup operation has completed successfully" window, but the size
>> of the backup file continued increasing...and apparently went on an
>> on, up to the expected size of the backup. Upon checking (restore),
>> the backup file was okay.
>> Has anyone encountered a similar situation? Any thoughts on this?
>>
>> Aramid|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK => N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME => N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
> >Hi
> >
> >Run sp_who2 during the process. You will see if the backup is still
running.
> >What does the job history say about the run time? Does it match the file
> >datetime stamp?
> >
> >Regards
> >Mike
> >
> >
> >"aramid" wrote:
> >
> >> Has anyone encountered a situation where the backup process is still
> >> running but Enterprise Manager already says that it was finished and
> >> was successful.
> >>
> >> I initiated a backup to a UNC share (but the actual drive is directly
> >> attached to the server) and the backup started. I see the size of the
> >> backup file increasing (via Windows Explorer) so I assumed everything
> >> is okay. After about 10% was done, EM suddenly showed me the usual
> >> "The backup operation has completed successfully" window, but the size
> >> of the backup file continued increasing...and apparently went on an
> >> on, up to the expected size of the backup. Upon checking (restore),
> >> the backup file was okay.
> >>
> >> Has anyone encountered a similar situation? Any thoughts on this?
> >>
> >>
> >> Aramid
> >>
>|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:
>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
>news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
>> Thanks, Mike.
>> I did monitor the backup process via sp_who2 and also did a TSQL
>> backup via QA as:
>> BACKUP DATABASE [database_namer] TO DISK =>> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =>> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
>> After about 1 minute, the error below shows up in QA:
>> =====>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
>> (WrapperRead()).
>> Server: Msg 11, Level 16, State 1, Line 0
>> General network error. Check your network documentation.
>> 10 percent backed up.
>> Connection Broken
>> =====>> Running sp_who2 shows that my QA connection still exists and is
>> running. The backup eventually completes without any problem from
>> this point onwards.
>> I did this several times, just to check if the pattern is consistent,
>> and it is. I also noticed that running something else on the QA
>> window (after the error has showed itself) where I ran the backup
>> command will immediately stop the "background backup" (tantamount to
>> killing the spid) and execute my new command (such as sp_who2).
>> Note that I am using the QA on the server itself, not from some remote
>> machine.
>> Aramid
>>
>> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
>> <mike@.epprecht.net> wrote:
>> >Hi
>> >
>> >Run sp_who2 during the process. You will see if the backup is still
>running.
>> >What does the job history say about the run time? Does it match the file
>> >datetime stamp?
>> >
>> >Regards
>> >Mike
>> >
>> >
>> >"aramid" wrote:
>> >
>> >> Has anyone encountered a situation where the backup process is still
>> >> running but Enterprise Manager already says that it was finished and
>> >> was successful.
>> >>
>> >> I initiated a backup to a UNC share (but the actual drive is directly
>> >> attached to the server) and the backup started. I see the size of the
>> >> backup file increasing (via Windows Explorer) so I assumed everything
>> >> is okay. After about 10% was done, EM suddenly showed me the usual
>> >> "The backup operation has completed successfully" window, but the size
>> >> of the backup file continued increasing...and apparently went on an
>> >> on, up to the expected size of the backup. Upon checking (restore),
>> >> the backup file was okay.
>> >>
>> >> Has anyone encountered a similar situation? Any thoughts on this?
>> >>
>> >>
>> >> Aramid
>> >>
>
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
AramidHi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:
> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
>Hi
>Run sp_who2 during the process. You will see if the backup is still running.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
>> Has anyone encountered a situation where the backup process is still
>> running but Enterprise Manager already says that it was finished and
>> was successful.
>> I initiated a backup to a UNC share (but the actual drive is directly
>> attached to the server) and the backup started. I see the size of the
>> backup file increasing (via Windows Explorer) so I assumed everything
>> is okay. After about 10% was done, EM suddenly showed me the usual
>> "The backup operation has completed successfully" window, but the size
>> of the backup file continued increasing...and apparently went on an
>> on, up to the expected size of the backup. Upon checking (restore),
>> the backup file was okay.
>> Has anyone encountered a similar situation? Any thoughts on this?
>>
>> Aramid|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK => N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME => N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
> >Hi
> >
> >Run sp_who2 during the process. You will see if the backup is still
running.
> >What does the job history say about the run time? Does it match the file
> >datetime stamp?
> >
> >Regards
> >Mike
> >
> >
> >"aramid" wrote:
> >
> >> Has anyone encountered a situation where the backup process is still
> >> running but Enterprise Manager already says that it was finished and
> >> was successful.
> >>
> >> I initiated a backup to a UNC share (but the actual drive is directly
> >> attached to the server) and the backup started. I see the size of the
> >> backup file increasing (via Windows Explorer) so I assumed everything
> >> is okay. After about 10% was done, EM suddenly showed me the usual
> >> "The backup operation has completed successfully" window, but the size
> >> of the backup file continued increasing...and apparently went on an
> >> on, up to the expected size of the backup. Upon checking (restore),
> >> the backup file was okay.
> >>
> >> Has anyone encountered a similar situation? Any thoughts on this?
> >>
> >>
> >> Aramid
> >>
>|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:
>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
>news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
>> Thanks, Mike.
>> I did monitor the backup process via sp_who2 and also did a TSQL
>> backup via QA as:
>> BACKUP DATABASE [database_namer] TO DISK =>> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =>> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
>> After about 1 minute, the error below shows up in QA:
>> =====>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
>> (WrapperRead()).
>> Server: Msg 11, Level 16, State 1, Line 0
>> General network error. Check your network documentation.
>> 10 percent backed up.
>> Connection Broken
>> =====>> Running sp_who2 shows that my QA connection still exists and is
>> running. The backup eventually completes without any problem from
>> this point onwards.
>> I did this several times, just to check if the pattern is consistent,
>> and it is. I also noticed that running something else on the QA
>> window (after the error has showed itself) where I ran the backup
>> command will immediately stop the "background backup" (tantamount to
>> killing the spid) and execute my new command (such as sp_who2).
>> Note that I am using the QA on the server itself, not from some remote
>> machine.
>> Aramid
>>
>> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
>> <mike@.epprecht.net> wrote:
>> >Hi
>> >
>> >Run sp_who2 during the process. You will see if the backup is still
>running.
>> >What does the job history say about the run time? Does it match the file
>> >datetime stamp?
>> >
>> >Regards
>> >Mike
>> >
>> >
>> >"aramid" wrote:
>> >
>> >> Has anyone encountered a situation where the backup process is still
>> >> running but Enterprise Manager already says that it was finished and
>> >> was successful.
>> >>
>> >> I initiated a backup to a UNC share (but the actual drive is directly
>> >> attached to the server) and the backup started. I see the size of the
>> >> backup file increasing (via Windows Explorer) so I assumed everything
>> >> is okay. After about 10% was done, EM suddenly showed me the usual
>> >> "The backup operation has completed successfully" window, but the size
>> >> of the backup file continued increasing...and apparently went on an
>> >> on, up to the expected size of the backup. Upon checking (restore),
>> >> the backup file was okay.
>> >>
>> >> Has anyone encountered a similar situation? Any thoughts on this?
>> >>
>> >>
>> >> Aramid
>> >>
>
backup problem 2
Has anyone encountered a situation where the backup process is still
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
AramidHi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:
> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =
N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
[vbcol=seagreen]
>Hi
>Run sp_who2 during the process. You will see if the backup is still running
.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
>|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/defaul...kb;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.
4ax.com ?...
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK =
> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====
> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
>
running.[vbcol=seagreen]
>|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:
>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/defaul...kb;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
> news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.
4ax.com ?...
>running.
>
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
AramidHi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:
> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =
N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
[vbcol=seagreen]
>Hi
>Run sp_who2 during the process. You will see if the backup is still running
.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
>|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/defaul...kb;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.
4ax.com ?...
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK =
> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====
> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
>
running.[vbcol=seagreen]
>|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:
>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/defaul...kb;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
> news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.
4ax.com ?...
>running.
>
backup problem 2
Has anyone encountered a situation where the backup process is still
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
Aramid
Hi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:
> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>
|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =
N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
[vbcol=seagreen]
>Hi
>Run sp_who2 during the process. You will see if the backup is still running.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/default...b;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...[vbcol=seagreen]
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK =
> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====
> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
running.
>
|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:
>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/default...b;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
>news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
>running.
>
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
Aramid
Hi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:
> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>
|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =
N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
[vbcol=seagreen]
>Hi
>Run sp_who2 during the process. You will see if the backup is still running.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/default...b;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...[vbcol=seagreen]
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK =
> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====
> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
running.
>
|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:
>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/default...b;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
>news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
>running.
>
Subscribe to:
Posts (Atom)