Re: [Veritas-bu] Media Server with multiple NICS
Greetings Paul, OK, I guess I mis-interpreted your question, apoligies. My initial thoughts are that you could set up a different DNS name for each interface on the media server. Then create a different storage unit that refers to each Media server name, and have that storage unit refer to the interface associated with the name. Then modify the backup policy to use the policy storage unit that refers to the interface you want to use. Just a thought.. In our environment we have multiple media servers and we direct backups to what ever media server we want for a particular policy. My guess, ( and it is only a guess) is that you could do a similar thing using one media server with multiple NIC's. I guess you could open a case with Symantec. Other people may have actual experince with this. Regasrd = Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] Esson, Paul [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/01/2008 07:02 AM To Esson, Paul [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu cc Subject Re: [Veritas-bu] Media Server with multiple NICS Folks, My clients won't have multiple NICS only the Media Server because its receiving input from multiple subnets so the use of REQUIRED_INTERFACE on the client won't help. I basically want to send certain clients to certain interfaces/addresses on the Media Server. Doesn't the Master tell the client where to send it's backup data via the policy information i.e. storage unit/device host? In a normal backup scenario nbjm starts the backup using bpcd to start bpbrm on the Media Server. The bpbrm process in turn starts bptm which then uses bpcd to start bpbkar on the client. Its the interaction between bpbkar on the client and bptm on the Media Server that I am trying to control but in my case the Media Server is a different host from the Master. Regards, Paul Esson From: Esson, Paul Sent: Fri 29/02/2008 18:33 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Media Server with multiple NICS Folks, Is anyone out there using Media Servers with multiple NICs on separate networks? I am trying to understand how to force clients to use specific interfaces on the Media Server when sending backup data or receiving restore data. Do I need to create multiple storage unit and Media Server entries to be able to target the clients through the policy? Or am I on the wrong track altogether? NBU 6.5 Solaris 10 Master and Media Servers - Media Servers have 4 NICs and clients are on multiple subnets. Regards, Paul Esson ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 5.5 training
On Thu, Feb 28, 2008 at 8:37 AM, Elena Khan [EMAIL PROTECTED] wrote: I took Veritas NetBackup 6.5 for Solaris Administration in November. Facility is in New York City on Madison Avenue (midtown) I was very pleased with the training, esp. the instructor who was open to lots of technical questions. The weather this winter is relatively mild, although there hasn't been a lot of sun. That is good to hear, I have that class scheduled in a couple of weeks at the same location. This will be my first class with Symantec, although I did take a VCS class some time back when it was still Veritas and it was top notch. There are always a lot of variables with this type of training: what the instructor is like, if the materials are up to date and in some cases even on site, the class makeup, classroom facilities. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Fragment Size
Dear NetBackup community, i have a question about the Fragment Size option in NetBackup 6.5 Windows Server 2003 environment. Are there any good known values for? Actually I set for all storage units (diskstaging and mediamanagers) a value of 2048 MB - is this a good option or is this fragment size to small? I would be pleased about some experienced data from same environments (Windows NTFS Filesystem). thanks in advance and greetings, Oliver Mohre ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] ACSLS and Netbackup Enterprise Vault Management
Do you have file called /usr/opv/volmgr/misc/EJECT.txt ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, March 03, 2008 12:19 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] ACSLS and Netbackup Enterprise Vault Management We just incorporated a new STK 8500 in our Netbackup environment. We have an AIX 5.3 master running Netbackup 6.0 MP4. After completing the nights backups we use Vault Management with Netbackup to duplicate our data and send tapes off-site. As part of the 8500 we just implemented an 7.2 ACSLS server - STK installed and configured. Here's the problem. Once vault runs and all data is duplicated, the tapes fail to eject into the 8500 cap. Netbackup vault jobs says Ejecting 2 tapes and creating reports, however netbackup just sits. Things I changed or checked. Within the vault session/profile I added the new 8500 cap ports, pointed to the new robot. Added MAP_ID to the vm.conf file. I can go into media in Netbackup and manually eject a tape into the 8500 cap. No errors in the netbackup vault sessions log file. No errors in the ACSLS log files. Set 8500 cap to both manual and automatic and tested - same result. Opened a sev-1 with netbackup. Any ideas? - PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation. ___ 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
[Veritas-bu] ACSLS and Netbackup Enterprise Vault Management
We just incorporated a new STK 8500 in our Netbackup environment. We have an AIX 5.3 master running Netbackup 6.0 MP4. After completing the nights backups we use Vault Management with Netbackup to duplicate our data and send tapes off-site. As part of the 8500 we just implemented an 7.2 ACSLS server - STK installed and configured. Here's the problem. Once vault runs and all data is duplicated, the tapes fail to eject into the 8500 cap. Netbackup vault jobs says Ejecting 2 tapes and creating reports, however netbackup just sits. Things I changed or checked. Within the vault session/profile I added the new 8500 cap ports, pointed to the new robot. Added MAP_ID to the vm.conf file. I can go into media in Netbackup and manually eject a tape into the 8500 cap. No errors in the netbackup vault sessions log file. No errors in the ACSLS log files. Set 8500 cap to both manual and automatic and tested - same result. Opened a sev-1 with netbackup. Any ideas? - PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NB Upgrade 3.4 to 6.5
We are planning the above mentioned upgrade. The catch is that we are switching hardware and OS as well. Currently running 3.4.1 on WinNT New Backup server (which will have the same name) is Windows 2003 and will have 6.5 loaded on it. These are my proposed steps: 1 – Create a VM of WIN NT and install NB3.4 2 – Import NB catalog 3 – Upgrade VM and NB to 4.5 4 – Create a VM of Win 2003 and install NB 4.5 5 – Import 4.5 NB Catalog to win 2003 VM NB 6 – Upgrade NB to 5.0 7 – Upgrade NB to 6.0 8 – Install Configure NB 6.0 on Production server (plus patches) 9 – Import VM NB catalog to production server Do you guys have any better options for doing this upgrade? The reason I am using a VM is because I cannot load 3.4 on the new Backup server in order to import the catalog. Thanks, Jerry ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] VMWare Consolidated Backup w/ Snapshot in different LUN
Hi List, We are considering using the working.Dir parameter to have VMWare place snapshots on a different LUN (on the SAN). We do not have space available on our guests' LUNs for snapshots. We will also use the sched.swap.dir parameter to keep the vswp files on the same LUN that guests' vmdk files are on. Will the LUN containing the snapshot have to be visible to the VCB Proxy host? Will VCB handle this correctly? Anyone doing this today? We are at NetBackup 6.0MP4 and VMWare 3.5 (VCB Framework and VNIM have been upgraded to the correct version), and will soon be upgrading to NBU 6.5. Thanks. --Jeff This communication is for use by the intended recipient and contains information that may be privileged, confidential or copyrighted under law. If you are not the intended recipient, you are hereby formally notified that any use, copying or distribution of this e-Mail, in whole or in part, is strictly prohibited. Please notify the sender by return e-Mail and delete this e-Mail from your system. Unless explicitly and conspicuously stated in the subject matter of the above e-Mail, this e-Mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer. This e-Mail does not constitute consent to the use of sender's contact information for direct marketing purposes or for transfers of data to third parties. This email has been scanned for all viruses by the MessageLabs service.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NB Upgrade 3.4 to 6.5
WOW Now that's a big upgrade, hope you aren't planning to do this all in one day. Plus what would worry me is that you are doing all those upgrades on a VM without actually being able to verify if anything even works Why not just upgrade current system to 4.5, setup the new hardware with 4.5 and import catalog. Run a full catalog backup, then upgrade to 5.1 and so on. I personally have only performed upgrades from Solaris running 5.1 6 AIX running 6 6.5 (not in production yet, just did in test) The 5.1 to 6 can be painful if you don't have a good plan. NBCC is critical to a successfully 5.1 6 upgrade. http://seer.entsupport.symantec.com/docs/294900.htm Jared M. Seaton Recovery Administrator Mylan Inc. 304-554-5926 304-685-1389 (Cell) Jerry Rioux [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/03/2008 02:54 PM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] NB Upgrade 3.4 to 6.5 We are planning the above mentioned upgrade. The catch is that we are switching hardware and OS as well. Currently running 3.4.1 on WinNT New Backup server (which will have the same name) is Windows 2003 and will have 6.5 loaded on it. These are my proposed steps: 1 ? Create a VM of WIN NT and install NB3.4 2 ? Import NB catalog 3 ? Upgrade VM and NB to 4.5 4 ? Create a VM of Win 2003 and install NB 4.5 5 ? Import 4.5 NB Catalog to win 2003 VM NB 6 ? Upgrade NB to 5.0 7 ? Upgrade NB to 6.0 8 ? Install Configure NB 6.0 on Production server (plus patches) 9 ? Import VM NB catalog to production server Do you guys have any better options for doing this upgrade? The reason I am using a VM is because I cannot load 3.4 on the new Backup server in order to import the catalog. Thanks, Jerry___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu == CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you. == ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How do you use NBCC?
On Thu, Feb 28, 2008 at 10:27 AM, Sean Mohr [EMAIL PROTECTED] wrote: It made for support to look at it and you really have to let them check it out. We went through the process and it took multiple passes and fixes of problems in our catalog before we are ok to do the upgrade and the upgrade (or at least the catalog conversion) went off without a hitch. The upgrade converts the 5.1 flat files into a database. The loading of the tables in the upgrade enforces database type consistency rules that will cause the import to fail when it finds things in your current version that it does not like. As prime example is media that is still assigned to a Media server that no longer that. (Like a decommission or migration) Hope this helps Thanks for the information everyone. This step has been done and other than a tape needing to be unfrozen there were no issues reported by Symantec. As part of documenting the steps I need to take, I am going through the PDF from Symantec Upgrading to Veritas Netbackup 6.5. It is very detailed, although there are a few steps that I do not see explained: Make a copy of the current Barcode rules. How do I do this? The step to run 'nbpushdata' is also a bit confusing. Here is a snippet from the guide, it is step 17: Run the nbpushdata command. This command moves data from your current database files (a subset of the NetBackup catalog) into a newly created EMM database. The sequence of when and on what systems you run the nbpushdata command is extremely important. For more information on running nbpushdata and creating the EMM database after you upgrade servers, refer to Populating the NetBackup EMM Database in the NetBackup 6.0 Installation Guides. The following list provides the order in which you must run the nbpushdata command in your environment. a 5.x Global Device Database Host - Run nbpushdata -add on the 5.x server that was configured as the Global Device Database Host. This is usually a master server, but a media server as the Global Device Database Host is also a supported configuration b Master servers - There is no particular order in which you must run nbpushdata -add on your master servers after you have run it on the server that was configured as the Global Device Database Host. VERITAS c Volume Database Hosts - You must next run nbpushdata -add on the server designated as a Volume Database Host. If the Volume Database Host was also the Global Device Database Host or a master server, this step does not apply. d Media Servers - Any remaining media servers that have not been upgraded to NetBackup 6.5 Media servers can be upgraded at a later time. == What is a Global Device Database Host ? Is it part of the master server, and if so will I only have to run it once on the master server? There is only one master server in this environment, no (other) media servers at all. Also as part of this step, is there any way to estimate how long it will take? I suppose it has something to do with the amount of data currently being backed up, speed of the server, etc? Thanks again, T. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Fragment Size
On Mon, 3 Mar 2008, Mohre, Oliver wrote: Dear NetBackup community, i have a question about the Fragment Size option in NetBackup 6.5 Windows Server 2003 environment. Are there any good known values for? Actually I set for all storage units (diskstaging and mediamanagers) a value of 2048 MB - is this a good option or is this fragment size to small? It depends on your dataset, I use 32 GiB personally, back in the day I used to use 2048 MiB but with drive backup speeds 100 MiB/s the drive barely spins up for a few seconds before it has to take a moment and write a marker every 2 gigabytes, I recommend a higher value. Obviously the higher the value means the longer it will take to seek for an individual file so its up to you to pick a good value. I would be pleased about some experienced data from same environments (Windows NTFS Filesystem). thanks in advance and greetings, Oliver Mohre ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Fragment Size
If you are using NTFS then you size must be less than about 50GB. NTFS files larger than that would error in Netbackup on my original testing. I'm currently using 10GB for my fragment sizes but I haven't done any performance testing related to other fragment sizes. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, March 03, 2008 4:25 PM To: Mohre, Oliver Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fragment Size On Mon, 3 Mar 2008, Mohre, Oliver wrote: Dear NetBackup community, i have a question about the Fragment Size option in NetBackup 6.5 Windows Server 2003 environment. Are there any good known values for? Actually I set for all storage units (diskstaging and mediamanagers) a value of 2048 MB - is this a good option or is this fragment size to small? It depends on your dataset, I use 32 GiB personally, back in the day I used to use 2048 MiB but with drive backup speeds 100 MiB/s the drive barely spins up for a few seconds before it has to take a moment and write a marker every 2 gigabytes, I recommend a higher value. Obviously the higher the value means the longer it will take to seek for an individual file so its up to you to pick a good value. I would be pleased about some experienced data from same environments (Windows NTFS Filesystem). thanks in advance and greetings, Oliver Mohre ___ 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] Fragment Size
Must be less than 50 GiB for NTFS? Hm.. I came into an environment that had no fragment size set and it (worked) albeit-- it took 2+ hours to restore a single file at the end of the tape (using Linux/ext3) however. Justin. On Mon, 3 Mar 2008, Martin, Jonathan wrote: If you are using NTFS then you size must be less than about 50GB. NTFS files larger than that would error in Netbackup on my original testing. I'm currently using 10GB for my fragment sizes but I haven't done any performance testing related to other fragment sizes. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, March 03, 2008 4:25 PM To: Mohre, Oliver Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fragment Size On Mon, 3 Mar 2008, Mohre, Oliver wrote: Dear NetBackup community, i have a question about the Fragment Size option in NetBackup 6.5 Windows Server 2003 environment. Are there any good known values for? Actually I set for all storage units (diskstaging and mediamanagers) a value of 2048 MB - is this a good option or is this fragment size to small? It depends on your dataset, I use 32 GiB personally, back in the day I used to use 2048 MiB but with drive backup speeds 100 MiB/s the drive barely spins up for a few seconds before it has to take a moment and write a marker every 2 gigabytes, I recommend a higher value. Obviously the higher the value means the longer it will take to seek for an individual file so its up to you to pick a good value. I would be pleased about some experienced data from same environments (Windows NTFS Filesystem). thanks in advance and greetings, Oliver Mohre ___ 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] NB Upgrade 3.4 to 6.5
Be afraid. Be very afraid. First, don't violate one of the sacred laws of upgrading: don't upgrade more than one thing at a time. You can upgrade your hardware, your OS your backup software. But for goodness sake, don't do them at the same time I agree with Jared. I really don't like the upgrading a bunch of versions at a time method with no way to check along the way. I realize that you've waited long enough that you've got some catch-22s. You can't upgrade to 6.x on NT, and you can't upgrade to Win2003 (is the really still the newest version?) and run 3.4. I'd do this in lock step. Along with the usual NBCC steps and things like that, I would do something like: 1. Backup the catalog, backup the catalog, backup the catalog 2. When testing this, do a bare metal backup to a similar machine so you can get NT running on some new hardware that you can test on. 3. Upgrade current install to 4.5 (I believe that will work on NT) 4. Test backups and recoveries 5. Build Win2003 server with a different name 6. Install 4.5 on Win2003 server (forget VM) 7. Import 4.5 catalog to Win2003 server 8. Do the change the hostname step that breaks in 6.0. 9. Test backups and recoveries 10. Upgrade to 5.1 11. Test backups and recoveries 12. Upgrade to 6.5 (I would skip 6.0 at this point.) 13. Test backups and recoveries This will have to be tested to make sure there aren't dependencies I don't know about. Will 4.5 install on NT? Will 4.5 install on Win2003? Each of the test backups and recoveries steps should be very extensive. Once you start running on the new stuff, you really can't go back without losing all your new backups. Step 7 is important, as it allows you to go all the way to the end when testing. (In case you do have to go backward after doing backups on a new version, I recommend keeping very tight records of which tapes/disk files you use in the new version. Then you can import them after downgrading.) Did I mention that I think you're crazy to do this without professional services? Call it self serving if you want, but Jared had it right. Your upgrade falls into the WOW category. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, March 03, 2008 12:28 PM To: Jerry Rioux Cc: veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] NB Upgrade 3.4 to 6.5 WOW Now that's a big upgrade, hope you aren't planning to do this all in one day. Plus what would worry me is that you are doing all those upgrades on a VM without actually being able to verify if anything even works Why not just upgrade current system to 4.5, setup the new hardware with 4.5 and import catalog. Run a full catalog backup, then upgrade to 5.1 and so on. I personally have only performed upgrades from Solaris running 5.1 6 AIX running 6 6.5 (not in production yet, just did in test) The 5.1 to 6 can be painful if you don't have a good plan. NBCC is critical to a successfully 5.1 6 upgrade. http://seer.entsupport.symantec.com/docs/294900.htm Jared M. Seaton Recovery Administrator Mylan Inc. 304-554-5926 304-685-1389 (Cell) Jerry Rioux [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/03/2008 02:54 PM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] NB Upgrade 3.4 to 6.5 We are planning the above mentioned upgrade. The catch is that we are switching hardware and OS as well. Currently running 3.4.1 on WinNT New Backup server (which will have the same name) is Windows 2003 and will have 6.5 loaded on it. These are my proposed steps: 1 - Create a VM of WIN NT and install NB3.4 2 - Import NB catalog 3 - Upgrade VM and NB to 4.5 4 - Create a VM of Win 2003 and install NB 4.5 5 - Import 4.5 NB Catalog to win 2003 VM NB 6 - Upgrade NB to 5.0 7 - Upgrade NB to 6.0 8 - Install Configure NB 6.0 on Production server (plus patches) 9 - Import VM NB catalog to production server Do you guys have any better options for doing this upgrade? The reason I am using a VM is because I cannot load 3.4 on the new Backup server in order to import the catalog. Thanks, Jerry___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu == CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or
Re: [Veritas-bu] Fragment Size
The Default Fragment size was orginally 2048 Megabytes. This was raised to 524,288 megabytes in 5.x or 6.x?? At least for disk. If I remember right, it was raised to reduce disk fragmentation with Disk Units. jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, March 03, 2008 1:53 PM To: Martin, Jonathan Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fragment Size Must be less than 50 GiB for NTFS? Hm.. I came into an environment that had no fragment size set and it (worked) albeit-- it took 2+ hours to restore a single file at the end of the tape (using Linux/ext3) however. Justin. On Mon, 3 Mar 2008, Martin, Jonathan wrote: If you are using NTFS then you size must be less than about 50GB. NTFS files larger than that would error in Netbackup on my original testing. I'm currently using 10GB for my fragment sizes but I haven't done any performance testing related to other fragment sizes. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, March 03, 2008 4:25 PM To: Mohre, Oliver Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fragment Size On Mon, 3 Mar 2008, Mohre, Oliver wrote: Dear NetBackup community, i have a question about the Fragment Size option in NetBackup 6.5 Windows Server 2003 environment. Are there any good known values for? Actually I set for all storage units (diskstaging and mediamanagers) a value of 2048 MB - is this a good option or is this fragment size to small? It depends on your dataset, I use 32 GiB personally, back in the day I used to use 2048 MiB but with drive backup speeds 100 MiB/s the drive barely spins up for a few seconds before it has to take a moment and write a marker every 2 gigabytes, I recommend a higher value. Obviously the higher the value means the longer it will take to seek for an individual file so its up to you to pick a good value. I would be pleased about some experienced data from same environments (Windows NTFS Filesystem). thanks in advance and greetings, Oliver Mohre ___ 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Fragment Size
I no longer use a fragment size...it is set to 0. This was recommended by veritas since all new tape drives can position to location within a fragment (can't remember what that is called...). The fragment size is a throw back to when tape drives could only position to a file marker. I had to remove my fragment size to properly duplicate my NDMP backups, otherwise if I dup'd with the 2048 meg fragment, then the NAS machine wouldn't be able to read the dup'd copy. Scott Chapman Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Horalek Sent: Monday, March 03, 2008 2:44 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fragment Size The Default Fragment size was orginally 2048 Megabytes. This was raised to 524,288 megabytes in 5.x or 6.x?? At least for disk. If I remember right, it was raised to reduce disk fragmentation with Disk Units. jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, March 03, 2008 1:53 PM To: Martin, Jonathan Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fragment Size Must be less than 50 GiB for NTFS? Hm.. I came into an environment that had no fragment size set and it (worked) albeit-- it took 2+ hours to restore a single file at the end of the tape (using Linux/ext3) however. Justin. On Mon, 3 Mar 2008, Martin, Jonathan wrote: If you are using NTFS then you size must be less than about 50GB. NTFS files larger than that would error in Netbackup on my original testing. I'm currently using 10GB for my fragment sizes but I haven't done any performance testing related to other fragment sizes. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Monday, March 03, 2008 4:25 PM To: Mohre, Oliver Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fragment Size On Mon, 3 Mar 2008, Mohre, Oliver wrote: Dear NetBackup community, i have a question about the Fragment Size option in NetBackup 6.5 Windows Server 2003 environment. Are there any good known values for? Actually I set for all storage units (diskstaging and mediamanagers) a value of 2048 MB - is this a good option or is this fragment size to small? It depends on your dataset, I use 32 GiB personally, back in the day I used to use 2048 MiB but with drive backup speeds 100 MiB/s the drive barely spins up for a few seconds before it has to take a moment and write a marker every 2 gigabytes, I recommend a higher value. Obviously the higher the value means the longer it will take to seek for an individual file so its up to you to pick a good value. I would be pleased about some experienced data from same environments (Windows NTFS Filesystem). thanks in advance and greetings, Oliver Mohre ___ 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 ___ 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] Media Server with multiple NICS
Paul, Each NIC on the media server should have a separate IP. Assign each IP a name in dns Ensure that the static routes are set up correctly between the media server and the clients. This part is critical. This means if you run a traceroute from teh media server to the client it is sending the packet out the correct NIC on the media server to the correct NIC on the client. Set up a unique storage unit for each IP assigned to a NIC servicing clients on the media server. As a suggestion, use the DNS name assigned to that IP. You will need at least one policy per storage unit. Consider naming the policy based on the underlying the storage unit. Group the appropriate clients in the appropriate policies. Other pertinent settings are MPX, multipstreaming, and vault duplication. Here are questions for you; what type of storage units are you using? Are you going directly to tape, VTL or to a DSU first? What kind of DSU? Do you use SSO? Do you use vault? Do the clients have multiple NICs as well? __ Jonathan Marianu (mah ree ah' nu) ATT Storage Planning and Design Architect (360) 597-6896 Work Hours 0800-1800 PST M-F Manager: Jim Taylor (dt3249) (678) 893-3170 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] 6.0MP6
Hello all, Anyone is already using 6.0mp6, that was released last Feb, 27 ? []'s Pedro Moranga AVISO: A informação contida neste e-mail, bem como em qualquer de seus anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) acima referido(s), podendo conter informações sigilosas e/ou legalmente protegidas. Caso você não seja o destinatário desta mensagem, informamos que qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de seus anexos é absolutamente proibida. Solicitamos que o remetente seja comunicado imediatamente, respondendo esta mensagem, e que o original desta mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão realizada a partir destes, sejam permanentemente apagados e/ou destruídos. Informações adicionais sobre nossa empresa podem ser obtidas no site http://sobre.uol.com.br/. NOTICE: The information contained in this e-mail and any attachments thereto is CONFIDENTIAL and is intended only for use by the recipient named herein and may contain legally privileged and/or secret information. If you are not the e-mail´s intended recipient, you are hereby notified that any dissemination, distribution or copy of this e-mail, and/or any attachments thereto, is strictly prohibited. Please immediately notify the sender replying to the above mentioned e-mail address, and permanently delete and/or destroy the original and any copy of this e-mail and/or its attachments, as well as any printout thereof. Additional information about our company may be obtained through the site http://www.uol.com.br/ir/. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
