Hi, everyday an automated backup is done of my content database and when i
checked today to ensure the job went thru, I realized it failed.
I get the error msg:
"A nonrecoverable I/O error occured on file
"\\tcl-fileserver3\backups\moss\daily"
The specified network name is no longer available. Error: 3013"
I created a new file and did a backup to that file
"\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
then renamed the original file and did a backup and that went thru......
Is it possible that a file name can be corrupted? The original backup path
was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
"\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
fine......
What could be the issue here?
When you say the remote server, you are referring to the server where i am
backing up the information to?
Also, I didn't change the time in the schedule, I just changed the name of
the file and it worked......
What could cause this?
"Des FitzGerald" wrote:
> Hi Shelly,
> I think this points to a problem with either the network connection at the
> scheduled time of the backup or to over processing on the remote network
> server you are sending the backup to at the time of the schedule.
> Could it be that this remote server is under heavy load during the backup?
> If so perhaps changing the time of the schedule if possible may help.
> Kind Regards,
> Des
>
> On 08/01/2008 16:09, in article
> ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
> <Shelley@.discussions.microsoft.com> wrote:
>
>
>
|||Hi, thanks so much for your help.
I renamed the file, but left the schedule the same and the backup went thru.
Still not sure what the exact problem was since this was the first time this
ever happened; have been doing the automated backups for about a month now.
Thanks again,
Shelley
"Des FitzGerald" wrote:
> The remote server is where you are backing up your database to - in this
> case \\tcl-fileserver
> I am thinking that this server was under load when your normal scheduled
> nightly execution took place and this may have caused the problem or perhaps
> there was an intermittent network problem at the time.
> Both these scenarios are possibilities as to why you have seen this issue,
> the file name may have become corrupt because of the I/O problems on the
> server, I would look at the time of the schedule and see if other heavy
> processing is occurring on your remote backup location and change the time
> if possible of the schedule so it executes when the server is under less
> strain.
> Alternatively if this happened only once out of 100 runs of the schedule it
> may just be bad luck and the schedule can remain. It would also be possible
> to write a check before starting the backup to make sure the file exists and
> can be reached and that all looks OK.
> Cheers,
> Des
> On 08/01/2008 16:31, in article
> 62B77DBE-316A-4C5F-AAAB-AD1B9E1AB994@.microsoft.com, "Shelley"
> <Shelley@.discussions.microsoft.com> wrote:
>
>
Showing posts with label automated. Show all posts
Showing posts with label automated. Show all posts
Tuesday, March 27, 2012
Backup failed - Error 3013
Hi, everyday an automated backup is done of my content database and when i
checked today to ensure the job went thru, I realized it failed.
I get the error msg:
"A nonrecoverable I/O error occured on file
"\\tcl-fileserver3\backups\moss\daily"
The specified network name is no longer available. Error: 3013"
I created a new file and did a backup to that file
"\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
then renamed the original file and did a backup and that went thru......
Is it possible that a file name can be corrupted? The original backup path
was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
"\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
fine......
What could be the issue here?Hi Shelly,
I think this points to a problem with either the network connection at the
scheduled time of the backup or to over processing on the remote network
server you are sending the backup to at the time of the schedule.
Could it be that this remote server is under heavy load during the backup?
If so perhaps changing the time of the schedule if possible may help.
Kind Regards,
Des
On 08/01/2008 16:09, in article
ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
<Shelley@.discussions.microsoft.com> wrote:
> Hi, everyday an automated backup is done of my content database and when i
> checked today to ensure the job went thru, I realized it failed.
> I get the error msg:
> "A nonrecoverable I/O error occured on file
> "\\tcl-fileserver3\backups\moss\daily"
> The specified network name is no longer available. Error: 3013"
> I created a new file and did a backup to that file
> "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
> then renamed the original file and did a backup and that went thru......
> Is it possible that a file name can be corrupted? The original backup path
> was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
> "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
> fine......
> What could be the issue here?|||When you say the remote server, you are referring to the server where i am
backing up the information to?
Also, I didn't change the time in the schedule, I just changed the name of
the file and it worked......
What could cause this?
"Des FitzGerald" wrote:
> Hi Shelly,
> I think this points to a problem with either the network connection at the
> scheduled time of the backup or to over processing on the remote network
> server you are sending the backup to at the time of the schedule.
> Could it be that this remote server is under heavy load during the backup?
> If so perhaps changing the time of the schedule if possible may help.
> Kind Regards,
> Des
>
> On 08/01/2008 16:09, in article
> ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
> <Shelley@.discussions.microsoft.com> wrote:
> > Hi, everyday an automated backup is done of my content database and when i
> > checked today to ensure the job went thru, I realized it failed.
> > I get the error msg:
> > "A nonrecoverable I/O error occured on file
> > "\\tcl-fileserver3\backups\moss\daily"
> > The specified network name is no longer available. Error: 3013"
> > I created a new file and did a backup to that file
> > "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
> > then renamed the original file and did a backup and that went thru......
> > Is it possible that a file name can be corrupted? The original backup path
> > was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
> > "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
> > fine......
> > What could be the issue here?
>
>
>|||The remote server is where you are backing up your database to - in this
case \\tcl-fileserver
I am thinking that this server was under load when your normal scheduled
nightly execution took place and this may have caused the problem or perhaps
there was an intermittent network problem at the time.
Both these scenarios are possibilities as to why you have seen this issue,
the file name may have become corrupt because of the I/O problems on the
server, I would look at the time of the schedule and see if other heavy
processing is occurring on your remote backup location and change the time
if possible of the schedule so it executes when the server is under less
strain.
Alternatively if this happened only once out of 100 runs of the schedule it
may just be bad luck and the schedule can remain. It would also be possible
to write a check before starting the backup to make sure the file exists and
can be reached and that all looks OK.
Cheers,
Des
On 08/01/2008 16:31, in article
62B77DBE-316A-4C5F-AAAB-AD1B9E1AB994@.microsoft.com, "Shelley"
<Shelley@.discussions.microsoft.com> wrote:
> When you say the remote server, you are referring to the server where i am
> backing up the information to?
> Also, I didn't change the time in the schedule, I just changed the name of
> the file and it worked......
> What could cause this?
> "Des FitzGerald" wrote:
>> Hi Shelly,
>> I think this points to a problem with either the network connection at the
>> scheduled time of the backup or to over processing on the remote network
>> server you are sending the backup to at the time of the schedule.
>> Could it be that this remote server is under heavy load during the backup?
>> If so perhaps changing the time of the schedule if possible may help.
>> Kind Regards,
>> Des
>>
>> On 08/01/2008 16:09, in article
>> ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
>> <Shelley@.discussions.microsoft.com> wrote:
>> Hi, everyday an automated backup is done of my content database and when i
>> checked today to ensure the job went thru, I realized it failed.
>> I get the error msg:
>> "A nonrecoverable I/O error occured on file
>> "\\tcl-fileserver3\backups\moss\daily"
>> The specified network name is no longer available. Error: 3013"
>> I created a new file and did a backup to that file
>> "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
>> then renamed the original file and did a backup and that went thru......
>> Is it possible that a file name can be corrupted? The original backup path
>> was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
>> "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
>> fine......
>> What could be the issue here?
>>
>>|||Hi, thanks so much for your help.
I renamed the file, but left the schedule the same and the backup went thru.
Still not sure what the exact problem was since this was the first time this
ever happened; have been doing the automated backups for about a month now.
Thanks again,
Shelley
"Des FitzGerald" wrote:
> The remote server is where you are backing up your database to - in this
> case \\tcl-fileserver
> I am thinking that this server was under load when your normal scheduled
> nightly execution took place and this may have caused the problem or perhaps
> there was an intermittent network problem at the time.
> Both these scenarios are possibilities as to why you have seen this issue,
> the file name may have become corrupt because of the I/O problems on the
> server, I would look at the time of the schedule and see if other heavy
> processing is occurring on your remote backup location and change the time
> if possible of the schedule so it executes when the server is under less
> strain.
> Alternatively if this happened only once out of 100 runs of the schedule it
> may just be bad luck and the schedule can remain. It would also be possible
> to write a check before starting the backup to make sure the file exists and
> can be reached and that all looks OK.
> Cheers,
> Des
> On 08/01/2008 16:31, in article
> 62B77DBE-316A-4C5F-AAAB-AD1B9E1AB994@.microsoft.com, "Shelley"
> <Shelley@.discussions.microsoft.com> wrote:
> > When you say the remote server, you are referring to the server where i am
> > backing up the information to?
> > Also, I didn't change the time in the schedule, I just changed the name of
> > the file and it worked......
> > What could cause this?
> >
> > "Des FitzGerald" wrote:
> >
> >> Hi Shelly,
> >>
> >> I think this points to a problem with either the network connection at the
> >> scheduled time of the backup or to over processing on the remote network
> >> server you are sending the backup to at the time of the schedule.
> >>
> >> Could it be that this remote server is under heavy load during the backup?
> >>
> >> If so perhaps changing the time of the schedule if possible may help.
> >>
> >> Kind Regards,
> >> Des
> >>
> >>
> >>
> >> On 08/01/2008 16:09, in article
> >> ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
> >> <Shelley@.discussions.microsoft.com> wrote:
> >>
> >> Hi, everyday an automated backup is done of my content database and when i
> >> checked today to ensure the job went thru, I realized it failed.
> >> I get the error msg:
> >> "A nonrecoverable I/O error occured on file
> >> "\\tcl-fileserver3\backups\moss\daily"
> >> The specified network name is no longer available. Error: 3013"
> >> I created a new file and did a backup to that file
> >> "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
> >> then renamed the original file and did a backup and that went thru......
> >> Is it possible that a file name can be corrupted? The original backup path
> >> was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
> >> "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
> >> fine......
> >> What could be the issue here?
> >>
> >>
> >>
> >>
> >>
>
>sql
checked today to ensure the job went thru, I realized it failed.
I get the error msg:
"A nonrecoverable I/O error occured on file
"\\tcl-fileserver3\backups\moss\daily"
The specified network name is no longer available. Error: 3013"
I created a new file and did a backup to that file
"\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
then renamed the original file and did a backup and that went thru......
Is it possible that a file name can be corrupted? The original backup path
was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
"\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
fine......
What could be the issue here?Hi Shelly,
I think this points to a problem with either the network connection at the
scheduled time of the backup or to over processing on the remote network
server you are sending the backup to at the time of the schedule.
Could it be that this remote server is under heavy load during the backup?
If so perhaps changing the time of the schedule if possible may help.
Kind Regards,
Des
On 08/01/2008 16:09, in article
ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
<Shelley@.discussions.microsoft.com> wrote:
> Hi, everyday an automated backup is done of my content database and when i
> checked today to ensure the job went thru, I realized it failed.
> I get the error msg:
> "A nonrecoverable I/O error occured on file
> "\\tcl-fileserver3\backups\moss\daily"
> The specified network name is no longer available. Error: 3013"
> I created a new file and did a backup to that file
> "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
> then renamed the original file and did a backup and that went thru......
> Is it possible that a file name can be corrupted? The original backup path
> was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
> "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
> fine......
> What could be the issue here?|||When you say the remote server, you are referring to the server where i am
backing up the information to?
Also, I didn't change the time in the schedule, I just changed the name of
the file and it worked......
What could cause this?
"Des FitzGerald" wrote:
> Hi Shelly,
> I think this points to a problem with either the network connection at the
> scheduled time of the backup or to over processing on the remote network
> server you are sending the backup to at the time of the schedule.
> Could it be that this remote server is under heavy load during the backup?
> If so perhaps changing the time of the schedule if possible may help.
> Kind Regards,
> Des
>
> On 08/01/2008 16:09, in article
> ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
> <Shelley@.discussions.microsoft.com> wrote:
> > Hi, everyday an automated backup is done of my content database and when i
> > checked today to ensure the job went thru, I realized it failed.
> > I get the error msg:
> > "A nonrecoverable I/O error occured on file
> > "\\tcl-fileserver3\backups\moss\daily"
> > The specified network name is no longer available. Error: 3013"
> > I created a new file and did a backup to that file
> > "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
> > then renamed the original file and did a backup and that went thru......
> > Is it possible that a file name can be corrupted? The original backup path
> > was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
> > "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
> > fine......
> > What could be the issue here?
>
>
>|||The remote server is where you are backing up your database to - in this
case \\tcl-fileserver
I am thinking that this server was under load when your normal scheduled
nightly execution took place and this may have caused the problem or perhaps
there was an intermittent network problem at the time.
Both these scenarios are possibilities as to why you have seen this issue,
the file name may have become corrupt because of the I/O problems on the
server, I would look at the time of the schedule and see if other heavy
processing is occurring on your remote backup location and change the time
if possible of the schedule so it executes when the server is under less
strain.
Alternatively if this happened only once out of 100 runs of the schedule it
may just be bad luck and the schedule can remain. It would also be possible
to write a check before starting the backup to make sure the file exists and
can be reached and that all looks OK.
Cheers,
Des
On 08/01/2008 16:31, in article
62B77DBE-316A-4C5F-AAAB-AD1B9E1AB994@.microsoft.com, "Shelley"
<Shelley@.discussions.microsoft.com> wrote:
> When you say the remote server, you are referring to the server where i am
> backing up the information to?
> Also, I didn't change the time in the schedule, I just changed the name of
> the file and it worked......
> What could cause this?
> "Des FitzGerald" wrote:
>> Hi Shelly,
>> I think this points to a problem with either the network connection at the
>> scheduled time of the backup or to over processing on the remote network
>> server you are sending the backup to at the time of the schedule.
>> Could it be that this remote server is under heavy load during the backup?
>> If so perhaps changing the time of the schedule if possible may help.
>> Kind Regards,
>> Des
>>
>> On 08/01/2008 16:09, in article
>> ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
>> <Shelley@.discussions.microsoft.com> wrote:
>> Hi, everyday an automated backup is done of my content database and when i
>> checked today to ensure the job went thru, I realized it failed.
>> I get the error msg:
>> "A nonrecoverable I/O error occured on file
>> "\\tcl-fileserver3\backups\moss\daily"
>> The specified network name is no longer available. Error: 3013"
>> I created a new file and did a backup to that file
>> "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
>> then renamed the original file and did a backup and that went thru......
>> Is it possible that a file name can be corrupted? The original backup path
>> was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
>> "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
>> fine......
>> What could be the issue here?
>>
>>|||Hi, thanks so much for your help.
I renamed the file, but left the schedule the same and the backup went thru.
Still not sure what the exact problem was since this was the first time this
ever happened; have been doing the automated backups for about a month now.
Thanks again,
Shelley
"Des FitzGerald" wrote:
> The remote server is where you are backing up your database to - in this
> case \\tcl-fileserver
> I am thinking that this server was under load when your normal scheduled
> nightly execution took place and this may have caused the problem or perhaps
> there was an intermittent network problem at the time.
> Both these scenarios are possibilities as to why you have seen this issue,
> the file name may have become corrupt because of the I/O problems on the
> server, I would look at the time of the schedule and see if other heavy
> processing is occurring on your remote backup location and change the time
> if possible of the schedule so it executes when the server is under less
> strain.
> Alternatively if this happened only once out of 100 runs of the schedule it
> may just be bad luck and the schedule can remain. It would also be possible
> to write a check before starting the backup to make sure the file exists and
> can be reached and that all looks OK.
> Cheers,
> Des
> On 08/01/2008 16:31, in article
> 62B77DBE-316A-4C5F-AAAB-AD1B9E1AB994@.microsoft.com, "Shelley"
> <Shelley@.discussions.microsoft.com> wrote:
> > When you say the remote server, you are referring to the server where i am
> > backing up the information to?
> > Also, I didn't change the time in the schedule, I just changed the name of
> > the file and it worked......
> > What could cause this?
> >
> > "Des FitzGerald" wrote:
> >
> >> Hi Shelly,
> >>
> >> I think this points to a problem with either the network connection at the
> >> scheduled time of the backup or to over processing on the remote network
> >> server you are sending the backup to at the time of the schedule.
> >>
> >> Could it be that this remote server is under heavy load during the backup?
> >>
> >> If so perhaps changing the time of the schedule if possible may help.
> >>
> >> Kind Regards,
> >> Des
> >>
> >>
> >>
> >> On 08/01/2008 16:09, in article
> >> ED8CA9B6-4896-4E15-BC4A-1DA86CDDCD03@.microsoft.com, "Shelley"
> >> <Shelley@.discussions.microsoft.com> wrote:
> >>
> >> Hi, everyday an automated backup is done of my content database and when i
> >> checked today to ensure the job went thru, I realized it failed.
> >> I get the error msg:
> >> "A nonrecoverable I/O error occured on file
> >> "\\tcl-fileserver3\backups\moss\daily"
> >> The specified network name is no longer available. Error: 3013"
> >> I created a new file and did a backup to that file
> >> "\\tcl-fileserver3\backups\moss\testing" and the backup went thru fine. I
> >> then renamed the original file and did a backup and that went thru......
> >> Is it possible that a file name can be corrupted? The original backup path
> >> was "\\tcl-fileserver3\backups\moss\daily" I renamed that file to:
> >> "\\tcl-fileserver3\backups\moss\daily_testing" and the backup went thru
> >> fine......
> >> What could be the issue here?
> >>
> >>
> >>
> >>
> >>
>
>sql
Thursday, March 8, 2012
Backup and Restore using VBScript (ActiveX)
We are trying to setup a central job server that will perform the backups, restores, and other automated tasks for all of our SQL servers. The goal is that we have one place to check the status of all of our jobs. I have a couple of problems, though.
The first is that, to backup a database on a remote server, we are using VBScript as an ActiveX Script type of step. The script uses SQLDMO. The jobs mostly run fine, but there seems to be a problem with concurrent jobs running against the same server. For instance, I have 4 backup jobs that I kick off at 7:00PM. One of them (not always the same one) will fail with:
Error Code: 0 Error Source= Microsoft SQL-DMO Error Description: [SQL-DMO]The application is busy. Error on Line 11. The step failed.
The databses are all quite small (master, msdb, and a couple of utility dbs we have). Are there threading issues in using SQL-DMO such that I can't run jobs concurrently? The remote server is SQL2000, so I don't believe I can use SMO. My script is at the end of this post.
My second problem is trying to remotely kick off a restore. Currently, when using the local scheduler, we use the RESTORE DATABASE command right after an ALTER DATABASE SET SINGLE_USER WITH ROLLBACK IMMEDIATE command. This command is necessary to kill any processes currently using the DB so that a restore will succeed. In DMO I can't find anyway to duplicate this functionality. Any ideas?
Thanks
Steve
-- Backup Script --
Dim sServer, sDatabase, sPath, sDumpFile, oSQLServer, oBackup
sServer = "PRDSQL01"
sDatabase = "master"
sPath = "E:\MSSQL\DUMP\"
sDumpFile = "master.dmp"
Set oSQLServer = CreateObject("SQLDMO.SQLServer")
Set oBackup = CreateObject("SQLDMO.BackUp")
oSQLServer.loginsecure = true
oSQLServer.Connect sServer
oBackup.Database = sDatabase
oBackup.Files = sPath & sDumpFile
oBackUp.BackupSetDescription = "Backup - " & sDatabase
oBackup.Initialize = "TRUE"
oBackup.SQLBackup oSQLServer
oSQLServer.Disconnect
Set sServer = nothing
Set sDatabase = nothing
Set sPath = nothing
Set sDumpFile = nothing
Set oSQLServer = nothing
Set oBackup = nothing
Hi Stev
Vimal , here ,
sir its helpful to take backup ,please tell me script for restore the taken dump file.
Vimal
Backup and Restore using VBScript (ActiveX)
We are trying to setup a central job server that will perform the backups, restores, and other automated tasks for all of our SQL servers. The goal is that we have one place to check the status of all of our jobs. I have a couple of problems, though.
The first is that, to backup a database on a remote server, we are using VBScript as an ActiveX Script type of step. The script uses SQLDMO. The jobs mostly run fine, but there seems to be a problem with concurrent jobs running against the same server. For instance, I have 4 backup jobs that I kick off at 7:00PM. One of them (not always the same one) will fail with:
Error Code: 0 Error Source= Microsoft SQL-DMO Error Description: [SQL-DMO]The application is busy. Error on Line 11. The step failed.
The databses are all quite small (master, msdb, and a couple of utility dbs we have). Are there threading issues in using SQL-DMO such that I can't run jobs concurrently? The remote server is SQL2000, so I don't believe I can use SMO. My script is at the end of this post.
My second problem is trying to remotely kick off a restore. Currently, when using the local scheduler, we use the RESTORE DATABASE command right after an ALTER DATABASE SET SINGLE_USER WITH ROLLBACK IMMEDIATE command. This command is necessary to kill any processes currently using the DB so that a restore will succeed. In DMO I can't find anyway to duplicate this functionality. Any ideas?
Thanks
Steve
-- Backup Script --
Dim sServer, sDatabase, sPath, sDumpFile, oSQLServer, oBackup
sServer = "PRDSQL01"
sDatabase = "master"
sPath = "E:\MSSQL\DUMP\"
sDumpFile = "master.dmp"
Set oSQLServer = CreateObject("SQLDMO.SQLServer")
Set oBackup = CreateObject("SQLDMO.BackUp")
oSQLServer.loginsecure = true
oSQLServer.Connect sServer
oBackup.Database = sDatabase
oBackup.Files = sPath & sDumpFile
oBackUp.BackupSetDescription = "Backup - " & sDatabase
oBackup.Initialize = "TRUE"
oBackup.SQLBackup oSQLServer
oSQLServer.Disconnect
Set sServer = nothing
Set sDatabase = nothing
Set sPath = nothing
Set sDumpFile = nothing
Set oSQLServer = nothing
Set oBackup = nothing
Hi Stev
Vimal , here ,
sir its helpful to take backup ,please tell me script for restore the taken dump file.
Vimal
Subscribe to:
Posts (Atom)