Author: JMARTI05 at intersil.com (Martin, Jonathan (Contractor))
Date: Mon, 12 Jun 2006 13:30:13 -0400
It is my understanding that I can't "restart" a failed backup with checkpoint enabled unless it is still in the backup window? Is this correct? Also, does anyone have any tips on using checkpoint and
I would like to run a certain script after a file is successfully backed on a client. How do I check on a netbackup client if a certain file was backed up successfully or not? Thanks in advance, -D _
My experience matches your understanding. My limited experience with large large backups has led me to avoid them where possible! In case you think I'm an idiot, you're not wrong, but maybe the advic
I've restarted streams after window closure, it seems to work OK. T. -- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 _____ It is my understanding that I can't "restart" a failed b
Author: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Wed, 14 Jun 2006 06:38:59 +0100
I always thought you would get a 196 status (Backup Window closed). I assume you restarted by choosing a stream that failed and right clicking on it and selecting "restart job" ? Regards Simon Weaver
I've just double checked, on a machine that conveniently failed it's backups last night.. :-) The job in question was a single stream of a multi stream backup, which had failed with an error 156. The
Author: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Wed, 14 Jun 2006 06:55:33 +0100
Ahhhhh I see - ok so MAYBE, if a job initially fails with 196 (backup window closed), and you attempt to re-run, it may automatically fail again. Now this is interesting, because another site that us
Author: pkeating at bank-banque-canada.ca (Paul Keating)
Date: Wed, 14 Jun 2006 08:48:43 -0400
Make sure you have a reasonable frgament size configured. if you have frag size set to "infinite", there will be no checkpoints taken, from what I understand, and have experienced. In my testing, wha
Author: pkeating at bank-banque-canada.ca (Paul Keating)
Date: Wed, 14 Jun 2006 08:51:59 -0400
The job PID was started as "scheduled" and within the start window....you're just re-starting an existing job, which is not the same as manually starting a job. Paul -- --Original Message-- From: ver
Author: JMARTI05 at intersil.com (Martin, Jonathan (Contractor))
Date: Wed, 14 Jun 2006 08:57:36 -0400
That is precisely the error I am getting. Sorry I wasn't more descriptive. I've got a remote site with about 3 TB to backup which takes about 40 hours on their hardware. The window opens Friday night
Author: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Thu, 15 Jun 2006 06:49:26 +0100
Jonathan Same here, just got into work, 2 streams failed - restarted, but as the backup window closed at 6am (got in at 6:30am) it went straight to 196! so............. perhaps this IS the behaviour
Author: JMARTI05 at intersil.com (Martin, Jonathan (Contractor))
Date: Thu, 15 Jun 2006 09:37:30 -0400
I'm thinking here that another possible solution (other than extending the window) might be to increase the time that jobs go to incomplete before failing in the master server properties. But what ki
Author: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Thu, 15 Jun 2006 15:18:49 +0100
Jonathan If I get 196, 84 or 86 I get a failure when attempting to retry the job! Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anc