Re: [Veritas-bu] SCSI reserves on SSO windows drives
, Ulises. -- next part -- An HTML attachment was scrubbed... URL: http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20100525/23e33068/attachment-0001.htm -- Message: 8 Date: Wed, 26 May 2010 09:54:46 +1000 From: Dean dean.de...@gmail.com Subject: Re: [Veritas-bu] RMAN crosscheck To: Jared Still jkst...@gmail.com Cc: veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Message-ID: aanlktinmyrcp_xib1aax4_c1s_kif3sxdpjafgec6...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Are you sure RMAN actually knows about the tape an image is on? If it does, that is just silly. It should just ask for a backupid, then NBU will give it the correct tape, regardless of whether it's a duped or vault copy or whatever. I've always been sure that that's the way it worked (Although, I'm not a DBA and don't know that much about RMAN). Why would RMAN, if it's using the sbt_tape pipe to talk to NBU, need to know media details? It doesn't make any sense. I can understand it if you're using RMAN without NBU to write straight to tape, but if RMAN is just piping data to NBU, why would it need to double up on NBUs media management? Does RMAN also track disk STUs? I know in our environment, we write all our Oracle archive log backups to a DSSU, then they get moved out to tape and deleted from the DSSU within a day or so. We restore regularly (to development), and it always works fine, regardless of whether the archive log backups are still on disk or have been moved to tape. Does that mean RMAN is aware of the destage process? I highly doubt it. On Wed, May 26, 2010 at 7:38 AM, Jared Still jkst...@gmail.com wrote: On Wed, May 19, 2010 at 1:16 PM, David McMullin david.mcmul...@cbc-companies.com wrote: NOTE THIS PART! but this list is incomplete if an image spans several media. I haven't experienced that myself. If that were true, RMAN would be unable to restore. Having used RMAN/NetBackup to do many restores, that statement seems incorrect to me. One thing that I have seen is that if the tape has been vaulted, the media ID changes and RMAN no longer knows the correct media to ask for. When that happen, I have to supply a date range to our Backup Admin, and he requests the right tapes to restore to the time period. As re-cataloging NetBackup tapes back into the RMAN repository is nearly impossible, I never expire anything from RMAN. That way when an old tape is put back into NBU, RMAN still has the correct names to request. I guess it is possible to re-catalog NBU tapes back into RMAN, it just isn't documented by Oracle. Here's an undocumented CATALOG command you may find interesting: http://erpondb.blogspot.com/2008/09/catalog-rman-backuppieces.html Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- next part -- An HTML attachment was scrubbed... URL: http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20100526/fef568b8/attachment-0001.htm -- Message: 9 Date: Tue, 25 May 2010 17:32:03 -0700 From: Jared Still jkst...@gmail.com Subject: Re: [Veritas-bu] RMAN crosscheck To: Dean dean.de...@gmail.com Cc: veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Message-ID: aanlktile6n-q_kec3cd6gzc_yoav_qkvl3danel-w...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 On Tue, May 25, 2010 at 4:54 PM, Dean dean.de...@gmail.com wrote: Are you sure RMAN actually knows about the tape an image is on? If it does, that is just silly. It should just ask for a backupid, then NBU will give it the correct tape, regardless of whether it's a duped or vault copy or whatever. I've always been sure that that's the way it worked (Although, I'm not a DBA and don't know that much about RMAN). I think you're right, it just keeps the Media ID. It's been a few months since I have looked closely at it. Regarding vaulted tapes: RMAN will not know that a tape has been vaulted, so it will have the wrong media ID for requesting the tape. If the tapes are restored into the NBU catalog, RMAN will then ask for the correct backup pieces by name. This not an issue with RMAN, as the API has that capability, at least according to the docs. It just has not been implemented by Veritas. This would bear further investigation, as that situation may have changed since I last looked into it. Does RMAN also track disk STUs? I know in our environment, we write all our Oracle archive log backups to a DSSU, then they get moved out to tape and deleted from the DSSU within a day or so. We restore regularly (to development), and it always works fine
Re: [Veritas-bu] SCSI reserves on SSO windows drives
/plain; charset=us-ascii I'd be interested in knowing if anyone is seeing this issue with an SL8500 running ACSLS. Thanks -sj Ulises Rodriguez ulises.rodrig...@wallst.com 5/25/2010 12:22 PM Hello All, I have an issue when I try to eject tapes, the process hangs but it only ejects one tape. I am running NBU 6.5.5 on Win2k3 64x, Storagetek L700 library. Has anybody seen or have ideas how to fix this? Thank you, Ulises. -- next part -- An HTML attachment was scrubbed... URL: http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20100525/23e33 068/attachment-0001.htm -- Message: 8 Date: Wed, 26 May 2010 09:54:46 +1000 From: Dean dean.de...@gmail.com Subject: Re: [Veritas-bu] RMAN crosscheck To: Jared Still jkst...@gmail.com Cc: veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Message-ID: aanlktinmyrcp_xib1aax4_c1s_kif3sxdpjafgec6...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Are you sure RMAN actually knows about the tape an image is on? If it does, that is just silly. It should just ask for a backupid, then NBU will give it the correct tape, regardless of whether it's a duped or vault copy or whatever. I've always been sure that that's the way it worked (Although, I'm not a DBA and don't know that much about RMAN). Why would RMAN, if it's using the sbt_tape pipe to talk to NBU, need to know media details? It doesn't make any sense. I can understand it if you're using RMAN without NBU to write straight to tape, but if RMAN is just piping data to NBU, why would it need to double up on NBUs media management? Does RMAN also track disk STUs? I know in our environment, we write all our Oracle archive log backups to a DSSU, then they get moved out to tape and deleted from the DSSU within a day or so. We restore regularly (to development), and it always works fine, regardless of whether the archive log backups are still on disk or have been moved to tape. Does that mean RMAN is aware of the destage process? I highly doubt it. On Wed, May 26, 2010 at 7:38 AM, Jared Still jkst...@gmail.com wrote: On Wed, May 19, 2010 at 1:16 PM, David McMullin david.mcmul...@cbc-companies.com wrote: NOTE THIS PART! but this list is incomplete if an image spans several media. I haven't experienced that myself. If that were true, RMAN would be unable to restore. Having used RMAN/NetBackup to do many restores, that statement seems incorrect to me. One thing that I have seen is that if the tape has been vaulted, the media ID changes and RMAN no longer knows the correct media to ask for. When that happen, I have to supply a date range to our Backup Admin, and he requests the right tapes to restore to the time period. As re-cataloging NetBackup tapes back into the RMAN repository is nearly impossible, I never expire anything from RMAN. That way when an old tape is put back into NBU, RMAN still has the correct names to request. I guess it is possible to re-catalog NBU tapes back into RMAN, it just isn't documented by Oracle. Here's an undocumented CATALOG command you may find interesting: http://erpondb.blogspot.com/2008/09/catalog-rman-backuppieces.html Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- next part -- An HTML attachment was scrubbed... URL: http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20100526/fef56 8b8/attachment-0001.htm -- Message: 9 Date: Tue, 25 May 2010 17:32:03 -0700 From: Jared Still jkst...@gmail.com Subject: Re: [Veritas-bu] RMAN crosscheck To: Dean dean.de...@gmail.com Cc: veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Message-ID: aanlktile6n-q_kec3cd6gzc_yoav_qkvl3danel-w...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 On Tue, May 25, 2010 at 4:54 PM, Dean dean.de...@gmail.com wrote: Are you sure RMAN actually knows about the tape an image is on? If it does, that is just silly. It should just ask for a backupid, then NBU will give it the correct tape, regardless of whether it's a duped or vault copy or whatever. I've always been sure that that's the way it worked (Although, I'm not a DBA and don't know that much about RMAN). I think you're right, it just keeps the Media ID. It's been a few months since I have looked closely at it. Regarding vaulted tapes: RMAN will not know that a tape has been vaulted, so it will have the wrong media ID for requesting the tape. If the tapes are restored into the NBU catalog, RMAN will then ask for the correct backup pieces by name. This not an issue with RMAN, as the API has that capability, at least according
[Veritas-bu] Incorrect File List being Built
Hi Guys I have quite an interesting one here NetBackup 6.5.5 - windows 2003 Master NetBackup 6.5.5 Windows 2003 Media Server behind a firewall backing itself up All comms going through vnetd I am using a file list such as: E:\Folder1\* E:\Folder2\* I am doing this so that I can pull the data of the disk using multiple streams so that I can keep a decent data flow to an LTO4 drive. Else certain directories containing small file just slow the entire backup volume down The first backup run used the wildcard and detected each subdirectory and ran a separate stream. When new sub directories are added they are not detected by the wildcard discovery - the directories which existed at the time the first back ran are the only ones which jobs are created for. If I create a new policy and specify E:\Folder1\* - NetBackup will then detect all the subdirectories and kick off a job for each one. Its almost as if the file list is being cached somewhere and not being rediscovered for each scheduled backup. Any thoughts or similar experiences? I am sure I have actually seen this will earlier versions of NetBackup - going back to NB5 Cheers ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Incorrect File List being Built
Delete the STREAMS files under images\client-name Warning: This will probably cause incremental to run as fulls until a new full has run. Kind regards M. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel Tal Sent: 26 May 2010 04:37 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Incorrect File List being Built Hi Guys I have quite an interesting one here NetBackup 6.5.5 - windows 2003 Master NetBackup 6.5.5 Windows 2003 Media Server behind a firewall backing itself up All comms going through vnetd I am using a file list such as: E:\Folder1\* E:\Folder2\* I am doing this so that I can pull the data of the disk using multiple streams so that I can keep a decent data flow to an LTO4 drive. Else certain directories containing small file just slow the entire backup volume down The first backup run used the wildcard and detected each subdirectory and ran a separate stream. When new sub directories are added they are not detected by the wildcard discovery - the directories which existed at the time the first back ran are the only ones which jobs are created for. If I create a new policy and specify E:\Folder1\* - NetBackup will then detect all the subdirectories and kick off a job for each one. Its almost as if the file list is being cached somewhere and not being rediscovered for each scheduled backup. Any thoughts or similar experiences? I am sure I have actually seen this will earlier versions of NetBackup - going back to NB5 Cheers ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Incorrect File List being Built
Thanks, will try that I can see there is a stream file for each policy which ran with the file structure inside - makes sense From: Marianne Van Den Berg [mailto:mvdb...@stortech.co.za] Sent: 26 May 2010 15:44 To: Shekel Tal; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Incorrect File List being Built Delete the STREAMS files under images\client-name Warning: This will probably cause incremental to run as fulls until a new full has run. Kind regards M. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel Tal Sent: 26 May 2010 04:37 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Incorrect File List being Built Hi Guys I have quite an interesting one here NetBackup 6.5.5 - windows 2003 Master NetBackup 6.5.5 Windows 2003 Media Server behind a firewall backing itself up All comms going through vnetd I am using a file list such as: E:\Folder1\* E:\Folder2\* I am doing this so that I can pull the data of the disk using multiple streams so that I can keep a decent data flow to an LTO4 drive. Else certain directories containing small file just slow the entire backup volume down The first backup run used the wildcard and detected each subdirectory and ran a separate stream. When new sub directories are added they are not detected by the wildcard discovery - the directories which existed at the time the first back ran are the only ones which jobs are created for. If I create a new policy and specify E:\Folder1\* - NetBackup will then detect all the subdirectories and kick off a job for each one. Its almost as if the file list is being cached somewhere and not being rediscovered for each scheduled backup. Any thoughts or similar experiences? I am sure I have actually seen this will earlier versions of NetBackup - going back to NB5 Cheers ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Incorrect File List being Built
On Wed, May 26, 2010 at 9:37 AM, Shekel Tal tal.she...@uk.fujitsu.comwrote: The first backup run used the wildcard and detected each subdirectory and ran a separate stream. When new sub directories are added they are not detected by the wildcard discovery – the directories which existed at the time the first back ran are the only ones which jobs are created for. If I create a new policy and specify E:\Folder1\* - NetBackup will then detect all the subdirectories and kick off a job for each one. Its almost as if the file list is being cached somewhere and not being rediscovered for each scheduled backup. What I think you're running into is the frequency of the pre-discovery process. man bpgetconfig and look at the -prep settings. -prep hours The preprocessing interval. This interval is the minimum time in hours between client queries to discover new paths when NetBackup uses auto- discover-streaming mode. For additional informa- tion, see Setting the Preprocess Interval for Auto Discovery in the File-List Directives for Multiple Data Streams intheNetBackup Administrator's Guide. The default Preprocess Interval value is 4 hours. If the preprocessing interval changes, change it back to the default by specifying -prep -1. The preprocessing interval can be set to prepro- cess immediately by specifying 0 as the preprocess interval for auto discovery on the bpconfig com- mand line. The maximum Preprocessing Interval is 48 hours. This has existed for many releases - I found a reference to it in the NBU 5 Windows guide. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org Linkedin http://www.linkedin.com/in/ewilts ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Media write error 84
So it looks to be happening again. Same policy. What makes no sense is that half the clients in the policy fail and the other half do not. There are also other policies that are writing to this same disk staging area and they are not seeing high volumes of media write errors either. This is the policy that I'm seeing the highest amount of failures on. sande...@backup1:/usr$ bpdbjobs |grep -c unix_night 42 sande...@backup1:/usr$ bpdbjobs |grep unix_night|grep -c 84 20 These are two other similar policies that both write to the exact same disk staging group as the above policy. sande...@backup1:/usr$ bpdbjobs |grep unix_DMZ|grep -c 84 1 sande...@backup1:/usr$ bpdbjobs |grep win_night|grep -c 84 6 What makes it further confusing is that if I rerun these jobs later, they all succeed. On 05/10/2010 09:45 AM, Nate Sanders wrote: Just seems odd that all 9 of these jobs failed at the same time with an 84 but others after it were just fine. I reran a couple of them now and they are all succeeding now. I also forgot these go to disk staging and not direct to tape. On 05/10/2010 09:37 AM, WEAVER, Simon (external) wrote: 84 is usually when you get errors writing to a disk. To the best of my knowledge, it does not sound like a disk full message. But I cannot tell you what error message may be related to that off my head. May need to enable BPDM logging on the Server (verbose=5) How much space have you got now? Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Monday, May 10, 2010 3:02 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Media write error 84 I know Netbackup errors are often cryptic or not very straight forward but I forget if an 84 on a regular job (cumulative) has any hidden meaning I'm not recalling. I know an 84 on a DSSU job usually implies a disk staging flush is needed. I got a hand full of 84s today and I know we've been running low on disk lately. I wasn't sure if this was a cryptic way of saying we ran out over the weekend. -- Nate SandersDigital Motorworks System Administrator (512) 692 - 1038 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] LTO3 to LTO4 conversion
Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are there any other gotchas or need to knows I must be aware of? Thank you much. P.S. New member to the list, working on getting scheduled for some on-line courses. -- Nate SandersDigital Motorworks System Administrator (512) 692 - 1038 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] LTO3 to LTO4 conversion
Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are there any other gotchas or need to knows I must be aware of? Thank you much. P.S. New member to the list, working on getting scheduled for some on-line courses. -- Nate SandersDigital Motorworks System Administrator (512) 692 - 1038 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] LTO3 to LTO4 conversion
That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are there any other gotchas or need to knows I must be aware of? Thank you much. P.S. New member to the list, working on getting scheduled for some on-line courses. -- Nate SandersDigital Motorworks System Administrator (512) 692 - 1038 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] LTO3 to LTO4 conversion
Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are there any other gotchas or need to knows I must be aware of? Thank you much. P.S. New member to the list, working on getting scheduled for some on-line courses. -- Nate SandersDigital Motorworks System Administrator (512) 692 - 1038 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] LTO3 to LTO4 conversion
Or create new LTO4 Pools that contain only LTO4 media, then when the LTO3 expires back to their pools, these will no longer be used by the Policies. Thus enforcing only LTO4 media is used. Yeah? All the information I've been getting is making sense now. Thanks everyone. On 05/26/2010 01:07 PM, Martin, Jonathan wrote: Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are there any other gotchas or need to knows I must be aware of? Thank you much. P.S. New member to the list, working on getting scheduled for some on-line courses. -- Nate SandersDigital Motorworks System Administrator (512) 692 - 1038 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If
Re: [Veritas-bu] LTO3 to LTO4 conversion
if you are replacing all drives at once, you may want to keep the media type the same, so that you can still read the lto3 media in the lto4 drives (such as restoring data). the lto4 drives can also write to the lto3 media if need be, unless you want to write using encryption. i've seen it freeze the lto3 media if it loads it when wanting to write to an encrypted pool. if you do keep the drives the same type, then simply freeze all lto3 media and they shouldn't be able to be written to if they are active or even after all images expire. they will remain frozen until you unfreeze them, and then you could manually move them to a media pool that no backup policies use. you wouldn't need to change any barcode rules or backup policies. jerald -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Wednesday, May 26, 2010 1:08 PM To: Nate Sanders Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are there any other gotchas or need to knows I must be aware of? Thank you much. P.S. New
Re: [Veritas-bu] LTO3 to LTO4 conversion
You don't really need new pools just a lto4 scratch pool. NBU takes care to match the correct tape media type with the right drive type i.e. hcart1 for lto3 and dhcart2 for lto4 -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 2:24 PM To: Martin, Jonathan Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Or create new LTO4 Pools that contain only LTO4 media, then when the LTO3 expires back to their pools, these will no longer be used by the Policies. Thus enforcing only LTO4 media is used. Yeah? All the information I've been getting is making sense now. Thanks everyone. On 05/26/2010 01:07 PM, Martin, Jonathan wrote: Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are there any other gotchas or need to knows I must be aware of? Thank you much. P.S. New member to the list, working on getting scheduled for some on-line courses.
Re: [Veritas-bu] LTO3 to LTO4 conversion
You can only have one scratch pool at a time. So if you change your existing scratch pool's properties and uncheck the scratch pool box, then create a new scratch pool, your LTO4 media will go to the new scratch pool (because of the Barcode rule) and your old LTO3 media go to the old scratch pool and not get used. Another note on the barcode rules, you can create a DEFAULT barcode rule (put DEFAULT in the barcode box when creating the rule) to create one rule that applies to all media that get loaded, regardless of barcode. -Jonathan -Original Message- From: Nate Sanders [mailto:sande...@dmotorworks.com] Sent: Wednesday, May 26, 2010 2:24 PM To: Martin, Jonathan Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Or create new LTO4 Pools that contain only LTO4 media, then when the LTO3 expires back to their pools, these will no longer be used by the Policies. Thus enforcing only LTO4 media is used. Yeah? All the information I've been getting is making sense now. Thanks everyone. On 05/26/2010 01:07 PM, Martin, Jonathan wrote: Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and
Re: [Veritas-bu] LTO3 to LTO4 conversion
Yeah that is our intent, to keep the media type the same. Changing drive types presents a more challenging rollback and also limits us to the amount of drives we can us during the migration and for restores. Overall using new pools is quicker and easier to migrate with. How do I freeze LTO3 media, outside of having to write protect every tape by hand. On 05/26/2010 01:29 PM, Iverson, Jerald wrote: if you are replacing all drives at once, you may want to keep the media type the same, so that you can still read the lto3 media in the lto4 drives (such as restoring data). the lto4 drives can also write to the lto3 media if need be, unless you want to write using encryption. i've seen it freeze the lto3 media if it loads it when wanting to write to an encrypted pool. if you do keep the drives the same type, then simply freeze all lto3 media and they shouldn't be able to be written to if they are active or even after all images expire. they will remain frozen until you unfreeze them, and then you could manually move them to a media pool that no backup policies use. you wouldn't need to change any barcode rules or backup policies. jerald -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Wednesday, May 26, 2010 1:08 PM To: Nate Sanders Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate
Re: [Veritas-bu] LTO3 to LTO4 conversion
bpmedia -freeze -m mediaid This will put the media into a special frozen state, so NetBackup will not write to it. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 2:35 PM To: Iverson, Jerald Cc: Sanders, Nate; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Yeah that is our intent, to keep the media type the same. Changing drive types presents a more challenging rollback and also limits us to the amount of drives we can us during the migration and for restores. Overall using new pools is quicker and easier to migrate with. How do I freeze LTO3 media, outside of having to write protect every tape by hand. On 05/26/2010 01:29 PM, Iverson, Jerald wrote: if you are replacing all drives at once, you may want to keep the media type the same, so that you can still read the lto3 media in the lto4 drives (such as restoring data). the lto4 drives can also write to the lto3 media if need be, unless you want to write using encryption. i've seen it freeze the lto3 media if it loads it when wanting to write to an encrypted pool. if you do keep the drives the same type, then simply freeze all lto3 media and they shouldn't be able to be written to if they are active or even after all images expire. they will remain frozen until you unfreeze them, and then you could manually move them to a media pool that no backup policies use. you wouldn't need to change any barcode rules or backup policies. jerald -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Wednesday, May 26, 2010 1:08 PM To: Nate Sanders Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of
Re: [Veritas-bu] LTO3 to LTO4 conversion
Well I have rules for different things. My catalog tapes have custom barcodes (makes them easy to spot or find) So I have a rule to put those in to the catalog pool I have some other special barcode labels as well with special pools. I also have more than one location and more than one master. All normal tapes for each location start with a different letter.. So I create barcode rules that if a tape from another location comes in, it also goes to a special pool so it does not go to the scratch pool. You can have different pools for different media types. In your case you need to keep your two types separate. Which should be done with media type like hcart, hcart1, hcart2, hcart3 But if you are not doing that you would have to play with barcode rules and the instructions of where tapes go when them come back into a library. (taken from tech doc 303076) With the RETURN_UNASSIGNED_MEDIA_TO_SCRATCH_POOL set to yes, then these things are true: Any tape media that started out in the scratch pool before it was assigned will go back into the scratch pool once the images have expired and the tape has been unassigned. If a tape media was assigned to a pool without ever being in the scratch pool, then that tape will not go into scratch once it has been expired and unassigned. It will remain in its originating volume pool. - So if your bp.conf has this and set to yes, and you put all your new tapes into the scratch pool they will go back there when they go unassigned. You have to look at what you need and see how the options will allow you to get the end result. Now if you are going to get rid of the lto3 tapes, then just don't put those back into the library. -Original Message- From: Nate Sanders [mailto:sande...@dmotorworks.com] Sent: Wednesday, May 26, 2010 12:59 PM To: Judy Hinchcliffe Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through the Media Manager (5.1) Admin manual for a better understanding of how NBU uses scratch/pools and expires tapes, but nothing really seems to explain how it works, just how to manage general tasks. If anyone can help answer my questions and also provide a better place for me to focus studying on I'd appreciate it. Thanks. On 05/03/2010 10:23 AM, Nate Sanders wrote: Forgive me for what may be a straight forward question, but our last backup admin has left and I'm doing my best to step up and keep our systems moving along. I'm looking for a general outline of an LTO3 to LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we can't wait to complete it). Right now we still have some LTO2 tapes, and I believe I must migrate and/or eject and store these in order to complete the conversion. Are
Re: [Veritas-bu] LTO3 to LTO4 conversion
Or if using the gui right click all the tapes and say freeze -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:35 PM To: Iverson, Jerald Cc: Sanders, Nate; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Yeah that is our intent, to keep the media type the same. Changing drive types presents a more challenging rollback and also limits us to the amount of drives we can us during the migration and for restores. Overall using new pools is quicker and easier to migrate with. How do I freeze LTO3 media, outside of having to write protect every tape by hand. On 05/26/2010 01:29 PM, Iverson, Jerald wrote: if you are replacing all drives at once, you may want to keep the media type the same, so that you can still read the lto3 media in the lto4 drives (such as restoring data). the lto4 drives can also write to the lto3 media if need be, unless you want to write using encryption. i've seen it freeze the lto3 media if it loads it when wanting to write to an encrypted pool. if you do keep the drives the same type, then simply freeze all lto3 media and they shouldn't be able to be written to if they are active or even after all images expire. they will remain frozen until you unfreeze them, and then you could manually move them to a media pool that no backup policies use. you wouldn't need to change any barcode rules or backup policies. jerald -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Wednesday, May 26, 2010 1:08 PM To: Nate Sanders Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you configure the barcode rules ( you should be able to find this in the volume manger manual) Now the barcode rules are based on what it finds when it scans the barcodes on the tapes. If you lto3 tapes have a L3 in the barcode then you can make a rule telling it L3's go to old pool Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes, then see if the tapes end up in the pools you want them to. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:12 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Getting ready to load in the new LTO4 tapes, but I'm still having a hard time planning the right way to do it. I assume I can make a new LTO4 scratch pool that will store all my initial blank media. I disable the existing scratch pool and this will ensure that only new LTO4 tapes are rotated into my other pools. But how do I make sure the existing LTO3 tapes that expire are not put back into this new LTO4 scratch pool? People keep mention barcode rules/labels but I've been unable to find what this means or where to view/manage these. If I were to make new duplicate LTO4 pools for my other volumes (production4, ndmp4, offsite4, etc) would this ensure none of the existing LTO3 tapes are reused? I've been digging through
Re: [Veritas-bu] Incorrect File List being Built
Try removing the pempersist file. Tech note http://support.veritas.com/docs/295532 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts Sent: Wednesday, May 26, 2010 11:01 AM To: Shekel Tal Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Incorrect File List being Built On Wed, May 26, 2010 at 9:37 AM, Shekel Tal tal.she...@uk.fujitsu.commailto:tal.she...@uk.fujitsu.com wrote: The first backup run used the wildcard and detected each subdirectory and ran a separate stream. When new sub directories are added they are not detected by the wildcard discovery - the directories which existed at the time the first back ran are the only ones which jobs are created for. If I create a new policy and specify E:\Folder1\* - NetBackup will then detect all the subdirectories and kick off a job for each one. Its almost as if the file list is being cached somewhere and not being rediscovered for each scheduled backup. What I think you're running into is the frequency of the pre-discovery process. man bpgetconfig and look at the -prep settings. -prep hours The preprocessing interval. This interval is the minimum time in hours between client queries to discover new paths when NetBackup uses auto- discover-streaming mode. For additional informa- tion, see Setting the Preprocess Interval for Auto Discovery in the File-List Directives for Multiple Data Streams intheNetBackup Administrator's Guide. The default Preprocess Interval value is 4 hours. If the preprocessing interval changes, change it back to the default by specifying -prep -1. The preprocessing interval can be set to prepro- cess immediately by specifying 0 as the preprocess interval for auto discovery on the bpconfig com- mand line. The maximum Preprocessing Interval is 48 hours. This has existed for many releases - I found a reference to it in the NBU 5 Windows guide. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.orgmailto:ewi...@ewilts.org [cid:image001.jpg@01CAFCE4.64F548A0]Linkedinhttp://www.linkedin.com/in/ewilts CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error; please notify Cranel Incorporated immediately by telephone at 614-431-8000 or 800-288-3475 and destroy all copies of this communication and any attachments. inline: image001.jpg___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Media write error 84
So I kicked off the unix_nightly policy during the day and all 16 hosts succeeded with no failures. Makes me wonder if the DSSU is being overloaded at night? I'll have to wait a few days to catch NBU during a lul period for the pempersist file, but what effect does this have or why might it be causing an issue? On 05/26/2010 01:53 PM, Patrick k. Behringer wrote: Try removing the pempersist file. NetBackup tech-note: http://support.veritas.com/docs/295532 -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 11:05 AM Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Media write error 84 So it looks to be happening again. Same policy. What makes no sense is that half the clients in the policy fail and the other half do not. There are also other policies that are writing to this same disk staging area and they are not seeing high volumes of media write errors either. This is the policy that I'm seeing the highest amount of failures on. sande...@backup1:/usr$ bpdbjobs |grep -c unix_night 42 sande...@backup1:/usr$ bpdbjobs |grep unix_night|grep -c 84 20 These are two other similar policies that both write to the exact same disk staging group as the above policy. sande...@backup1:/usr$ bpdbjobs |grep unix_DMZ|grep -c 84 1 sande...@backup1:/usr$ bpdbjobs |grep win_night|grep -c 84 6 What makes it further confusing is that if I rerun these jobs later, they all succeed. On 05/10/2010 09:45 AM, Nate Sanders wrote: Just seems odd that all 9 of these jobs failed at the same time with an 84 but others after it were just fine. I reran a couple of them now and they are all succeeding now. I also forgot these go to disk staging and not direct to tape. On 05/10/2010 09:37 AM, WEAVER, Simon (external) wrote: 84 is usually when you get errors writing to a disk. To the best of my knowledge, it does not sound like a disk full message. But I cannot tell you what error message may be related to that off my head. May need to enable BPDM logging on the Server (verbose=5) How much space have you got now? Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Monday, May 10, 2010 3:02 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Media write error 84 I know Netbackup errors are often cryptic or not very straight forward but I forget if an 84 on a regular job (cumulative) has any hidden meaning I'm not recalling. I know an 84 on a DSSU job usually implies a disk staging flush is needed. I got a hand full of 84s today and I know we've been running low on disk lately. I wasn't sure if this was a cryptic way of saying we ran out over the weekend. -- Nate SandersDigital Motorworks System Administrator (512) 692 - 1038 This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Media write error 84
On Wed, May 26, 2010 at 2:08 PM, Nate Sanders sande...@dmotorworks.comwrote: So I kicked off the unix_nightly policy during the day and all 16 hosts succeeded with no failures. Makes me wonder if the DSSU is being overloaded at night? An 84 on a DSSU is a physical disk error - somewhere in your transport chain or the raid controllers or disk drives, you're getting an error. I've seen it when a fibre ISL was being driven at 2Gbps when the distance and fibre type mandated that it only be run at 1Gbps - that took me a while to find. It can be bad RAID controller firmware. Check everything from beginning to end and see if you can narrow it down. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org Linkedin http://www.linkedin.com/in/ewilts ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] LTO3 to LTO4 conversion
This is an interesting one. I understand the need to keep LTO3 and LTO4 as the same media type, so you can still restore from LTO3 tapes on LTO4 drives. But how to ensure the expiring LTO3 tapes don't return to scratch and get reused for new backups? Freezing them is the only way I can think of. It will work. It just means you'll have to manually unfreeze them at some point in the future so you can delete them. If you have long-ish retentions on some of these backups (like 7 years, as we do), it's something that will hang around for a while! It would be nice if there was some way to tell NBU, for a particular tape, or set of tapes, that they shouldn't be returned to scratch. But I can't think of any way to do it (other than freezing). Manually flipping the write-protect tab on the tapes is not really an option, as you'll get lots of backups failing with status 84 (media open error) when they try to write to the write-protected scratch tapes. I guess freezing is the only option. You can periodically run bpmedialist over the coming ... years? and if a tape is both frozen, and expired, you'll be able to tell that all the images on it have expired. I guess the best thing to do then would be to physically eject it from the library, then unfreeze it (I like the term thaw), at which point it will go straight back to the scratch pool. Then you can delete it completely (vmdelete, or just right click and delete in the GUI). I had an inkling there was a previous_pool type parameter you could set with vmchange, so when a tape expires, it will go back to something other than the scratch pool, but I can't see any reference to it. If anyone else has a better solution to this little problem, it's something I'd be interested in too. Cheers Dean On Thu, May 27, 2010 at 4:35 AM, Nate Sanders sande...@dmotorworks.comwrote: Yeah that is our intent, to keep the media type the same. Changing drive types presents a more challenging rollback and also limits us to the amount of drives we can us during the migration and for restores. Overall using new pools is quicker and easier to migrate with. How do I freeze LTO3 media, outside of having to write protect every tape by hand. On 05/26/2010 01:29 PM, Iverson, Jerald wrote: if you are replacing all drives at once, you may want to keep the media type the same, so that you can still read the lto3 media in the lto4 drives (such as restoring data). the lto4 drives can also write to the lto3 media if need be, unless you want to write using encryption. i've seen it freeze the lto3 media if it loads it when wanting to write to an encrypted pool. if you do keep the drives the same type, then simply freeze all lto3 media and they shouldn't be able to be written to if they are active or even after all images expire. they will remain frozen until you unfreeze them, and then you could manually move them to a media pool that no backup policies use. you wouldn't need to change any barcode rules or backup policies. jerald -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Wednesday, May 26, 2010 1:08 PM To: Nate Sanders Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule? And when are these rules actually processed? I know it's used when injecting new tapes, but what other situations does it apply these rules? On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote: Bar code rules can be viewed Go to the gui and act like you are going to inject tapes into your library Choose the radio button for update volume configuration This will then un-gray the advanced options Click that button and you will see a screen where you
Re: [Veritas-bu] LTO3 to LTO4 conversion
That's why I was thinking about making a new scratch pool. If you make a new scratch pool, and deactivate the old scratch pool, your LTO3 media should still return to the old scratch pool when they expire, while barcode rules move new LTO4 media into the new scratch pool. -Jonathan From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dean Sent: Wednesday, May 26, 2010 6:07 PM To: Nate Sanders Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion This is an interesting one. I understand the need to keep LTO3 and LTO4 as the same media type, so you can still restore from LTO3 tapes on LTO4 drives. But how to ensure the expiring LTO3 tapes don't return to scratch and get reused for new backups? Freezing them is the only way I can think of. It will work. It just means you'll have to manually unfreeze them at some point in the future so you can delete them. If you have long-ish retentions on some of these backups (like 7 years, as we do), it's something that will hang around for a while! It would be nice if there was some way to tell NBU, for a particular tape, or set of tapes, that they shouldn't be returned to scratch. But I can't think of any way to do it (other than freezing). Manually flipping the write-protect tab on the tapes is not really an option, as you'll get lots of backups failing with status 84 (media open error) when they try to write to the write-protected scratch tapes. I guess freezing is the only option. You can periodically run bpmedialist over the coming ... years? and if a tape is both frozen, and expired, you'll be able to tell that all the images on it have expired. I guess the best thing to do then would be to physically eject it from the library, then unfreeze it (I like the term thaw), at which point it will go straight back to the scratch pool. Then you can delete it completely (vmdelete, or just right click and delete in the GUI). I had an inkling there was a previous_pool type parameter you could set with vmchange, so when a tape expires, it will go back to something other than the scratch pool, but I can't see any reference to it. If anyone else has a better solution to this little problem, it's something I'd be interested in too. Cheers Dean On Thu, May 27, 2010 at 4:35 AM, Nate Sanders sande...@dmotorworks.com wrote: Yeah that is our intent, to keep the media type the same. Changing drive types presents a more challenging rollback and also limits us to the amount of drives we can us during the migration and for restores. Overall using new pools is quicker and easier to migrate with. How do I freeze LTO3 media, outside of having to write protect every tape by hand. On 05/26/2010 01:29 PM, Iverson, Jerald wrote: if you are replacing all drives at once, you may want to keep the media type the same, so that you can still read the lto3 media in the lto4 drives (such as restoring data). the lto4 drives can also write to the lto3 media if need be, unless you want to write using encryption. i've seen it freeze the lto3 media if it loads it when wanting to write to an encrypted pool. if you do keep the drives the same type, then simply freeze all lto3 media and they shouldn't be able to be written to if they are active or even after all images expire. they will remain frozen until you unfreeze them, and then you could manually move them to a media pool that no backup policies use. you wouldn't need to change any barcode rules or backup policies. jerald -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Wednesday, May 26, 2010 1:08 PM To: Nate Sanders Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion Barcode rules are only used when injecting new media. Your existing media will return to whatever pool they came from when they expire. If you don't want your old LTO3 media to be used anymore then change your media type for LTO4 to something different than what your LTO3 media use, and reconfigure your drives only to use that media type. I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1. NetBackup won't put an hcart media an hcart1 drive. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Wednesday, May 26, 2010 1:59 PM To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion That tiny bit of information just answered tons of questions. Thank you! So now I know how to properly handle all new incoming LTO4 tapes. And ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s wind up in a dead pool for old tapes, do I simply enter L3 as the barcode rule?
