Re: Backup tools too slow for LTO-3
- From: "Richard B. Gilbert" <rgilbert88@xxxxxxxxxxx>
- Date: Tue, 16 May 2006 12:55:40 -0400
Darren Dunham wrote:
Richard B. Gilbert <rgilbert88@xxxxxxxxxxx> wrote:<snip>
OTOH, they have some limitations. In a Disaster Recovery situation, you have to restore your backup server before you can restore anything else! Not good if time is critical.
I'm talking about a backup initiated from the Netbackup client. We needed to do it that way because it was a database backup and we determined what to backup on the fly by querying the database (select from V$DATAFILES....).
Netbackup had the odd, to me, idea that if a backup failed it should exit with SUCCESS anyway to ensure the the script would continue with the next backup.
What script are you referring to here? Are you talking about scripting
around a client-side backup or parsing the result of a server-side
backup? Most NBU failures are pretty explicit in the job log.
One time in perhaps fifty attempts, the backup would die before completing. I thought Netbackup should exit with failure so that my script could detect the failure and restart/retry the backup. Tech support insisted that the right way to do it was to to read the log file (or parse it). Detecting the failure by reading the log file the following morning made retrying infeasible; our backup Window had closed. We agreed to disagree.
- Prev by Date: Re: SUNWaccu SUNWaccr
- Next by Date: Re: Insufficient space for Sun Studio 11 installation
- Previous by thread: Re: Backup tools too slow for LTO-3
- Next by thread: Re: Backup tools too slow for LTO-3