Re: [Veritas-bu] Checkpoint Restart
Title: Message 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 of the system! As you said, if the window is open, no doubt the job will run but you would have to reconfigure the frequency I believe :-) Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Martin, Jonathan (Contractor) [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 13:58To: WEAVER, Simon; Tristan Ball; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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, and runs through Saturday. Now if that looong job fails because tape #3 of the backup set is bad, and I try to restart the job Monday morning (or Sunday / anytime after the window closes) it goes strait to 196. So my idea is to keep the window open until Monday morning, which gives me plenty of time to restart the job - but that's not a great solution because I don't want the backup job firing at 8:00AM Monday morning if the library gets backlogged (for whatever reason.) I suppose I could use priority to solve this, but why can't I just manually restart jobs that have failed? I'm still looking for solutions... h -Jonathan From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 1:56 AMTo: 'Tristan Ball'; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart Ah 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 uses the method you described complained the job re-launched but got 196 straight away! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 06:50To: WEAVER, Simon; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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. Thejob was "Done", not suspended.The window closed at 6am this morning. Iright-clicked restarted itand the new job for that stream came up in activity monitor after a couple of seconds. Interestingly, the new job came up as a "Scheduled" just like the original. I thought the manual restart might have made the new job an "Immediate". Regards, T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 June 2006 3:39 PMTo: Tristan Ball; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 01:40To: Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Checkpoint Restart I've restarted streams after window closure, it seems to work OK. T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)Sent: Tuesday, 13 June 2006 3:30 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Checkpoint Restart 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 correc
Re: [Veritas-bu] Checkpoint Restart
Title: Message 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 kind of jobs go incomplete before failing? If for example my job errors with Media Write Error (84) - will that go to incomplete (in my case for up to 24 hours) or will it go directly to failed? -Jonathan From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 1:49 AMTo: Martin, Jonathan (Contractor); Tristan Ball; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 of the system! As you said, if the window is open, no doubt the job will run but you would have to reconfigure the frequency I believe :-) Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Martin, Jonathan (Contractor) [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 13:58To: WEAVER, Simon; Tristan Ball; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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, and runs through Saturday. Now if that looong job fails because tape #3 of the backup set is bad, and I try to restart the job Monday morning (or Sunday / anytime after the window closes) it goes strait to 196. So my idea is to keep the window open until Monday morning, which gives me plenty of time to restart the job - but that's not a great solution because I don't want the backup job firing at 8:00AM Monday morning if the library gets backlogged (for whatever reason.) I suppose I could use priority to solve this, but why can't I just manually restart jobs that have failed? I'm still looking for solutions... h -Jonathan From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 1:56 AMTo: 'Tristan Ball'; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart Ah 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 uses the method you described complained the job re-launched but got 196 straight away! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 06:50To: WEAVER, Simon; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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. Thejob was "Done", not suspended.The window closed at 6am this morning. Iright-clicked restarted itand the new job for that stream came up in activity monitor after a couple of seconds. Interestingly, the new job came up as a "Scheduled" just like the original. I thought the manual restart might have made the new job an "Immediate". Regards, T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 June 2006 3:39 PMTo: Tristan Ball; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 01:40To: Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Checkpoint Restart I've restarte
Re: [Veritas-bu] Checkpoint Restart
Title: Message Jonathan If I get 196, 84 or 86 I get a failure when attempting to retry the job! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Martin, Jonathan (Contractor) [mailto:[EMAIL PROTECTED] Sent: 15 June 2006 14:38To: WEAVER, Simon; Tristan Ball; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 kind of jobs go incomplete before failing? If for example my job errors with Media Write Error (84) - will that go to incomplete (in my case for up to 24 hours) or will it go directly to failed? -Jonathan From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 1:49 AMTo: Martin, Jonathan (Contractor); Tristan Ball; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 of the system! As you said, if the window is open, no doubt the job will run but you would have to reconfigure the frequency I believe :-) Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Martin, Jonathan (Contractor) [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 13:58To: WEAVER, Simon; Tristan Ball; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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, and runs through Saturday. Now if that looong job fails because tape #3 of the backup set is bad, and I try to restart the job Monday morning (or Sunday / anytime after the window closes) it goes strait to 196. So my idea is to keep the window open until Monday morning, which gives me plenty of time to restart the job - but that's not a great solution because I don't want the backup job firing at 8:00AM Monday morning if the library gets backlogged (for whatever reason.) I suppose I could use priority to solve this, but why can't I just manually restart jobs that have failed? I'm still looking for solutions... h -Jonathan From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 1:56 AMTo: 'Tristan Ball'; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart Ah 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 uses the method you described complained the job re-launched but got 196 straight away! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 06:50To: WEAVER, Simon; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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. Thejob was "Done", not suspended.The window closed at 6am this morning. Iright-clicked restarted itand the new job for that stream came up in activity monitor after a couple of seconds. Interestingly, the new job came up as a "Scheduled" just like the original. I thought the manual restart might have made the new job an "Immediate". Regards, T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 June 2006 3:39 PMTo: Tristan Ball; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas
Re: [Veritas-bu] Checkpoint Restart
Title: Message 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. Thejob was "Done", not suspended.The window closed at 6am this morning. Iright-clicked restarted itand the new job for that stream came up in activity monitor after a couple of seconds. Interestingly, the new job came up as a "Scheduled" just like the original. I thought the manual restart might have made the new job an "Immediate". Regards, T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 June 2006 3:39 PMTo: Tristan Ball; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 01:40To: Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Checkpoint Restart I've restarted streams after window closure, it seems to work OK. T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)Sent: Tuesday, 13 June 2006 3:30 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Checkpoint Restart 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 large backups? Thanks, -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Monday, June 12, 2006 8:22 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NetBackup Planning / DR process keep in mind that in order for BMR to work properly, clients must be on the same VLAN as the BMR server, in order to boot. -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, SimonSent: June 12, 2006 4:02 AMTo: 'veritas-bu@mailman.eng.auburn.edu'Subject: [Veritas-bu] NetBackup Planning / DR process Good Morning Well so far, so good - got a more stable NBU system - one SAN Media failed its backup, but not bothered about that and its running fine now! I wanted to try and cover some grounds with any NBU win2k3/NT/2000 environments, about how your NetBackup environment is configured and what failover you have in place or DR plans. I have been looking at BMR for NBU6, but I run 5.1 MP2 which has been extremely stable for us (if you exclude the manual intervention of someone destroying it!!!), and have not been fully convinced about going to 6 yet. BMR works and integrates with 6, but from a DR point, I am not sure if this is the right method to go down. This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Checkpoint Restart
Title: Message Ah 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 uses the method you described complained the job re-launched but got 196 straight away! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 06:50To: WEAVER, Simon; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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. Thejob was "Done", not suspended.The window closed at 6am this morning. Iright-clicked restarted itand the new job for that stream came up in activity monitor after a couple of seconds. Interestingly, the new job came up as a "Scheduled" just like the original. I thought the manual restart might have made the new job an "Immediate". Regards, T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 June 2006 3:39 PMTo: Tristan Ball; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 01:40To: Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Checkpoint Restart I've restarted streams after window closure, it seems to work OK. T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)Sent: Tuesday, 13 June 2006 3:30 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Checkpoint Restart 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 large backups? Thanks, -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Monday, June 12, 2006 8:22 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NetBackup Planning / DR process keep in mind that in order for BMR to work properly, clients must be on the same VLAN as the BMR server, in order to boot. -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, SimonSent: June 12, 2006 4:02 AMTo: 'veritas-bu@mailman.eng.auburn.edu'Subject: [Veritas-bu] NetBackup Planning / DR process Good Morning Well so far, so good - got a more stable NBU system - one SAN Media failed its backup, but not bothered about that and its running fine now! I wanted to try and cover some grounds with any NBU win2k3/NT/2000 environments, about how your NetBackup environment is configured and what failover you have in place or DR plans. I have been looking at BMR for NBU6, but I run 5.1 MP2 which has been extremely stable for us (if you exclude the manual intervention of someone destroying it!!!), and have not been fully convinced about going to 6 yet. BMR works and integrates with 6, but from a DR point, I am not sure if this is the right method to go down. This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449
Re: [Veritas-bu] Checkpoint Restart
Title: Message 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, what I have seen is that, if you set the checkpoint time to say 15 minutes, it will "queue" that action, for lack of a better word, after 15 minutes have elapsed, then write the checkpoint when the fragment being written is complete. Paul -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)Sent: June 12, 2006 1:30 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Checkpoint Restart 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 large backups? Thanks, -Jonathan La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Checkpoint Restart
Title: Message The job PID was started as "scheduled" and within the start windowyou're just re-starting an existing job, which is not the same as manually starting a job. Paul -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tristan BallSent: June 14, 2006 1:50 AMTo: WEAVER, Simon; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Checkpoint Restart 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. Thejob was "Done", not suspended.The window closed at 6am this morning. Iright-clicked restarted itand the new job for that stream came up in activity monitor after a couple of seconds. Interestingly, the new job came up as a "Scheduled" just like the original. I thought the manual restart might have made the new job an "Immediate". Regards, T. La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Checkpoint Restart
Title: Message 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, and runs through Saturday. Now if that looong job fails because tape #3 of the backup set is bad, and I try to restart the job Monday morning (or Sunday / anytime after the window closes) it goes strait to 196. So my idea is to keep the window open until Monday morning, which gives me plenty of time to restart the job - but that's not a great solution because I don't want the backup job firing at 8:00AM Monday morning if the library gets backlogged (for whatever reason.) I suppose I could use priority to solve this, but why can't I just manually restart jobs that have failed? I'm still looking for solutions... h -Jonathan From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 1:56 AMTo: 'Tristan Ball'; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart Ah 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 uses the method you described complained the job re-launched but got 196 straight away! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 06:50To: WEAVER, Simon; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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. Thejob was "Done", not suspended.The window closed at 6am this morning. Iright-clicked restarted itand the new job for that stream came up in activity monitor after a couple of seconds. Interestingly, the new job came up as a "Scheduled" just like the original. I thought the manual restart might have made the new job an "Immediate". Regards, T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 June 2006 3:39 PMTo: Tristan Ball; Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Checkpoint Restart 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 Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 01:40To: Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Checkpoint Restart I've restarted streams after window closure, it seems to work OK. T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)Sent: Tuesday, 13 June 2006 3:30 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Checkpoint Restart 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 large backups? Thanks, -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Monday, June 12, 2006 8:22 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NetBackup Planning / DR process keep in mind that in order for BMR to work properly, clients must be on the same VLAN as the BMR server, in order to boot. -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, SimonSent: June 12, 2006 4:02 AMTo: 'veritas-bu@mailman.eng.auburn.edu'Subject: [Veritas-bu] NetBackup Planning / DR process Good Morning Well so far, so good - got a more stable NBU system - one SAN Media failed its backup, but not bothered about that and its running fine now! I wanted to try and cov
Re: [Veritas-bu] Checkpoint Restart
Title: Message I've restarted streams after window closure, it seems to work OK. T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)Sent: Tuesday, 13 June 2006 3:30 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Checkpoint Restart 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 large backups? Thanks, -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Monday, June 12, 2006 8:22 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NetBackup Planning / DR process keep in mind that in order for BMR to work properly, clients must be on the same VLAN as the BMR server, in order to boot. -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, SimonSent: June 12, 2006 4:02 AMTo: 'veritas-bu@mailman.eng.auburn.edu'Subject: [Veritas-bu] NetBackup Planning / DR process Good Morning Well so far, so good - got a more stable NBU system - one SAN Media failed its backup, but not bothered about that and its running fine now! I wanted to try and cover some grounds with any NBU win2k3/NT/2000 environments, about how your NetBackup environment is configured and what failover you have in place or DR plans. I have been looking at BMR for NBU6, but I run 5.1 MP2 which has been extremely stable for us (if you exclude the manual intervention of someone destroying it!!!), and have not been fully convinced about going to 6 yet. BMR works and integrates with 6, but from a DR point, I am not sure if this is the right method to go down. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Checkpoint Restart
Title: Message 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 Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: 14 June 2006 01:40To: Martin, Jonathan (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Checkpoint Restart I've restarted streams after window closure, it seems to work OK. T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor)Sent: Tuesday, 13 June 2006 3:30 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Checkpoint Restart 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 large backups? Thanks, -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Monday, June 12, 2006 8:22 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NetBackup Planning / DR process keep in mind that in order for BMR to work properly, clients must be on the same VLAN as the BMR server, in order to boot. -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, SimonSent: June 12, 2006 4:02 AMTo: 'veritas-bu@mailman.eng.auburn.edu'Subject: [Veritas-bu] NetBackup Planning / DR process Good Morning Well so far, so good - got a more stable NBU system - one SAN Media failed its backup, but not bothered about that and its running fine now! I wanted to try and cover some grounds with any NBU win2k3/NT/2000 environments, about how your NetBackup environment is configured and what failover you have in place or DR plans. I have been looking at BMR for NBU6, but I run 5.1 MP2 which has been extremely stable for us (if you exclude the manual intervention of someone destroying it!!!), and have not been fully convinced about going to 6 yet. BMR works and integrates with 6, but from a DR point, I am not sure if this is the right method to go down. This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Checkpoint Restart
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 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Checkpoint Restart
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 advice can be helpful to a few ... I'll give 3 examples from recent activities in my own shop: * I had a mail server with 250+GB in 15+M files. It took 60+ hours for a full backup. It turns out that its data is spread over many file systems. I turned on allow multiple streams and the total backup time was reduced to about 12 hours (It will be substantially better than that if I'm able to split two of the larger file systems). * I have a development system that had 300+GB of data in dozens of Oracle DBs. Full and incremental backups are similar in size and very long in duration. Many of the DBs are also backed up with the NetBackup for Oracle agent. Backups are being brought under control by allow multiple streams, as well as excluding the Oracle DB files from file system backups. * Less successful ... with one large file server (large because it's currently at the end of a relatively slow pipe), I've carved up the file system using multiple policies and exclude files so each policy exists for a part of the data (make sure one policy is all the rest or you'll get killed by new data/structure). This works, but is, IMHO, too unwieldy to recommend. In this case, if I had a fast pipe or backup storage close to the client, the file systems would no longer be large! I still like the IBM TSM model of backing up a file exactly once, eliminating all this full-backup nonsense. (Of course, back on the backup server you shuffle files around as much as you can to maintain good restore times). Hope this helps! cheers, wayne Martin, Jonathan (Contractor) wrote, in part, on 6/12/2006 1:30 PM: 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 large backups? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
