Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1
But it worked :-) From: Clooney, David [mailto:[EMAIL PROTECTED] Sent: Thursday, January 31, 2008 10:14 AM To: Clooney, David; WEAVER, Simon (external); [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 remember its a soft SCSI release and not a hardware release. From: Clooney, David Sent: 31 January 2008 10:13 To: 'WEAVER, Simon (external)'; [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 vmoprcmd -crawlreleasebyname drive_name From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: 30 January 2008 16:54 To: [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 All I have 18 large Media Servers, all Win2k3, single TL with SSO and 12 drives. I tend to sort out most problems without bringing the whole lot down. When I do maintenance on the library, I shutdown all of the NBU Services first, then power down the library. Once the library is up, I then re-run device manager to scan for new hardware, and the drives and library come into play on each Media Server. In most cases this can be done remotely. Once the server sees the library, start the Master and then media servers and check drive status. In almost all cases, everything has come up fine. Yes a little pain, but its done in such an Art, it rarely takes that long to do this task. The one issue I had a problem with involved performing a scsi reset while NetBackup was idle due to a drive in a complete mixed state that could not recover from manually. (cant find the technote, but its a scsi release command to be done on all affected drive(s)). Apart from this, its mostly trouble free. If its working, I leave things well alone. The environment is 5.1 and soon to be moved to 6.x and if 6.x is as better than 5.1, then I look forward to this upgrade to make Admin Life easier. I agree, getting the right hardware and configuration in place is a must. S. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 30, 2008 4:23 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 I agree with Randy, I've had a lot of issues with the Media/SAN Media Windows servers. I would recommend that if you are pre 6.x, examine your backup requirements for each server and use teaming (I have also experienced problems with these) or Gig NICs when you can. Not only will this solution save you money, but it will also save you administration headache, regardless of Media server platform, when you do run into problems. -Rusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, January 30, 2008 9:11 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 NetBackup doesn't get it until version 6. I am 100% windows here with a mixture of 19 Media and SAN Media servers sharing a library with 24 drives. First, stabilize it. Zone your library and make sure that the only servers that can even see the library are servers that you want to see the library. Check HBA settings and disable removable storage service. Until you have the communication paths really stable between servers and drives, the problems won't ever cease. But once you have it stable, it typically will stay that way. However, in version 5.1, whenever I had to do any type of maintenance on my library causing it to lose connection to NetBackup servers, I had to reboot all of my NetBackup servers before I could get NetBackup to see the library again. My SAN Media servers are high profile servers and rebooting them periodically wasn't a popular activity with our customers. Microsoft said it wasn't Windows, Symantec said it wasn't NetBackup and I could never get a straight answer. But 6.0 doesn't have that problem. I can reboot the library all day long and as soon as it is back on line, NetBackup is back on line. Thanks, Randy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of X_S Sent: Wednesday, January 30, 2008 8:02 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 but would you implement such a large sso environment with Windows servers? we've shared 20,30,40 drives across many windows servers and it becomes hell whenever drives go offline and/or is replaced and then shuffles in the os. we've used persistent binding but this doesn't help with vtl drives. but sometimes, netbackup just doesn't get it. +-- |This
Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1
remember its a soft SCSI release and not a hardware release. From: Clooney, David Sent: 31 January 2008 10:13 To: 'WEAVER, Simon (external)'; [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 vmoprcmd -crawlreleasebyname drive_name From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: 30 January 2008 16:54 To: [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 All I have 18 large Media Servers, all Win2k3, single TL with SSO and 12 drives. I tend to sort out most problems without bringing the whole lot down. When I do maintenance on the library, I shutdown all of the NBU Services first, then power down the library. Once the library is up, I then re-run device manager to scan for new hardware, and the drives and library come into play on each Media Server. In most cases this can be done remotely. Once the server sees the library, start the Master and then media servers and check drive status. In almost all cases, everything has come up fine. Yes a little pain, but its done in such an Art, it rarely takes that long to do this task. The one issue I had a problem with involved performing a scsi reset while NetBackup was idle due to a drive in a complete mixed state that could not recover from manually. (cant find the technote, but its a scsi release command to be done on all affected drive(s)). Apart from this, its mostly trouble free. If its working, I leave things well alone. The environment is 5.1 and soon to be moved to 6.x and if 6.x is as better than 5.1, then I look forward to this upgrade to make Admin Life easier. I agree, getting the right hardware and configuration in place is a must. S. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 30, 2008 4:23 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 I agree with Randy, I've had a lot of issues with the Media/SAN Media Windows servers. I would recommend that if you are pre 6.x, examine your backup requirements for each server and use teaming (I have also experienced problems with these) or Gig NICs when you can. Not only will this solution save you money, but it will also save you administration headache, regardless of Media server platform, when you do run into problems. -Rusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, January 30, 2008 9:11 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 NetBackup doesn't get it until version 6. I am 100% windows here with a mixture of 19 Media and SAN Media servers sharing a library with 24 drives. First, stabilize it. Zone your library and make sure that the only servers that can even see the library are servers that you want to see the library. Check HBA settings and disable removable storage service. Until you have the communication paths really stable between servers and drives, the problems won't ever cease. But once you have it stable, it typically will stay that way. However, in version 5.1, whenever I had to do any type of maintenance on my library causing it to lose connection to NetBackup servers, I had to reboot all of my NetBackup servers before I could get NetBackup to see the library again. My SAN Media servers are high profile servers and rebooting them periodically wasn't a popular activity with our customers. Microsoft said it wasn't Windows, Symantec said it wasn't NetBackup and I could never get a straight answer. But 6.0 doesn't have that problem. I can reboot the library all day long and as soon as it is back on line, NetBackup is back on line. Thanks, Randy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of X_S Sent: Wednesday, January 30, 2008 8:02 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 but would you implement such a large sso environment with Windows servers? we've shared 20,30,40 drives across many windows servers and it becomes hell whenever drives go offline and/or is replaced and then shuffles in the os. we've used persistent binding but this doesn't help with vtl drives. but sometimes, netbackup just doesn't get it. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1
vmoprcmd -crawlreleasebyname drive_name From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: 30 January 2008 16:54 To: [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 All I have 18 large Media Servers, all Win2k3, single TL with SSO and 12 drives. I tend to sort out most problems without bringing the whole lot down. When I do maintenance on the library, I shutdown all of the NBU Services first, then power down the library. Once the library is up, I then re-run device manager to scan for new hardware, and the drives and library come into play on each Media Server. In most cases this can be done remotely. Once the server sees the library, start the Master and then media servers and check drive status. In almost all cases, everything has come up fine. Yes a little pain, but its done in such an Art, it rarely takes that long to do this task. The one issue I had a problem with involved performing a scsi reset while NetBackup was idle due to a drive in a complete mixed state that could not recover from manually. (cant find the technote, but its a scsi release command to be done on all affected drive(s)). Apart from this, its mostly trouble free. If its working, I leave things well alone. The environment is 5.1 and soon to be moved to 6.x and if 6.x is as better than 5.1, then I look forward to this upgrade to make Admin Life easier. I agree, getting the right hardware and configuration in place is a must. S. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 30, 2008 4:23 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 I agree with Randy, I've had a lot of issues with the Media/SAN Media Windows servers. I would recommend that if you are pre 6.x, examine your backup requirements for each server and use teaming (I have also experienced problems with these) or Gig NICs when you can. Not only will this solution save you money, but it will also save you administration headache, regardless of Media server platform, when you do run into problems. -Rusty From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, January 30, 2008 9:11 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 NetBackup doesn't get it until version 6. I am 100% windows here with a mixture of 19 Media and SAN Media servers sharing a library with 24 drives. First, stabilize it. Zone your library and make sure that the only servers that can even see the library are servers that you want to see the library. Check HBA settings and disable removable storage service. Until you have the communication paths really stable between servers and drives, the problems won't ever cease. But once you have it stable, it typically will stay that way. However, in version 5.1, whenever I had to do any type of maintenance on my library causing it to lose connection to NetBackup servers, I had to reboot all of my NetBackup servers before I could get NetBackup to see the library again. My SAN Media servers are high profile servers and rebooting them periodically wasn't a popular activity with our customers. Microsoft said it wasn't Windows, Symantec said it wasn't NetBackup and I could never get a straight answer. But 6.0 doesn't have that problem. I can reboot the library all day long and as soon as it is back on line, NetBackup is back on line. Thanks, Randy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of X_S Sent: Wednesday, January 30, 2008 8:02 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Whats Best Practice for SSO in NBU 5.1 but would you implement such a large sso environment with Windows servers? we've shared 20,30,40 drives across many windows servers and it becomes hell whenever drives go offline and/or is replaced and then shuffles in the os. we've used persistent binding but this doesn't help with vtl drives. but sometimes, netbackup just doesn't get it. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 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
[Veritas-bu] Another bpstart, oracle and streams question
Guys im running Netbackup 6.0mp4 and a number of oracle SSO media servers backing themselves up. Solaris9/10 This has been mentioned before many times im sure and i found a thread on it called 'Yet another bpstart/bpend questions' but i dont have a copy of it to reply to. Basically as im running a UNIX backup (forget oracle for the moment) and we have multistreams set and all_local_drives directive, a bpstart_notify script we have which does this (there are extra checks etc also):- dd if=/path/to/votedsk1 of=$STAGING/votingdisk bs=4k /dev/null 21 ..is obviously running on each stream which is kicked off. I just need it to run once. There was talk about the bpstart script taking a STREAMS parameter but it doesnt say so within the /opt/openv/netbackup/bin/goodies version so can anyone confirm there are STREAMS variables passed to it? I was thinking ( perhaps like many people ) to create some lock file and then remove it. This leads to all sorts of issues regarding streams restarting, certain ones finishing before others etc and so i'd need to create some good logic around it. What are people doing in the wild? I just need the above command to run once per backup. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Another bpstart, oracle and streams question
The short answer is: don't even try if you have multiple disks. You *may* be able to get away with it now using the parent/child job functionality that got added in 6.0 but we haven't tested this, having given up on a long time ago after a multi-year battle. Sure, you can get it work most of the time, and many people do. However, there are many, many edge cases where this will break down, and if you do go down this route, you'll find some them eventually. You'll find cases where the bpstart didn't run or the bpend didn't run, or they'll run twice. We definitely had a really, really bright guy working on the bpstart/bpend scripts and he could not solve the problem so that it was 100% reliable. We simply wanted to put Oracle into hotbackup mode, do the backups, and take it out of hotbackup mode. Like you said, you'll be writing some logic around it. However, you'll be writing and writing and writing, tweaking it regularly as you run into all of the edge conditions and you'll cuss and swear as you stumble over them. Bottom line: it can't be done reliably. Use a different method of coordinating this. .../Ed On Jan 31, 2008 8:57 AM, Dave Markham [EMAIL PROTECTED] wrote: Guys im running Netbackup 6.0mp4 and a number of oracle SSO media servers backing themselves up. Solaris9/10 This has been mentioned before many times im sure and i found a thread on it called 'Yet another bpstart/bpend questions' but i dont have a copy of it to reply to. Basically as im running a UNIX backup (forget oracle for the moment) and we have multistreams set and all_local_drives directive, a bpstart_notify script we have which does this (there are extra checks etc also):- dd if=/path/to/votedsk1 of=$STAGING/votingdisk bs=4k /dev/null 21 ..is obviously running on each stream which is kicked off. I just need it to run once. There was talk about the bpstart script taking a STREAMS parameter but it doesnt say so within the /opt/openv/netbackup/bin/goodies version so can anyone confirm there are STREAMS variables passed to it? I was thinking ( perhaps like many people ) to create some lock file and then remove it. This leads to all sorts of issues regarding streams restarting, certain ones finishing before others etc and so i'd need to create some good logic around it. What are people doing in the wild? I just need the above command to run once per backup. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Another bpstart, oracle and streams question
Curious about this thread - so far as I know we're not doing anything special for backing up voting disk and OCR for Oracle RAC (unless the DBAs somehow set this up via RMAN to the policies we created in NBU). Is this something we should be doing? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, January 31, 2008 10:50 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Another bpstart, oracle and streams question The short answer is: don't even try if you have multiple disks. You *may* be able to get away with it now using the parent/child job functionality that got added in 6.0 but we haven't tested this, having given up on a long time ago after a multi-year battle. Sure, you can get it work most of the time, and many people do. However, there are many, many edge cases where this will break down, and if you do go down this route, you'll find some them eventually. You'll find cases where the bpstart didn't run or the bpend didn't run, or they'll run twice. We definitely had a really, really bright guy working on the bpstart/bpend scripts and he could not solve the problem so that it was 100% reliable. We simply wanted to put Oracle into hotbackup mode, do the backups, and take it out of hotbackup mode. Like you said, you'll be writing some logic around it. However, you'll be writing and writing and writing, tweaking it regularly as you run into all of the edge conditions and you'll cuss and swear as you stumble over them. Bottom line: it can't be done reliably. Use a different method of coordinating this. .../Ed On Jan 31, 2008 8:57 AM, Dave Markham [EMAIL PROTECTED] wrote: Guys im running Netbackup 6.0mp4 and a number of oracle SSO media servers backing themselves up. Solaris9/10 This has been mentioned before many times im sure and i found a thread on it called 'Yet another bpstart/bpend questions' but i dont have a copy of it to reply to. Basically as im running a UNIX backup (forget oracle for the moment) and we have multistreams set and all_local_drives directive, a bpstart_notify script we have which does this (there are extra checks etc also):- dd if=/path/to/votedsk1 of=$STAGING/votingdisk bs=4k /dev/null 21 ..is obviously running on each stream which is kicked off. I just need it to run once. There was talk about the bpstart script taking a STREAMS parameter but it doesnt say so within the /opt/openv/netbackup/bin/goodies version so can anyone confirm there are STREAMS variables passed to it? I was thinking ( perhaps like many people ) to create some lock file and then remove it. This leads to all sorts of issues regarding streams restarting, certain ones finishing before others etc and so i'd need to create some good logic around it. What are people doing in the wild? I just need the above command to run once per backup. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Netbackup 6.5.1 with VCB 1.1
Hi all, I am currently implementing NBU 6.5.1 with VCB 1.1. Am using Netapps FAS2020 iSCSI LUNs. However on running the backup in NBU 6.5.1 with VCB 1.1, I always get snapshot error. We always get error code 156. Error Message: FTL - snapshot creation failed, status 156 Although I can see the VM snapshot creation in VirtualCenter console, the VMDK backup process never took place and respectively the newly created VM snapshots were deleted automatically by VirtualCenter after few seconds. After inspecting some of the netbackup logs I believe I found the exact cause however I don't have a workaround for it as yet. Fragments from the bpfis.log file: 17:52:19.085 [5596.6096] 2 onlfi_vfms_logf: do_cmd: Command failed C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbMounter.exe -h esxhost:443 -u root -p *** -c C:\Program Files\VMware\VMware Consolidated Backup Framework\vmName.cache -a ipaddr:vmguest.domain.local -t fullvm -L 6 -r e:\vcb_mnt\vmguest.domain.local -M 1 -m san NUL C:\WINDOWS\TEMP\VfMS-055962010207332660962-a06096 2C:\WINDOWS\TEMP\VfMS-055962010207332660963-a06096 As it can be seen, the command initiated by NetBackup to VCB contains the parameter of using SAN transfer method which is not going to work for me because I don't have SAN infrastructure at all. I would like to use the -m nbd feature of VCB for making backups over LAN however I can't find any place where to change this parameter in NetBackup. Initiating the vcbMounter manually from CLI with the correct parameter works just great so in my opinion this is definitely a problem with the NetBackup / VCB cooperation. I didn't find any clues neither on the internet nor in the official manuals regarding such situations so I would appreciate very much the help of anyone who can give me some workarounds or additional information on how to procede next. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] cron script doing global search to backup specificfiles
I don't have an environment that I can test this on right now but you might try excluding everthing then including back in the *.pst files afterward, ie: $cat /usr/openv/netbackup/exclude_list.policyname / $cat /usr/openv/netbackup/include_list.policyname *.pst ...might work... Otherwise you could use find to create an include list every day... find /mntpoint -type f -name *.pst /tmp/include.me bpplinclude policyname -l | sed s/^INCLUDE *// /tmp/remove.me bpplinclude policyname -delete -f /tmp/remove.me bpplinclude policyname -add -f /tmp/include.me nbpemreq -updatepolicies ...the second is a bit kludgy but it should work... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of schomakw Sent: Wednesday, January 30, 2008 11:34 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] cron script doing global search to backup specificfiles I am runing NetBackup Enterprise Server, V6.0 MP5. I am looking for linux scripts which I can run in cron that would do a global search on a volume/mount point and backup specific files (in this case *.pst) regardless of where they are in the directory structure. I know I can use wildcards for filenames but have not figured out how to do this for directories. OR Is there an undocumented way to do this in the Administrator GUI using the Backup Selections window? Thanks! +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ 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] Max Fragment Size for Disk and LTO4 Based Storage Units
So I just got a SpectraLogic T950 tape library, and after some initial teething pains it's up and running and it's wicked fast, but being an impatient little monkey of a NetBackup administrator I'm wondering if I could make it wicked faster. My primary backups go to DataDomain restorers and then are duplicated to tape for offsite storage with Iron Mountain. When I set all of this up I used 2048 megabytes as the maximum fragment size in both the disk based and tape based storage units. This was based on my predecessor's experience with what was the best trade-off between backup speed and file restoration speed with LTO Gen 2 drives. But I'm wondering if I can improve backup performance even more by increasing the fragment size for my disk and LTO4 based storage units without degrading my current file restoration performance. I thought I would send this to the list to find out what people were using as the frag sizes on LTO4 and on disk based storage units such as the DataDomains. Also if I change the fragment size on my tape based storage units how does NetBackup handle tapes that have backups written to them with different fragment sizes. Can this cause problems? Any feedback will be greatly appreciated. Thank You, Jamie Jamison ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Max Fragment Size for Disk and LTO4 Based Storage Units
On Jan 31, 2008 6:21 PM, JAJA (Jamie Jamison) [EMAIL PROTECTED] wrote: So I just got a SpectraLogic T950 tape library, and after some initial teething pains it's up and running and it's wicked fast, but being an impatient little monkey of a NetBackup administrator I'm wondering if I could make it wicked faster. Faster for backups or faster for restores? There's a difference and you need to decide which is more important. Individual file restores or full volume restores? My primary backups go to DataDomain restorers and then are duplicated to tape for offsite storage with Iron Mountain. When I set all of this up I used 2048 megabytes as the maximum fragment size in both the disk based and tape based storage units. This was based on my predecessor's experience with what was the best trade-off between backup speed and file restoration speed with LTO Gen 2 drives. But I'm wondering if I can improve backup performance even more by increasing the fragment size for my disk and LTO4 based storage units without degrading my current file restoration performance. I thought I would send this to the list to find out what people were using as the frag sizes on LTO4 and on disk based storage units such as the DataDomains. Also if I change the fragment size on my tape based storage units how does NetBackup handle tapes that have backups written to them with different fragment sizes. Can this cause problems? Any feedback will be greatly appreciated. You can change the fragment size on the fly and it won't affect recovery of the existing backups. Larger fragments will be better for full-volume restores but slower for individual file restores. By how much is up to you to measure. We typically use 20GB fragments on LTO-3 destaging from DSSUs and have found that we don't have much of a significant delay in individual file restores. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 6.5.1 with VCB 1.1
Hi Daniel. A snapshot creation error (status 156) can be caused by a number of issues. These include: *** Backup Proxy has not been provided access (via iSCSI in your case) to the VMware Datastore(s). If this is the case the snapshot creation would fail pretty much as you are describing. This can be easily tested outside of NetBackup. You can use the vcbMounter.exe command for this. Manually running the vcbMounter.exe command from the Backup Proxy tests the entire snapshot creation process including copying the vmdk files to the Backup Proxy. The vcbMounter.exe command can be found in the home directory of the VCB Framework SW. This is typically: \Program Files\VMware\VMware Consolidated Backup Framework The command syntax is as follows: vcbMounter.exe -h FQDN of ESX Server -u root -p root password -a ipaddr:FQDN of virtual machine -r e:\vcb_mnt\VM hostname -t fullvm Instead of the FQDN of ESX Server you could also use the FQDN of Virtual Center Server. After the -r option, the e:\vcb_mnt directory (staging area) must exist. I've never personally tested this on iSCSI but I don't think you need the -m switch. If you can't get it to work initially make sure you don't have any typo issues (I'm a bad typist!). If this works, NetBackup should work as well. Once you get this command to work correctly, be sure and delete the folder and files that were transferred to the Backup Proxy as a result of this command. Some other issues that might prevent the snapshot creation are: *** VCB snapshot already exists. From the VI Client, check the Snapshot Manger for the target Virtual Machine and make sure the special VCB Snapshot (_VCB-BACKUP_) is not currently created. If it is, either another backup job has been initiated or it was not properly deleted after the last backup attempt. Delete this snapshot and then try the vcbMounter.exe command again. *** Not enough room on the staging area. The staging area must be at least as large as the largest VM you are going to backup. The staging area should be large enough to support multiple VM's if you are going to run parallel backups. *** The VCB Framework version is not correct. The VCB Framework SW, ESX Server version and the VC Server version all need to be the correct versions. Check the release notes for the version of ESX server you are running to make sure that all of the components mentioned are the correct version for your ESX server. *** You are using the VMware NetBackup Integration Module If you have installed this, remove it if you are using NetBackup 6.5.1. NetBackup 6.5 and above does not use the VMware NetBackup Integration Module. If it is installed, it can prevent backups from working properly. If it is installed and you uninstall it, make sure you also remove any bp_start_notify and bp_end_notify scripts that have been created as a result of this module. Daniel, I hope this helps. -George -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Goh Sent: Thursday, January 31, 2008 10:42 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Netbackup 6.5.1 with VCB 1.1 Hi all, I am currently implementing NBU 6.5.1 with VCB 1.1. Am using Netapps FAS2020 iSCSI LUNs. However on running the backup in NBU 6.5.1 with VCB 1.1, I always get snapshot error. We always get error code 156. Error Message: FTL - snapshot creation failed, status 156 Although I can see the VM snapshot creation in VirtualCenter console, the VMDK backup process never took place and respectively the newly created VM snapshots were deleted automatically by VirtualCenter after few seconds. After inspecting some of the netbackup logs I believe I found the exact cause however I don't have a workaround for it as yet. Fragments from the bpfis.log file: 17:52:19.085 [5596.6096] 2 onlfi_vfms_logf: do_cmd: Command failed C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbMounter.exe -h esxhost:443 -u root -p *** -c C:\Program Files\VMware\VMware Consolidated Backup Framework\vmName.cache -a ipaddr:vmguest.domain.local -t fullvm -L 6 -r e:\vcb_mnt\vmguest.domain.local -M 1 -m san NUL C:\WINDOWS\TEMP\VfMS-055962010207332660962-a06096 2C:\WINDOWS\TEMP\VfMS-055962010207332660963-a06096 As it can be seen, the command initiated by NetBackup to VCB contains the parameter of using SAN transfer method which is not going to work for me because I don't have SAN infrastructure at all. I would like to use the -m nbd feature of VCB for making backups over LAN however I can't find any place where to change this parameter in NetBackup. Initiating the vcbMounter manually from CLI with the correct parameter works just great so in my opinion this is definitely a problem with the NetBackup / VCB cooperation. I didn't find any clues neither on the internet nor in the official manuals regarding such situations so I would appreciate very much the help of
[Veritas-bu] NBU Catalog on NAS
Hi Guys, Anyone know if NBU catalog is store on a NAS storage instead of SAN or localdisk? We can cases where the catalog is on the NAS as we encounter status 233 and this don't happen if we using SAN. Any experience to share? +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
