Is there a way to to set a sql single stream job to rerun twice. I know how to set the master server to rerun jobs twice however the issue with when our sql backups run there is the main stream(full) which calls a bunch of other streams(each individual db backup) If one individual stream fails the overall status of the main stream will be a "1" but that individual db backup stream will have a failure status. For example main stream calls 6 individual streams. They all run successfully except one individual stream which gets a error "25" and the overall main stream gets a 1 but we miss a single stream db backup.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Rerun SQL Jobs Twice 3
- Thread starter smicro
- Start date
-
1
- #2
- Thread starter
- #3
Thanks Bob,
Yeah the only problem having there is some of these sql servers are "locked down" and access is limited but I agree with you we can have the DBAs just rerun the stream from the gui. This all startedstatus 25 socket errors with no reasoning(happens day,night, not everyday, not same client, etc. We found a sqlservr.exe process running on one of the sql servers taking 2gb of memory, the client had 4 total but we dont know for sure yet if that was the issue. Thanks!
Yeah the only problem having there is some of these sql servers are "locked down" and access is limited but I agree with you we can have the DBAs just rerun the stream from the gui. This all startedstatus 25 socket errors with no reasoning(happens day,night, not everyday, not same client, etc. We found a sqlservr.exe process running on one of the sql servers taking 2gb of memory, the client had 4 total but we dont know for sure yet if that was the issue. Thanks!
-
1
- #4
I have also experienced a number of EC 25's for sql backups and resolved alot of them by changing the timeout settings on the client. There was nothing actually wrong with the backup setup and it was just waiting for drives and would then fail after the timeout value was exceeded. Not sure if your issue is related but hopefully this can give you a some direction if it is.
-
1
- #6
Is there a way to to set a sql single stream job to rerun twice. "
The fact that NBU does not rerun a single sql stream job in case of a problem is one of the top most disappointing features in NetBackup and causes a lot problems.
"I simply login to the SQL server and run the failed individual db stream" is not option in a environment with hundreds of ms sql server instances.
Another disappointing fact is, that NBU is still not able to
backup the shadow copy compoments of Windows 2003 reliable, completely and correctly (5.1MP6).
The fact that NBU does not rerun a single sql stream job in case of a problem is one of the top most disappointing features in NetBackup and causes a lot problems.
"I simply login to the SQL server and run the failed individual db stream" is not option in a environment with hundreds of ms sql server instances.
Another disappointing fact is, that NBU is still not able to
backup the shadow copy compoments of Windows 2003 reliable, completely and correctly (5.1MP6).
- Thread starter
- #7
SQL autmatic retries is now available in NB 6.0 MP5
Etrack Incident = ET867730
Description:
An enhancement was included in this maintenance pack that implements an
automatic retry for SQL backups.
To carry out a retry, NetBackup MSSQL (NB-MSSQL) keeps track of the failed
operations in the batch. Failed operations are written to a newly
generated batch file with the number of retries, decremented by 1. For a
manual retry, the retry batch is placed in dbext\mssql\retry\. For an
automatic retry, the retry batch is placed in dbext\mssql\temp\ and is
initiated automatically by NB-MSSQL when the previous batch file completes.
Note: There are no NetBackup server changes in this feature for providing
advanced job grouping, server console retry, and-so-on.
Retry functionality is driven by new keyword-value pairs as follows:
RETRYTYPE MANUAL|AUTOMATIC
NUMRETRIES n --- n must be 1-9
RETRYWAITSECONDS n ?--- number of seconds until next retry
Usage:
1. Keywords are available only if all of the operations in the batch
file are backups.
2. They are only allowed in the first operation of the batch file.
3. They are also compatible with GROUPSIZE, BATCHSIZE, as well as $ALL
options.
4. If NUMRETRIES is specified but not RETRYTYPE, then AUTOMATIC is assumed.
5. If RETRYTYPE is specified, but not NUMRETRIES, then 1 retry is assumed.
Note: Backup $ALL uses an expansion macro to generate a new batch file that
Specifies operations for each object. If retry is specified with $ALL,
then the retry logic is applied to the expanded batch file.
In addition to restart capability, new information is added to the
progress viewer to enumerate the objects on which failed to get
backed up.
Bob Stump
VERITAS - "Ain't it the truth?"
Etrack Incident = ET867730
Description:
An enhancement was included in this maintenance pack that implements an
automatic retry for SQL backups.
To carry out a retry, NetBackup MSSQL (NB-MSSQL) keeps track of the failed
operations in the batch. Failed operations are written to a newly
generated batch file with the number of retries, decremented by 1. For a
manual retry, the retry batch is placed in dbext\mssql\retry\. For an
automatic retry, the retry batch is placed in dbext\mssql\temp\ and is
initiated automatically by NB-MSSQL when the previous batch file completes.
Note: There are no NetBackup server changes in this feature for providing
advanced job grouping, server console retry, and-so-on.
Retry functionality is driven by new keyword-value pairs as follows:
RETRYTYPE MANUAL|AUTOMATIC
NUMRETRIES n --- n must be 1-9
RETRYWAITSECONDS n ?--- number of seconds until next retry
Usage:
1. Keywords are available only if all of the operations in the batch
file are backups.
2. They are only allowed in the first operation of the batch file.
3. They are also compatible with GROUPSIZE, BATCHSIZE, as well as $ALL
options.
4. If NUMRETRIES is specified but not RETRYTYPE, then AUTOMATIC is assumed.
5. If RETRYTYPE is specified, but not NUMRETRIES, then 1 retry is assumed.
Note: Backup $ALL uses an expansion macro to generate a new batch file that
Specifies operations for each object. If retry is specified with $ALL,
then the retry logic is applied to the expanded batch file.
In addition to restart capability, new information is added to the
progress viewer to enumerate the objects on which failed to get
backed up.
Bob Stump
VERITAS - "Ain't it the truth?"
- Thread starter
- #9
- Status