Re: [Veritas-bu] Fw: Question about posting to site
Sounds like you are in a jam. (Sorry - couldn't resist.) Patrick Sweeney (978) 787-4553 patrick.swee...@axcelis.com I.T. Systems/Networks For issues requiring immediate attention please contact the Solution Center IT Solution Center (978) 787- beverly.helpd...@axcelis.com Axcelis Technologies Have you searched here and here? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of debbie.l...@jmsmucker.com Sent: Thursday, December 11, 2008 2:16 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Fw: Question about posting to site This is a follow-up message from the email I sent, that is listed below. Can you please let me know if this is ok and I will send you the email with the link for the survey. Thank you. P.S. I am running out of time to get this completed. Thanks again. Debbie Lang Sr. System Administrator The J. M. Smucker Company (330) 684-3990 - Forwarded by Debbie Lang/MIS/Corporate/JMS on 12/11/2008 02:14 PM - | | From: | | --| |Debbie Lang/MIS/Corporate/JMS | --| | | To:| | --| |mailman-ow...@mailman.eng.auburn.edu | --| | | Date: | | --| |12/01/2008 08:48 AM | --| | | Subject: | | --| |Question about posting to site | --| I would like to ask permission it I can post a survey question. This survey is a requirement for completing my project that is necessary for receiving my bachelor's degree in Business Management from Malone University. The survey will be accessed via a weblink and will be kept completely confidential. Please let me know if I can send you my email to post to your website. Thanks, Debbie Lang (also Student at Malone University) Sr. System Administrator The J. M. Smucker Company (330) 684-3990 - Notice: The information contained in this electronic mail transmission is intended by The J.M. Smucker Company (or one of its subsidiaries) for the sole use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please notify the sender of the error by reply email so that our address record can be corrected. Thank you. ___ 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] Fw: Question about posting to site
God, PRESERVE us from bad puns... -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Sweeney, Patrick Sent: Friday, December 12, 2008 9:01 AM To: 'debbie.l...@jmsmucker.com'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Fw: Question about posting to site Sounds like you are in a jam. (Sorry - couldn't resist.) Patrick Sweeney (978) 787-4553 patrick.swee...@axcelis.com I.T. Systems/Networks For issues requiring immediate attention please contact the Solution Center IT Solution Center (978) 787- beverly.helpd...@axcelis.com Axcelis Technologies Have you searched here and here? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of debbie.l...@jmsmucker.com Sent: Thursday, December 11, 2008 2:16 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Fw: Question about posting to site This is a follow-up message from the email I sent, that is listed below. Can you please let me know if this is ok and I will send you the email with the link for the survey. Thank you. P.S. I am running out of time to get this completed. Thanks again. Debbie Lang Sr. System Administrator The J. M. Smucker Company (330) 684-3990 - Forwarded by Debbie Lang/MIS/Corporate/JMS on 12/11/2008 02:14 PM - | | From: | | --- ---| |Debbie Lang/MIS/Corporate/JMS | --- ---| | | To:| | --- ---| |mailman-ow...@mailman.eng.auburn.edu | --- ---| | | Date: | | --- ---| |12/01/2008 08:48 AM | --- ---| | | Subject: | | --- ---| |Question about posting to site | --- ---| I would like to ask permission it I can post a survey question. This survey is a requirement for completing my project that is necessary for receiving my bachelor's degree in Business Management from Malone University. The survey will be accessed via a weblink and will be kept completely confidential. Please let me know if I can send you my email to post to your website. Thanks, Debbie Lang (also Student at Malone University) Sr. System Administrator The J. M. Smucker Company (330) 684-3990 - Notice: The information contained in this electronic mail transmission is intended by The J.M. Smucker Company (or one of its subsidiaries) for the sole use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please notify the sender of the error by reply email so that our address record can be corrected. Thank you. ___ 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 -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to plan out policy(schedules), [...]
Bob, This is a really well-thought-out answer to his question. Although I don't agree with ALL of your recommendations (I don't like frequency-based schedules for fulls), this is actually a pretty good summary of what someone should do to setup a new backup environment. You've inspired me to blog about the same. (Of course, I may use my own opinions...) ;) Curtis Preston | VP Data Protection GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: +1 760 710 2009 cpres...@glasshouse.com | www.glasshouse.com Infrastructure :: Optimized -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of bob944 Sent: Saturday, December 06, 2008 6:37 PM To: veritas-bu@mailman.eng.auburn.edu Cc: boloba...@gmail.com Subject: Re: [Veritas-bu] How to plan out policy(schedules), [...] All other advice you receive will be more complicated and that's fine if it makes more sense to you. My philosophy here is to make your NetBackup as simple and self-maintaing as possible; every exception (and there will be some) is a cost. I am very new to NBU. Our enviornment has 300 intell and 100 unix system.We have 1 master ( sun t5120) for entire enviornment and 2 media ( sun x4500 disk storage) for lan based backup. one media server ( sun t5220 ) for SAN client for exchange and RMAN. One more media server ( sun t5220 ) for NDMP backup. We also have stk 8500 tape library. So you need a (emphasis: a) windows policy, a standard, an Exchange, an Oracle and an NDMP. If you'll have long-running backups, set as long a checkpoint interval as you can stand. Give every policy some default priority, say, 1000 (sooner or later, you'll have something that should run as low-priority but if all the policies are 0, there's no lower setting). Set allow multiple data streams. Our plan is to have 45 days retention for all data Personally, I wouldn't save incremenal data for more than two fulls, but since a single retention period is simpler and meets your needs, let's use it. But rather than create a custom retention period let's use one that's already in NetBackup, say 2 months. (Though I love to fiddle with and customize things personally, I prefer to leave everything as stock as possible and still meet the business requirements--every customization adds to the list of things that have to be replicated in the future. If you have a Real Business Need for 45 days, or if the extra retention will cause you to buy more storage, then go ahead and customize a retention level.) and do increamental daiy and full on weekend. Don't do that. Figure out your backup window, say 2000-0600, and set full and incremental frequency-based schedules the same, every day. (Remember that the end time of a window is the last time a policy can automatically _start_, so if a queued backup starting at 0550 and running for a couple of hours is too late, use an earlier time than 0600.) Your weekly fulls will run every seven days (and that day's incremental will not). (There are half a dozen ways to avoid doing a disproportionate number of fulls on a weeknight; the simplest is to just add, say, 10% of your clients to policies every weekday and the rest on Friday; a client/policy's first backup will be a full.) For windows and standard policies selection lists: ALL_LOCAL_DRIVES. Set up (you and/or your clients) excludes for database files, for netbackup/db/images and your disk STUs (yes, include your NetBackup servers in the standard policy for simplicity) and for any other data the client doesn't want/need backed up and make the client responsible for managing it--that's why exclude/include lists are on the client in the first place. For database policies, have all clients use the same name and location for the script. As of now we not planning for cloning ( VAULT ( offsite)). There is alos plan to migrate data if LAN media server ( x4500) fills to 80% to Tape library. NDMP and SAN client backup will go directly to 8500. That sounds as if you're going to have one copy of some backups on disk (only) and one copy of others on tape (only). If the loss of backups due to failed disk or failed tape is acceptable, fine. If that's not acceptable, use Storage Lifecycle Policies to do the duplications; SLPs can easily do duplications integrated into the backup period rather than the big vault batches usually done in off-hours. Two SLPs (one disk-to-tape, the other tape-to-tape) will cover both duplications in your setup. Use the storage unit groups for destinations. stgunit, stggroup, Storage units are almost self-defining. Device discovery for the tape drives and supply a disk path to create basic disk storage units. Reduce the fragment size only if you will be doing significant smounts of individual file restores. Multiplex the tape STUs to something like 8 or even 32 (and control the actual multiplexing used in the
Re: [Veritas-bu] How to plan out policy(schedules), [...]
On Fri, Dec 12, 2008 at 9:34 AM, Curtis Preston cpres...@glasshouse.comwrote: Bob, This is a really well-thought-out answer to his question. Although I don't agree with ALL of your recommendations (I don't like frequency-based schedules for fulls), this is actually a pretty good summary of what someone should do to setup a new backup environment. You've inspired me to blog about the same. (Of course, I may use my own opinions...) ;) The key opinion that we all know you'll disagree with is one policy per server, which Bob apparently doesn't like and we know that you. The man in the suit vs the man in the yellow shirt discussion, for those of who were at the customer forum in Roseville in October. :-) Personally, I agree with Bob on frequency-based schedules for fulls. Calendar-based schedules only make sense if you have a strict business requirement for say, an end-of-quarter backup after the books close. The key thing to always remember is to keep things as absolutely simple as possible. Make it easy for other people (new employees, support folks, contractors) to see what the heck you've done a year or more after you set it up. The more complicated you make it, the harder it is to support. The more you deviate from a normal configuration, the more likely it is you'll trigger bugs in future NetBackup releases. Simple is good. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to plan out policy(schedules), [...]
I agree with Ed I am the guy in the Jeans and T-Shirt. 1) Nowt wrong with frequency schedules for Fulls! Use them all the time 2) Keep the Policies and Volumes to a LESS as possible. 3) Over complexing the system makes NBU harder to administer than it really, really needs to be ! Simon (White Shirt, Jeans, Trainers, NBU Admin) :-) From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts Sent: Friday, December 12, 2008 3:54 PM To: Curtis Preston Cc: bob...@attglobal.net; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] How to plan out policy(schedules), [...] On Fri, Dec 12, 2008 at 9:34 AM, Curtis Preston cpres...@glasshouse.com wrote: Bob, This is a really well-thought-out answer to his question. Although I don't agree with ALL of your recommendations (I don't like frequency-based schedules for fulls), this is actually a pretty good summary of what someone should do to setup a new backup environment. You've inspired me to blog about the same. (Of course, I may use my own opinions...) ;) The key opinion that we all know you'll disagree with is one policy per server, which Bob apparently doesn't like and we know that you. The man in the suit vs the man in the yellow shirt discussion, for those of who were at the customer forum in Roseville in October. :-) Personally, I agree with Bob on frequency-based schedules for fulls. Calendar-based schedules only make sense if you have a strict business requirement for say, an end-of-quarter backup after the books close. The key thing to always remember is to keep things as absolutely simple as possible. Make it easy for other people (new employees, support folks, contractors) to see what the heck you've done a year or more after you set it up. The more complicated you make it, the harder it is to support. The more you deviate from a normal configuration, the more likely it is you'll trigger bugs in future NetBackup releases. Simple is good. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Fw: Survey Posted - Thanks
Below is the link to my survey. Thank you for your help. I will post my findings when completed. Survey is on Reducing Costs of Backups. http://www.surveymonkey.com/s.aspx?sm=v6a2TZ4h4U2DVmZZzP2yGA_3d_3d I hope you have time to help me out of my JAM !!! If you have any additional questions please feel free to send to email account listed below. Thanks again, Debbie Lang Student at Malone University and Sr. System Admin at The J. M. Smucker Company. dlm...@ymail.com | | From: | | --| |Sweeney, Patrick patrick.swee...@axcelis.com | --| | | To:| | --| |'debbie.l...@jmsmucker.com' debbie.l...@jmsmucker.com, veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu | --| | | Date: | | --| |12/12/2008 09:01 AM | --| | | Subject: | | --| |RE: [Veritas-bu] Fw: Question about posting to site | --| Sounds like you are in a jam. (Sorry - couldn't resist.) Patrick Sweeney (978) 787-4553 patrick.swee...@axcelis.com I.T. Systems/Networks For issues requiring immediate attention please contact the Solution Center IT Solution Center (978) 787- beverly.helpd...@axcelis.com Axcelis Technologies Have you searched here and here? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [ mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of debbie.l...@jmsmucker.com Sent: Thursday, December 11, 2008 2:16 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Fw: Question about posting to site This is a follow-up message from the email I sent, that is listed below. Can you please let me know if this is ok and I will send you the email with the link for the survey. Thank you. P.S. I am running out of time to get this completed. Thanks again. Debbie Lang Sr. System Administrator The J. M. Smucker Company (330) 684-3990 - Forwarded by Debbie Lang/MIS/Corporate/JMS on 12/11/2008 02:14 PM - | | From: | | --| |Debbie Lang/MIS/Corporate/JMS | --| | | To:| | --| |mailman-ow...@mailman.eng.auburn.edu | --| | | Date: | | --| |12/01/2008 08:48 AM | --| | | Subject: | | --| |Question about posting to site |
Re: [Veritas-bu] How to plan out policy(schedules), [...]
This is a really well-thought-out answer to his question. Although I don't agree with ALL of your recommendations (I don't like frequency-based schedules for fulls), this is actually a pretty good summary of what someone should do to setup a new backup environment. You've inspired me to blog about the same. (Of course, I may use my own opinions...) ;) Thank you, Curtis. I'm just a simple guy; complex setups make my hair hurt and I've have had enough Oops, forgot about moments that I use simplicity to minimize them. The other approach that I love (though I'd never implement it unless I had beaucoup time to get the coding right end-to-end) is the exact opposite: one person on this list (sorry, I don't rember who you are) who has a bajillion clients with a policy for each one with an automated setup, like a scratch-built backup provisioning system. Took a week for the concept to grow on me, and I can see it for a very experienced shop with a fluid mix of clients. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Using NetBackup to backup a DPM server
Greetings - Is there anyone on this list who is successfully backing up a DPM server from a Unix or Linux NetBackup server? If so, would you mind sharing your secrets? I've read the applicable sections of the DPM manuals and it looks like work on the client side is required for a successful backup from a Unix NetBackup server. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Full backup followed by a Differential= Another Full
Thanks for the replies/pointers to this question. The 200644.htm doc was helpful. Now, I've tested 3 environments: Isilon - NDMP; NetApp - NDMP and Solaris - Standard backup. In each case, I used a chgrp command to change the ctime of a small set of files. I then kicked off a Differential for that client. And in each case the small set of files that I had changed were included in the Differential Incremental for each client. I don't have USE_CTIME_FOR_INCREMENTALS in any bp.conf files on clients/media servers or master server. So, I'm still confused, and I guess I'll open up a ticket with Symantec to try and get to the bottom of this. Thanks again, Randy From: Donaldson, Mark mark.donald...@staples.com To: Randy Doering rdoeri...@verizon.net; A Darren Dunham ddun...@taos.com; Veritas-bu@mailman.eng.auburn.edu Sent: Wednesday, December 10, 2008 6:37:52 PM Subject: RE: [Veritas-bu] Full backup followed by a Differential= Another Full Netbackup, by default, uses mtime for incrementals. It can be configured to use C-time in bp.conf but that's not usual at all. More here: http://seer.support.veritas.com/docs/200644.htm -M -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Randy Doering Sent: Wednesday, December 10, 2008 3:42 PM To: A Darren Dunham; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Full backup followed by a Differential= Another Full Mystery solved - or so it seems. Last week we had a helpdesk ticket where the user wanted some chmod/chgrp modifications of all files/directories in this area. My co-worker did that on Thursday/Friday of last week. Seems this changes the ChangeTime (ctime), which NBU is using for determining if something has Changed. I then did a Differential, and it was looking at the ctime. For one of the files: stat error.txt File: `error.txt' Size: 338713 Blocks: 962 IO Block: 4096 regular file Device: 1dh/29d Inode: 4365470520 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 2370/ cgoina) Gid: ( 9003/jtc-solexa) Access: 2008-10-15 09:44:41.235029187 -0400 Modify: 2008-10-15 09:44:41.235029187 -0400 Change: 2008-12-09 19:00:21.895757388 -0500 Turns out, the chmod/chgrp needed to be rerun on Monday/Tuesday this week. Is there a way for NBU to look at mtime instead of ctime? Thanks, Randy - Original Message - From: A Darren Dunham ddun...@taos.com To: Veritas-bu@mailman.eng.auburn.edu Sent: Wednesday, December 10, 2008 11:23 AM Subject: Re: [Veritas-bu] Full backup followed by a Differential = Another Full On Wed, Dec 10, 2008 at 07:42:41AM -0800, Randy Doering wrote: Backup Client = Isilon NAS Unit - NDMP. NBU version is 6.5.3. With this?one (10+TBs, 1,643,099 files) during the backup NBU said it was doing a Differential, but when it was all done, it had actually backedup everything again. If I kick off another Differential this coming weekend, I certainly don't want to have yet another backup that gets all of the data once again. Any thoughts? Since this is NDMP, Netbackup isn't making any of the file level decisions. It's just passing a set of parameters to the host (dump level, date of backup, file path, tape drive, etc...) and letting the make the selections. I don't have it in my notes, but you can up the log level of ndmp on the isilon and view exactly what NBU is sending over. It'll show up in the ndmp logs. Ah. Found my notes... On any node of the cluster, edit the file /etc/mcp/templates/syslog.conf and change the line: *.=info /var/log/isi_ndmp_d to: *.* /var/log/isi_ndmp_d This should increase the logging levels on the cluster for ndmp. You may want to check with your support contacts before doing this, but it's just a log level change. With that in place, you can start a manual differential and see what it looks to be doing. You'll be able to kill it so it won't consume tapes for you. If nothing looks obviously wrong, you may have to contact support. Good luck! -- Darren ___ 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] How to plan out policy(schedules), [...]
Man in the suit, I'd like to hear your reasons against frequency based scheds. For my situation, I want a full backup once a week, once a month, once a quarter, once a year, etc. *I* don't care when it happens, though my customer might, though in most circumstances, backups should not hinder the performance of the box. In situations where a customer needs a backup on a specific day/day of the month, we'll use calendar, but I personally hate calendar because of the extra administration effort required to set it up so you don't suddenly stop getting backups in 2015 because someone was lazy and didn't finish it out. Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693 Keeping People and Information Connected® ▪ http://availability.sungard.com/ P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. Curtis Preston cpres...@glasshouse.com Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 12/12/2008 09:55 AM To bob...@attglobal.net, veritas-bu@mailman.eng.auburn.edu cc boloba...@gmail.com Subject Re: [Veritas-bu] How to plan out policy(schedules), [...] Bob, This is a really well-thought-out answer to his question. Although I don't agree with ALL of your recommendations (I don't like frequency-based schedules for fulls), this is actually a pretty good summary of what someone should do to setup a new backup environment. You've inspired me to blog about the same. (Of course, I may use my own opinions...) ;) Curtis Preston | VP Data Protection GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: +1 760 710 2009 cpres...@glasshouse.com | www.glasshouse.com Infrastructure :: Optimized -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of bob944 Sent: Saturday, December 06, 2008 6:37 PM To: veritas-bu@mailman.eng.auburn.edu Cc: boloba...@gmail.com Subject: Re: [Veritas-bu] How to plan out policy(schedules), [...] All other advice you receive will be more complicated and that's fine if it makes more sense to you. My philosophy here is to make your NetBackup as simple and self-maintaing as possible; every exception (and there will be some) is a cost. I am very new to NBU. Our enviornment has 300 intell and 100 unix system.We have 1 master ( sun t5120) for entire enviornment and 2 media ( sun x4500 disk storage) for lan based backup. one media server ( sun t5220 ) for SAN client for exchange and RMAN. One more media server ( sun t5220 ) for NDMP backup. We also have stk 8500 tape library. So you need a (emphasis: a) windows policy, a standard, an Exchange, an Oracle and an NDMP. If you'll have long-running backups, set as long a checkpoint interval as you can stand. Give every policy some default priority, say, 1000 (sooner or later, you'll have something that should run as low-priority but if all the policies are 0, there's no lower setting). Set allow multiple data streams. Our plan is to have 45 days retention for all data Personally, I wouldn't save incremenal data for more than two fulls, but since a single retention period is simpler and meets your needs, let's use it. But rather than create a custom retention period let's use one that's already in NetBackup, say 2 months. (Though I love to fiddle with and customize things personally, I prefer to leave everything as stock as possible and still meet the business requirements--every customization adds to the list of things that have to be replicated in the future. If you have a Real Business Need for 45 days, or if the extra retention will cause you to buy more storage, then go ahead and customize a retention level.) and do increamental daiy and full on weekend. Don't do that. Figure out your backup window, say 2000-0600, and set full and incremental frequency-based schedules the same, every day. (Remember that the end time of a window is the last time a policy can automatically _start_, so if a queued backup starting at 0550 and running for a couple of hours is too late, use an earlier time than 0600.) Your weekly fulls will run every seven days (and that day's incremental will not). (There are half a dozen ways to avoid doing a disproportionate number of fulls on a weeknight; the simplest is to just add, say, 10% of your clients to policies every weekday and the rest on Friday; a client/policy's first backup will be a full.) For windows and standard policies selection lists: ALL_LOCAL_DRIVES. Set up (you and/or your clients) excludes for database files, for netbackup/db/images and your disk STUs (yes, include your NetBackup servers in the
[Veritas-bu] NetApp vs. SAN Media Server
Hi Kids, I have a Windows environment and NBU 6.5.2a. I have a SAN Media Server that houses and backs up my SQL dumps. Those backups run the longest but by far the fastest. My SAN guys purchased a NetApp device and have decided to have the SQL dumps write directly to the NetApp device and implement NDMP for backups. I have absolutely no experience with NDMP so can someone out in NBU land tell me if my backups are going to be slower :( faster :) somewhere in between :|? Thanks, Randy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetApp vs. SAN Media Server
On Fri, Dec 12, 2008 at 2:23 PM, Randy Samora randy.sam...@stewart.comwrote: I have a Windows environment and NBU 6.5.2a. I have a SAN Media Server that houses and backs up my SQL dumps. Those backups run the longest but by far the fastest. My SAN guys purchased a NetApp device and have decided to have the SQL dumps write directly to the NetApp device and implement NDMP for backups. I have absolutely no experience with NDMP so can someone out in NBU land tell me if my backups are going to be slower :( faster :) somewhere in between :|? NDMP is *fast* on a NetApp filer. We're doing NDMP directly to tape and have also done it to DSSU. Don't forget that you need to purchase the NDMP license. And the tiering is funny (even number for a single head and odd number for a clustered filer). With snapshots enabled on the filer, the chances are pretty good you won't ever have to do a restore for your SQL admins. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetApp vs. SAN Media Server
Thanks Ed. I'm pricing the NDMP license now and it isn't going to be cheap. From: Ed Wilts [mailto:ewi...@ewilts.org] Sent: Friday, December 12, 2008 14:46: VIRUS ALERT! To: Randy Samora Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NetApp vs. SAN Media Server On Fri, Dec 12, 2008 at 2:23 PM, Randy Samora randy.sam...@stewart.com wrote: I have a Windows environment and NBU 6.5.2a. I have a SAN Media Server that houses and backs up my SQL dumps. Those backups run the longest but by far the fastest. My SAN guys purchased a NetApp device and have decided to have the SQL dumps write directly to the NetApp device and implement NDMP for backups. I have absolutely no experience with NDMP so can someone out in NBU land tell me if my backups are going to be slower :( faster :) somewhere in between :|? NDMP is *fast* on a NetApp filer. We're doing NDMP directly to tape and have also done it to DSSU. Don't forget that you need to purchase the NDMP license. And the tiering is funny (even number for a single head and odd number for a clustered filer). With snapshots enabled on the filer, the chances are pretty good you won't ever have to do a restore for your SQL admins. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Fw: Survey Posted - Thanks
In your What part of the United States are you located in? question, you need a Not located in the United States option. Or, make it clear up front that you are only interested in hearing from people in the US. Cheers, Dean ;) On Sat, Dec 13, 2008 at 3:46 AM, debbie.l...@jmsmucker.com wrote: Below is the link to my survey. Thank you for your help. I will post my findings when completed. Survey is on Reducing Costs of Backups. http://www.surveymonkey.com/s.aspx?sm=v6a2TZ4h4U2DVmZZzP2yGA_3d_3d I hope you have time to help me out of my JAM !!! If you have any additional questions please feel free to send to email account listed below. Thanks again, Debbie Lang Student at Malone University and Sr. System Admin at The J. M. Smucker Company. dlm...@ymail.com | | From: | | --| |Sweeney, Patrick patrick.swee...@axcelis.com | --| | | To:| | --| |'debbie.l...@jmsmucker.com' debbie.l...@jmsmucker.com, veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu | --| | | Date: | | --| |12/12/2008 09:01 AM | --| | | Subject: | | --| |RE: [Veritas-bu] Fw: Question about posting to site | --| Sounds like you are in a jam. (Sorry - couldn't resist.) Patrick Sweeney (978) 787-4553 patrick.swee...@axcelis.com I.T. Systems/Networks For issues requiring immediate attention please contact the Solution Center IT Solution Center (978) 787- beverly.helpd...@axcelis.com Axcelis Technologies Have you searched here and here? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [ mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of debbie.l...@jmsmucker.com Sent: Thursday, December 11, 2008 2:16 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Fw: Question about posting to site This is a follow-up message from the email I sent, that is listed below. Can you please let me know if this is ok and I will send you the email with the link for the survey. Thank you. P.S. I am running out of time to get this completed. Thanks again. Debbie Lang Sr. System Administrator The J. M. Smucker Company (330) 684-3990 - Forwarded by Debbie Lang/MIS/Corporate/JMS on 12/11/2008 02:14 PM - | | From: | | --| |Debbie Lang/MIS/Corporate/JMS | --| | | To:| | --| |mailman-ow...@mailman.eng.auburn.edu | --| | | Date: | | --| |12/01/2008 08:48 AM | --| | | Subject: | |
Re: [Veritas-bu] NetApp vs. SAN Media Server
On Fri, Dec 12, 2008 at 02:23:26PM -0600, Randy Samora wrote: Hi Kids, I have a Windows environment and NBU 6.5.2a. I have a SAN Media Server that houses and backs up my SQL dumps. Those backups run the longest but by far the fastest. My SAN guys purchased a NetApp device and have decided to have the SQL dumps write directly to the NetApp device and implement NDMP for backups. I have absolutely no experience with NDMP so can someone out in NBU land tell me if my backups are going to be slower :( faster :) somewhere in between :|? Yes they will. :-) NDMP isn't faster or slower, it's just different. In many situations it will be faster because you can avoid some bottlenecks, but it depends on how you set things up. NDMP can write directly to a tape, go over networks, through other machines, etc. Network appliance filers will prefer to schedule user data service over NDMP service. So if you have a filer that's running low on horsepower (but still very zippy with serving data), you can find that NDMP jobs crawl. But most of the time the same things that make NDMP slow make other backups slow (lots of tiny files, overloaded networks) -- Darren ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to plan out policy(schedules), [...]
I am a proponent of the one-client-per-policy design. I've blogged about it: http://www.backupcentral.com/content/blogsection/4/47/ Curtis Preston | VP Data Protection GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: +1 760 710 2009 cpres...@glasshouse.com | www.glasshouse.com Infrastructure :: Optimized -Original Message- From: bob944 [mailto:bob...@attglobal.net] Sent: Friday, December 12, 2008 9:47 AM To: veritas-bu@mailman.eng.auburn.edu Cc: Curtis Preston Subject: RE: [Veritas-bu] How to plan out policy(schedules), [...] This is a really well-thought-out answer to his question. Although I don't agree with ALL of your recommendations (I don't like frequency-based schedules for fulls), this is actually a pretty good summary of what someone should do to setup a new backup environment. You've inspired me to blog about the same. (Of course, I may use my own opinions...) ;) Thank you, Curtis. I'm just a simple guy; complex setups make my hair hurt and I've have had enough Oops, forgot about moments that I use simplicity to minimize them. The other approach that I love (though I'd never implement it unless I had beaucoup time to get the coding right end-to-end) is the exact opposite: one person on this list (sorry, I don't rember who you are) who has a bajillion clients with a policy for each one with an automated setup, like a scratch-built backup provisioning system. Took a week for the concept to grow on me, and I can see it for a very experienced shop with a fluid mix of clients. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Best exclude list for Windows, solaris, linux ?
You can also use bpgetconfig and bpsetconfig. Curtis Preston | VP Data Protection GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: +1 760 710 2009 cpres...@glasshouse.com | www.glasshouse.com Infrastructure :: Optimized -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Servet Ince Sent: Friday, December 05, 2008 6:12 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Best exclude list for Windows, solaris, linux ? Hi, I've been trying to exclude something (.jpeg, .avi) on the windows client, but It doesn't work, I don't know why! If I give Full path including the file name, at that time it works. Otherwise, like if I write '*.jpg'; it doesn't work:( By the way; You should add more paths. There are 3 ways to do it; 1.) On the Client Properties from Master GUI. There is 'Exclude List' under the Windows Client option. 2.) There is 'Client Properties' on Backup, Archive and Restore GUI at Client site. There should be 'Exclude List'. You can add the path to there. 3.) You can create a file under '\InstallPath\ProgramFiles\Veritas\Netbackup' and name it as 'exclude_list' then put the path in it. FYI. Servet -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of toaster Sent: Friday, December 05, 2008 4:00 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Best exclude list for Windows, solaris, linux ? Hi guys, I was wondering what was your exlude list on Windows client? I found only 1 mention of this on symantec site: http://seer.entsupport.symantec.com/docs/182189.htm witch is : C:\VERITAS\NetBackup\bin\bpdbm.lock C:\VERITAS\NetBackup\bin\bprd.d\*.lock C:\VERITAS\NetBackup\bin\bprd.lock C:\VERITAS\NetBackup\bin\bpsched.d\*.lock C:\VERITAS\Volmgr\misc\* But i think that i can include more like: c:\temp c:\windows\temp What else can be exlude for backup?Same question for Solaris, Linux client :) +-- |This was sent by hero...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to plan out policy(schedules), [...]
Suit!?!?! Them’s fightin’ words! I need to do a blog on this, as I answer this question a lot. If you want to do weekly backups using frequency based schedules, here are your choices. 1. Leave the window open only on the night you want the backup to run. Schedules that succeed that night will be fine. BUT if it fails that night, it won’t retry until next week. Yuck. 2. Leave all nights’ windows open. When the backup that’s supposed to run Monday fails and then runs on Tuesday, it will always run on Tuesday from then on because that will be when it meets the frequency of 7 days. Full backups end up creeping around and bunching together. I HATE this one as it’s unpredictable over time. I’ve seen it where over time all my full backups were running on the same night. (I like to spread them out.) 3. Leave a few days’ windows open (say, 3), and set a frequency of 4 days. This causes NBU to try on the first day with an open window, then retry on the second/third if it fails. You have the retry feature that calendar-based backups have without the schedule creep problem because you have a frequency of four days. (This is the best of the three, IMHO.) The schedule-creep problem is compounded by manual backups. If you ever do a manual backup, the frequency will be calculated from that day. Suppose you chose option three above and opened the windows for Friday, Saturday, and Sunday night, and put a frequency of four days. If you happened to run a manual full backup on Thursday night, your regular full backup won’t run that weekend. _I_ like to do monthly full backups and weekly cumulative incremental backups. The above problems are compounded when you want to do this. You can’t reliably predict what night the fulls are going to run, and can’t easily spread them out across the month (which I like to do). It’s much easier to spread them out using calendar based schedules. You take some clients and tell them to do their full on the 1st Friday of the month, and their cumulative incremental every Friday. When the two “clash” on the 1st Friday, the full takes precedence and runs. Every other Friday it will run a cumulative incremental. As for the failed backup problem, you just check “allow after run day,” and it will retry the backups until they succeed, and this won’t mess in any way with when they’ll run the next time. Also, running manual full backups won’t mess with the schedule either. The manual tells you not to mix calendar and frequency backups. I don’t like calendar backups for daily backups, so some see this as a problem. BUT I’ve found that if you monthly full, weekly cumulative, and daily (frequency based) incremental all have the same windows, the frequency-based schedule will take precedence and run when the others aren’t running and the calendar backups will take precedence when it’s time for them to run. You just have to keep the windows the same. The only goofy thing about calendar-based schedules (and it really annoys me) is that most people use a 6 PM to 6 AM clock (or some evening hour to some morning hour). If you tell NBU to do the full on the 1st Friday of the month and leave all windows open, it will actually run the backup at just after midnight on Friday (Thursday night). That’s probably not what you wanted. So you have to delete the window for the night before (in this case, Thursday). I hate it, but I’ve learned to live with it. Both methods have issues. I prefer the predictability of the calendar-based method. Curtis Preston | VP Data Protection GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: +1 760 710 2009 cpres...@glasshouse.com | www.glasshouse.com http://www.glasshouse.com/ Infrastructure :: Optimized This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to plan out policy(schedules), [...]
On Fri, Dec 12, 2008 at 06:31:20PM -0500, Curtis Preston wrote: The only goofy thing about calendar-based schedules (and it really annoys me) is that most people use a 6 PM to 6 AM clock (or some evening hour to some morning hour). If you tell NBU to do the full on the 1st Friday of the month and leave all windows open, it will actually run the backup at just after midnight on Friday (Thursday night). That?s probably not what you wanted. So you have to delete the window for the night before (in this case, Thursday). I hate it, but I?ve learned to live with it. I know this happens to a lot of folks, but I've never experienced this in 5.1 and 6.0. I have midnight-crossing start windows and Full backup schedules set for last day of month. They all start at the opening of the window on the afternoon of the last day, not at midnight that day (which would be valid, but is part of the previous day's window). Not sure what my installation is doing that others aren't, but I'm very happy it works this way. -- Darren ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to plan out policy(schedules), [...]
Hmmm... Looks like I've got some testing to do. Curtis Preston | VP Data Protection GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: +1 760 710 2009 cpres...@glasshouse.com | www.glasshouse.com Infrastructure :: Optimized -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of A Darren Dunham Sent: Friday, December 12, 2008 3:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] How to plan out policy(schedules), [...] On Fri, Dec 12, 2008 at 06:31:20PM -0500, Curtis Preston wrote: The only goofy thing about calendar-based schedules (and it really annoys me) is that most people use a 6 PM to 6 AM clock (or some evening hour to some morning hour). If you tell NBU to do the full on the 1st Friday of the month and leave all windows open, it will actually run the backup at just after midnight on Friday (Thursday night). That?s probably not what you wanted. So you have to delete the window for the night before (in this case, Thursday). I hate it, but I?ve learned to live with it. I know this happens to a lot of folks, but I've never experienced this in 5.1 and 6.0. I have midnight-crossing start windows and Full backup schedules set for last day of month. They all start at the opening of the window on the afternoon of the last day, not at midnight that day (which would be valid, but is part of the previous day's window). Not sure what my installation is doing that others aren't, but I'm very happy it works this way. -- Darren ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to plan out policy(schedules), [...]
On Sat, Dec 13, 2008 at 10:31 AM, Curtis Preston cpres...@glasshouse.comwrote: Suit!?!?! Them's fightin' words! I need to do a blog on this, as I answer this question a lot. If you want to do weekly backups using frequency based schedules, here are your choices. 1. Leave the window open only on the night you want the backup to run. Schedules that succeed that night will be fine. BUT if it fails that night, it won't retry until next week. Yuck. 2. Leave all nights' windows open. When the backup that's supposed to run Monday fails and then runs on Tuesday, it will always run on Tuesday from then on because that will be when it meets the frequency of 7 days. Full backups end up creeping around and bunching together. I HATE this one as it's unpredictable over time. I've seen it where over time all my full backups were running on the same night. (I like to spread them out.) 3. Leave a few days' windows open (say, 3), and set a frequency of 4 days. This causes NBU to try on the first day with an open window, then retry on the second/third if it fails. You have the retry feature that calendar-based backups have without the schedule creep problem because you have a frequency of four days. (This is the best of the three, IMHO.) The schedule-creep problem is compounded by manual backups. If you ever do a manual backup, the frequency will be calculated from that day. Suppose you chose option three above and opened the windows for Friday, Saturday, and Sunday night, and put a frequency of four days. If you happened to run a manual full backup on Thursday night, your regular full backup won't run that weekend. I agree 100% with Curtis on this. If you have a large environment with drives/resources being super utilised schedule creep can and is disastrous. Not to mention client X expected his full to run on day Y and needed to backout from a change based on the full backup - woops! _*I*_ like to do monthly full backups and weekly cumulative incremental backups. The above problems are compounded when you want to do this. You can't reliably predict what night the fulls are going to run, and can't easily spread them out across the month (which I like to do). It's much easier to spread them out using calendar based schedules. You take some clients and tell them to do their full on the 1st Friday of the month, and their cumulative incremental every Friday. When the two clash on the 1 st Friday, the full takes precedence and runs. Every other Friday it will run a cumulative incremental. As for the failed backup problem, you just check allow after run day, and it will retry the backups until they succeed, and this won't mess in any way with when they'll run the next time. Also, running manual full backups won't mess with the schedule either. The manual tells you not to mix calendar and frequency backups. I don't like calendar backups for daily backups, so some see this as a problem. BUT I've found that if you monthly full, weekly cumulative, and daily (frequency based) incremental all have the same windows, the frequency-based schedule will take precedence and run when the others aren't running and the calendar backups will take precedence when it's time for them to run. You just have to keep the windows the same. The only goofy thing about calendar-based schedules (and it really annoys me) is that most people use a 6 PM to 6 AM clock (or some evening hour to some morning hour). If you tell NBU to do the full on the 1st Friday of the month and leave all windows open, it will actually run the backup at just after midnight on Friday (Thursday night). That's probably not what you wanted. So you have to delete the window for the night before (in this case, Thursday). I hate it, but I've learned to live with it. Both methods have issues. I prefer the predictability of the calendar-based method. *Curtis Preston | VP Data Protection** *GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: +1 760 710 2009 cpres...@glasshouse.com | www.glasshouse.com *Infrastructure :: Optimized* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ___ 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
Re: [Veritas-bu] NetApp vs. SAN Media Server
On Fri, Dec 12, 2008 at 4:52 PM, Curtis Preston cpres...@glasshouse.comwrote: Ed Wilts said: With snapshots enabled on the filer, the chances are pretty good you won't ever have to do a restore for your SQL admins. Because he's creating a new dump each day, I'm not sure that's true. Snapshots only work the way you describe if you're modifying files, not completely overwriting them every day. Say what? 1. Create a sql dump file at 6pm. 2. Create a NetApp snapshot at 7pm 3. Repeat If you keep 7 days of snapshots, you'll be able to recover from the snapshot from daily.0, daily.1, ... daily.6. Snapshots appear to be full copies of the file system, whether anything has changed or not. It doesn't matter if you're modifying files, deleting files, or completely overwriting them. It's a good thing you're a backup expert and not claiming to be a NetApp expert :-) -- Ed Wilts, Mounds View, MN, USA ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetApp vs. SAN Media Server
With snapshots enabled on the filer, the chances are pretty good you won't ever have to do a restore for your SQL admins. .../Ed Alternatively, you could pony up for the Snap Manager for MS-SQL license, and you can make your DBA's do the backups AND restores. It links the process of quiescing the database with the netapp snapshot. Some assembly required. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
