Re: [Veritas-bu] Status Code 129
Guys, We had the same issue on our dd670's, as illustrated in this tech note (http://www.symantec.com/business/support/index?page=contentid=TECH1351 74) The fix for us was to apply an EEB (I forget which EEb number) and then touch a file on each of our media servers. On our two Windows 2008 R2 media servers, the file is under veritas/netbackup/bin/ost-plugins and is called REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain The file is empty. This fixed the issue for us. The readme from the eeb is below... EEB README: --- The EEB is a change in the OST core library to selectively replace logical capacity values with physical capacity values for a specific storage server type. This allows NetBackup to adapt to newer plugins which vary their logical capacity values according to newer plugin specifications which NetBackup currently does not handle. The EEB (new OST core library) needs to be placed onto each media server and the master server. The new behavior must be enabled on a per storage server type basis by creating a touch file on each media and master server. The touch file is named REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY. where represents a specific storage server type. Only when the touch file exists will the logical values be replaced by the physical values (physical values remain unmodified) for the specific storage server type. Create the touch file in the directory where the storage server plugin is installed. Unix example: /usr/openv/lib/ost- plugins/REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain Windows example: C:\Program Files\Veritas\Netbackup\bin\ost- plugins\REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain In these examples, the storage server type, , is DataDomain. To determine the of a storage server, execute the admincmd nbdevquery to list the storage servers: nbdevquery -liststs -U In the output of that command, the Storage Server Type field is the . Note: the string is case sensitive From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wayne T Smith Sent: Wednesday, September 12, 2012 2:08 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Status Code 129 I forget where it's specified, but NetBackup has a (max) size for a disk pool someplace ... maybe part of OST? I set it when I setup my Quantum disk appliance. For example, nbdevquery -listdv -stype Quantum shows me the quota in the 5th column. ymmv. Cheers, Wayne On Wed, Sep 12, 2012 at 2:40 PM, Armenti, Joseph jarme...@lordabbett.com wrote, in part: Duplication jobs are failing with a 129, insufficient space on our DR Data Domain. We have over 17tb of free space at least. What is causing this? Backups are running fine. Dup jobs to our production Data Domain are fine. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Status Code 129
We are running 7.1. There is no value in the files. It's just a file that tells NBU to report Physical capacity instead of the logical. I believe you'll need to restart the NBU services as well. From: Armenti, Joseph [mailto:jarme...@lordabbett.com] Sent: Wednesday, September 12, 2012 2:18 PM To: Mark Glazerman; w...@maine.edu; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Status Code 129 I tried placing in value in that file. That didn't help. Was that for 7.1.02? We are running 7.1.03. Would an upgrade to .04 do help? Joseph Armenti Jr. NCC Associate Production Support Engineer Lord, Abbett Co. LLC 90 Hudson Street Jersey City, NJ 07302-3973 T. 201-827-4194 F. 201-827-5194 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Wednesday, September 12, 2012 3:15 PM To: w...@maine.edu; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Status Code 129 Guys, We had the same issue on our dd670's, as illustrated in this tech note (http://www.symantec.com/business/support/index?page=contentid=TECH1351 74) The fix for us was to apply an EEB (I forget which EEb number) and then touch a file on each of our media servers. On our two Windows 2008 R2 media servers, the file is under veritas/netbackup/bin/ost-plugins and is called REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain The file is empty. This fixed the issue for us. The readme from the eeb is below... EEB README: --- The EEB is a change in the OST core library to selectively replace logical capacity values with physical capacity values for a specific storage server type. This allows NetBackup to adapt to newer plugins which vary their logical capacity values according to newer plugin specifications which NetBackup currently does not handle. The EEB (new OST core library) needs to be placed onto each media server and the master server. The new behavior must be enabled on a per storage server type basis by creating a touch file on each media and master server. The touch file is named REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY. where represents a specific storage server type. Only when the touch file exists will the logical values be replaced by the physical values (physical values remain unmodified) for the specific storage server type. Create the touch file in the directory where the storage server plugin is installed. Unix example: /usr/openv/lib/ost- plugins/REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain Windows example: C:\Program Files\Veritas\Netbackup\bin\ost- plugins\REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain In these examples, the storage server type, , is DataDomain. To determine the of a storage server, execute the admincmd nbdevquery to list the storage servers: nbdevquery -liststs -U In the output of that command, the Storage Server Type field is the . Note: the string is case sensitive From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wayne T Smith Sent: Wednesday, September 12, 2012 2:08 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Status Code 129 I forget where it's specified, but NetBackup has a (max) size for a disk pool someplace ... maybe part of OST? I set it when I setup my Quantum disk appliance. For example, nbdevquery -listdv -stype Quantum shows me the quota in the 5th column. ymmv. Cheers, Wayne On Wed, Sep 12, 2012 at 2:40 PM, Armenti, Joseph jarme...@lordabbett.com wrote, in part: Duplication jobs are failing with a 129, insufficient space on our DR Data Domain. We have over 17tb of free space at least. What is causing this? Backups are running fine. Dup jobs to our production Data Domain are fine. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Status Code 129
Understood. Sorry I couldn't help. From: Armenti, Joseph [mailto:jarme...@lordabbett.com] Sent: Wednesday, September 12, 2012 2:20 PM To: Mark Glazerman; w...@maine.edu; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Status Code 129 Symantec added a value in that file as a potential fix. But it didn't help. Joseph Armenti Jr. NCC Associate Production Support Engineer Lord, Abbett Co. LLC 90 Hudson Street Jersey City, NJ 07302-3973 T. 201-827-4194 F. 201-827-5194 From: Mark Glazerman [mailto:mark.glazer...@spartech.com] Sent: Wednesday, September 12, 2012 3:19 PM To: Armenti, Joseph; w...@maine.edu; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Status Code 129 We are running 7.1. There is no value in the files. It's just a file that tells NBU to report Physical capacity instead of the logical. I believe you'll need to restart the NBU services as well. From: Armenti, Joseph [mailto:jarme...@lordabbett.com] Sent: Wednesday, September 12, 2012 2:18 PM To: Mark Glazerman; w...@maine.edu; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Status Code 129 I tried placing in value in that file. That didn't help. Was that for 7.1.02? We are running 7.1.03. Would an upgrade to .04 do help? Joseph Armenti Jr. NCC Associate Production Support Engineer Lord, Abbett Co. LLC 90 Hudson Street Jersey City, NJ 07302-3973 T. 201-827-4194 F. 201-827-5194 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Wednesday, September 12, 2012 3:15 PM To: w...@maine.edu; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Status Code 129 Guys, We had the same issue on our dd670's, as illustrated in this tech note (http://www.symantec.com/business/support/index?page=contentid=TECH1351 74) The fix for us was to apply an EEB (I forget which EEb number) and then touch a file on each of our media servers. On our two Windows 2008 R2 media servers, the file is under veritas/netbackup/bin/ost-plugins and is called REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain The file is empty. This fixed the issue for us. The readme from the eeb is below... EEB README: --- The EEB is a change in the OST core library to selectively replace logical capacity values with physical capacity values for a specific storage server type. This allows NetBackup to adapt to newer plugins which vary their logical capacity values according to newer plugin specifications which NetBackup currently does not handle. The EEB (new OST core library) needs to be placed onto each media server and the master server. The new behavior must be enabled on a per storage server type basis by creating a touch file on each media and master server. The touch file is named REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY. where represents a specific storage server type. Only when the touch file exists will the logical values be replaced by the physical values (physical values remain unmodified) for the specific storage server type. Create the touch file in the directory where the storage server plugin is installed. Unix example: /usr/openv/lib/ost- plugins/REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain Windows example: C:\Program Files\Veritas\Netbackup\bin\ost- plugins\REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain In these examples, the storage server type, , is DataDomain. To determine the of a storage server, execute the admincmd nbdevquery to list the storage servers: nbdevquery -liststs -U In the output of that command, the Storage Server Type field is the . Note: the string is case sensitive From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wayne T Smith Sent: Wednesday, September 12, 2012 2:08 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Status Code 129 I forget where it's specified, but NetBackup has a (max) size for a disk pool someplace ... maybe part of OST? I set it when I setup my Quantum disk appliance. For example, nbdevquery -listdv -stype Quantum shows me the quota in the 5th column. ymmv. Cheers, Wayne On Wed, Sep 12, 2012 at 2:40 PM, Armenti, Joseph jarme...@lordabbett.com wrote, in part: Duplication jobs are failing with a 129, insufficient space on our DR Data Domain. We have over 17tb of free space at least. What is causing this? Backups are running fine. Dup jobs to our production Data Domain are fine. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Migrate from NBU 7.5.0.1 (Solaris Sparc) to NBU 5220Appliance (2.5)
Are all the netbackup services up and running on the appliance ? I know we ran into issues once thinking the services needed to be down. Thanks, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Vikash Gupta Sent: Thursday, July 05, 2012 2:48 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Migrate from NBU 7.5.0.1 (Solaris Sparc) to NBU 5220Appliance (2.5) Hi Team, We are having issue in restoring the Catalog backup taken from NBU 7.5.0.1 (Solaris Sparc) to NBU 5220 Appliance (2.5). The catalog restore fail after few GB of data. (we are following the standard catalog DR recovery process with same hostname and ip on Appliance) Does anyone have done the migration of complete NBU data from Solaris Sparc Master Server running 7.5.0.1 to NBU 5220 appliances? Need help in the steps on how to do this. I did check the Symantec support and there is not a single document which talks about such migration details/steps. Thanks Regards Vikash ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Fixing catalog inconsistencies
While I wait for support to get around to actually analyzing the NBCC bundle I sent them, can anyone tell me what the process is likely to be to fix the catalog inconsistencies that the NBCC tool says it found ? We have one host that we cannot run synthetic fulls against because of an apparent catalog inconsistency. Incremental backups against the same host work fine but synth fulls fail with a 671. I ran the NBCC tool and it says it found something but obviously didn't tell me what. Any input on likely next steps greatly appreciated !! Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backup Selection on Windows 2008 Master Serverfor Unix Servers.
We use the ALL_LOCAL_DRIVES as our backup selection on Solaris OS backups and then have exclude lists on each host to make sure we don’t back up any application specific files (like oracle dbf, rdo and arc files) which will get backed up using other policies. As mentioned below, selecting the “cross mount points” check box can lead to HUGE backups being taken because it will attempt to backup data residing on NFS shares etc… For example, we have our Data Domain appliances mounted as NFS shares on some of our Solaris servers. If we used the “Cross Mount Points” option each OS backup would attempt to backup 100+TB of compressed data residing on the Data Domain appliances. This is obviously not required. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: Friday, May 25, 2012 6:48 AM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Backup Selection on Windows 2008 Master Serverfor Unix Servers. Door files on Solaris, socket files on any flavor of UNIX/Linux, /proc and others are special files that can’t be backed up and don’t need to be as they are created on the fly on the system on which they exist. To prevent your backup with exiting with a status 1 (which means generally successful) you could add the files complained about to your exclude list. The autofs stuff is for NFS mounts. In addition to cross mount points you’d have to enable crossing NFS boundaries. Note that this generally is NOT necessary or desirable because the files are typically backed up on the system that exported the NFS share. On the Solaris host if you do “df /home” it should show you which system the share was exported from and you should be able to verify whether that system is being backed up separately. You do NOT want to backup /net as it is shortcut to all visible shares whether they are used on the system or not so you might end up backing up data from multiple other systems that a) is being backed up on those systems already and b) is not actually necessary for the running of the system you’re currently backing up. Here again I’d suggest adding /net at least to your exclude and /home if it is in fact being backed up from the system that exports it to this one. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Harpreet Singh Chana Sent: Friday, May 25, 2012 4:31 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Backup Selection on Windows 2008 Master Server for Unix Servers. Dear All, We have setting up a Master/Media server running on Windows 2008 (64 bit) server. Where I am trying to do a backup of Sun Solaris clients. In the Standard Backup Policy. In the Policy attributes I am using “cross mount points” and in backup selection “/” i.e. I want to backup the whole root file system But during the backup, I am not able to cover the whole root file system and it is keep skipping some of the files. 5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/sysevent_door] is a door file. Skipping 5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/devfsadm_event_channel/1] is a door file. Skipping 5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/devfsadm_event_channel/reg_door] is a door file. Skipping 5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/syseventconfd_event_channel/reg_door] is a door file. Skipping 5/26/2012 4:17:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/home] is on file system type autofs. Skipping 5/26/2012 4:18:06 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/net] is on file system type autofs. Skipping 5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/platform/sun4v/lib/libc_psr.so.1] is on file system type lofs. Skipping 5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/platform/sun4v/lib/sparcv9/libc_psr.so.1] is on file system type lofs. Skipping 5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/proc] is on file system type PROC. Skipping 5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/system/contract] is on file system type ctfs. Skipping 5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/system/object] is on file system type objfs. Skipping 5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/tmp/.X11-unix/X0] is a socket special file. Skipping . . etc Please advise how I can do a clean backup for Unix Servers
Re: [Veritas-bu] DR for Netbackup Catalog 7.1.0.4
Assuming that the catalog isn't much different in 7.1.0.4 as it is in 7.1 here is a rundown of how we handle our catalog backups during DR exercises. We backup the catalog and the associated DR file to the data domain via an NFS share on our master server. This directory on the data domain is setup to replicate via standard directory based replication to our second data domain at our DR site. We have a lights out master server with exactly the same name, IP etc.. in a rack at our DR site. At time of disaster we spin up this server, start netbackup and mount the replica data domain exactly as it's mounted in production. We copy the most recent DR file from its location on the data domain to /usr/openv/netbackup/db and then point the netbackup catalog restore wizard to this location. The actual catalog restore takes about 30 minutes. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jimenez, Daniel Sent: Monday, April 23, 2012 2:16 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] DR for Netbackup Catalog 7.1.0.4 Hey guys I would like to find out from everyone out there how you have your DR setup for the Netbackup catalog (7.1.0.4). We don't have an OST license so looking for suggestions on how to do this using DataDomain appliances. We currently replicate the catalog but looking to find out the most efficient way to do this. Any suggestions would be appreciated. Daniel Jimenez Backup and Recovery ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Issues with media server dedupe pools / replication / restores ??
I'm wondering if anyone has observed strange behavior like this with regard to media server dedupe pools and associated replication and restores. Here's our scenario... We have 2 media server dedupe pools setup. One hangs off a local media server. The other hangs off a media server at our DR site. The local pool has the credentials of the remote pool (to enable push replication). The remote pool doesn't have any extra credentials although we'd ideally like to setup a pull replication setup where the remote pool has the credentials of the local pool and initiates the pull of images). We backup to the local dedupe pool and then have an SLP which duplicates those images to the pool hanging off the remote media server. All the primary backup images are in the local pool. All the copy 2's are in the remote pool. Data in both pools has the same retention. If all of that is in place and backups and replication are working, when we're asked to restore a file who's primary copy is in the local pool, it will try and route the backup through the remote media server (which doesn't have the primary image). The restore job will just sit there until we cancel it. The only way we have found to resolve this issue is to remove the credentials of the remote media server from the local media server dedupe pool (which disables our ability to replicate data between the 2 pools), reboot all NBU machines (master server and media servers) and the restart all the NBU services. Once this has been done, restores look automatically at the local media server (where the primary image always resides) and the restore is successful. Support are being as good as useless so I'm reaching out to you fine folks to see if anyone has any advice. NBU environment is 7.1 solaris x86 master, 7.1 media servers on windows 2008 R2. Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Issues with media server dedupe pools / replication / restores ??
Stefanos, We understand that the typical behavior or NBU is to look for the primary image on the primary storage and to look to restore it to the primary client. That is what we want to occur with each of these restore attempts. We will only ever want the remote media server to handle restores at time of disaster (or testing) when we promote all copy 2's to become primary images. What does the media host override do ? If we delete the DR media server from the storage server, our replication jobs between the pools fail with a 2101 (NBU status: 2101, EMM status: Media server not found in EMM database (2101)) because our primary pool does not have the credentials required to push the duplicated images to the remote pool. How would I setup an SLP to backup to the local pool and replicate to the remote pool if the local media server cannot see / access the remote pool ? Thanks for your input, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: stefanos [mailto:sm...@peppas.gr] Sent: Thursday, February 23, 2012 9:40 AM To: Mark Glazerman; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: RE: [Veritas-bu] Issues with media server dedupe pools / replication / restores ?? Typical, The DR media server is trying to read the primary image from the primary storage server are send it back to the primary client. One way to resolve this is to use the media host override option. Another way is to delete the DR media server from the primary storage server and configure the SLPs accordingly. And upgrade to 7.1.0.3. It has many fixes to deduplication stefanos From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Thursday, February 23, 2012 5:22 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Issues with media server dedupe pools / replication / restores ?? I'm wondering if anyone has observed strange behavior like this with regard to media server dedupe pools and associated replication and restores. Here's our scenario... We have 2 media server dedupe pools setup. One hangs off a local media server. The other hangs off a media server at our DR site. The local pool has the credentials of the remote pool (to enable push replication). The remote pool doesn't have any extra credentials although we'd ideally like to setup a pull replication setup where the remote pool has the credentials of the local pool and initiates the pull of images). We backup to the local dedupe pool and then have an SLP which duplicates those images to the pool hanging off the remote media server. All the primary backup images are in the local pool. All the copy 2's are in the remote pool. Data in both pools has the same retention. If all of that is in place and backups and replication are working, when we're asked to restore a file who's primary copy is in the local pool, it will try and route the backup through the remote media server (which doesn't have the primary image). The restore job will just sit there until we cancel it. The only way we have found to resolve this issue is to remove the credentials of the remote media server from the local media server dedupe pool (which disables our ability to replicate data between the 2 pools), reboot all NBU machines (master server and media servers) and the restart all the NBU services. Once this has been done, restores look automatically at the local media server (where the primary image always resides) and the restore is successful. Support are being as good as useless so I'm reaching out to you fine folks to see if anyone has any advice. NBU environment is 7.1 solaris x86 master, 7.1 media servers on windows 2008 R2. Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Issues with media server dedupe pools /replication / restores ??
Scott, Thanks so much for your reply. So if I understand correctly, I add the following in the bp.conf on the master server FORCE_RESTORE_MEDIA_SERVER = nbumedia2 where nbumedia2 is the name of the media server I want to use for restores ? I had no idea that this was by design when using OST but it certainly makes sense. Thanks, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Kendall, Scott [mailto:scott.kend...@twcable.com] Sent: Thursday, February 23, 2012 10:41 AM To: Mark Glazerman; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: RE: [Veritas-bu] Issues with media server dedupe pools /replication / restores ?? It's by design. OST will try to use the least busy media server with credentials. Media Host Override is one way to get around the behavior and get it to do what you want. http://www.symantec.com/docs/TECH74646 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Thursday, February 23, 2012 10:50 AM To: stefanos; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Issues with media server dedupe pools / replication / restores ?? Stefanos, We understand that the typical behavior or NBU is to look for the primary image on the primary storage and to look to restore it to the primary client. That is what we want to occur with each of these restore attempts. We will only ever want the remote media server to handle restores at time of disaster (or testing) when we promote all copy 2's to become primary images. What does the media host override do ? If we delete the DR media server from the storage server, our replication jobs between the pools fail with a 2101 (NBU status: 2101, EMM status: Media server not found in EMM database (2101)) because our primary pool does not have the credentials required to push the duplicated images to the remote pool. How would I setup an SLP to backup to the local pool and replicate to the remote pool if the local media server cannot see / access the remote pool ? Thanks for your input, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: stefanos [mailto:sm...@peppas.gr] Sent: Thursday, February 23, 2012 9:40 AM To: Mark Glazerman; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: RE: [Veritas-bu] Issues with media server dedupe pools / replication / restores ?? Typical, The DR media server is trying to read the primary image from the primary storage server are send it back to the primary client. One way to resolve this is to use the media host override option. Another way is to delete the DR media server from the primary storage server and configure the SLPs accordingly. And upgrade to 7.1.0.3. It has many fixes to deduplication stefanos From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Thursday, February 23, 2012 5:22 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Issues with media server dedupe pools / replication / restores ?? I'm wondering if anyone has observed strange behavior like this with regard to media server dedupe pools and associated replication and restores. Here's our scenario... We have 2 media server dedupe pools setup. One hangs off a local media server. The other hangs off a media server at our DR site. The local pool has the credentials of the remote pool (to enable push replication). The remote pool doesn't have any extra credentials although we'd ideally like to setup a pull replication setup where the remote pool has the credentials of the local pool and initiates the pull of images). We backup to the local dedupe pool and then have an SLP which duplicates those images to the pool hanging off the remote media server. All the primary backup images are in the local pool. All the copy 2's are in the remote pool. Data in both pools has the same retention. If all of that is in place and backups and replication are working, when we're asked to restore a file who's primary copy is in the local pool, it will try and route the backup through the remote media server (which doesn't have the primary image). The restore job will just sit there until we cancel it. The only way we have found to resolve this issue is to remove the credentials of the remote media server from the local media server dedupe pool (which disables our ability to replicate data between the 2 pools), reboot all NBU machines (master server and media servers) and the restart all the NBU services. Once this has been done, restores look automatically at the local media server (where the primary image always resides) and the restore is successful. Support are being as good as useless so I'm reaching out to you fine folks to see if anyone
Re: [Veritas-bu] Issues with media server dedupe pools /replication / restores ??
Jack / Scott, We actually just added this entry and (knock on wood) it appears to be doing what we want (and what you guys have said it would !!). I should have reached out to the mailing list sooner because I've had a sev 2 ticket open with Symantec since Monday and they have yet to even make any suggestions about possible solutions. We'd tried adding MEDIA_SERVER_OVERRIDE entries in the bp.conf but it wasn't until I was reading a technote from one of the replies to my question today that I saw that NetBackup's logic, when it comes to media server allocations for restores, would ignore bp.conf entries. I'm going to leave the ticket open with support, just to see how long it takes them to get back to me, but for now I think we've got a resolution. Thanks, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: jack.fores...@mylan.com [mailto:jack.fores...@mylan.com] Sent: Thursday, February 23, 2012 2:22 PM To: Mark Glazerman Cc: Kendall, Scott; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU; veritas-bu-boun...@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Issues with media server dedupe pools /replication / restores ?? Here's some info explaining the behavior: http://www.symantec.com/connect/forums/how-media-server-load-balancing-affects-restores-openstorage We use the USE_BACKUP_MEDIA_SERVER_FOR_RESTORE option in our environment as we have multiple MSDPs at locations across the country. I don't want a media server in Vermont reading a backup image in California to restore to a client in North Carolina. I hope future versions of NetBackup handle this situation better and don't assume that I always want the least busy media server to do the restore because it may not be the best server for the restore based on physical proximity. -- Jack Forester, Jr. Sr. Data Protection Administrator Global Technology Services - AHS Mylan, Inc. 5005 Greenbag Road Morgantown, WV 26501 jack.fores...@mylan.com Phone: +1.304.554.6039 Cell: +1.412.805.5313 == 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] NBAC Solaris Master
We tried to set it up and before we knew what was going on, our entire NBU environment started slowly going south. In the end, the most helpful thing I can tell you is that if stuff starts going nuts, all that's needed to get NBU to ignore any NBAC configs is to change the USE_VXSS bpconf entry on the master server to = PROHIBITED. That basically tells NBU to ignore any VXSS stuff you may or may not have managed to get configured on any of your servers. For what it's worth, the Symantec TC who helped us with that bpconf entry told us that he tries to steer customers away from NBAC wherever possible. We met with our Symantec sales team last week and they informed us that the new ops center coming out with 7.5 has the ability to offer varying levels of access to NBU services in a much more user friendly application. We're going to give this a go when it's available as we need our helpdesk to have the ability to perform restores of remote file server data for users. We've been told we can do this without giving them access to restore everything from everywhere. Thanks, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mr Crosby Sent: Monday, February 13, 2012 8:23 AM To: Netback_mailinglist Subject: [Veritas-bu] NBAC Solaris Master I have to upgrade our live server from 6.5.5 to 7.1.0.3 next week. I also have to install access control. Should I upgrade to 7.0 then add access control or leave the install it till finished 7.1.0.3 version. Mick ___ 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] New backup
The first backup of a host using a new policy will always be a full. Netbackup will have no record of the files on that host because they have never been backed up using that policy before. An incremental backup will backup changes since the last full but without a full to base that comparison on, default behavior will be to backup everything (essentially a full backup is run the very first time) but subsequent incrementals will only backup changes since that first backup until the full runs, based on the policy schedule. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shields, Matthew Sent: Tuesday, January 24, 2012 12:41 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] New backup If you were to add a backup for the first time on a day that the policy has an Incremental specified, would it automatically promote to full Matthew T. Shields matthew.shie...@td.com This message and any attachments may contain confidential or privileged information and are intended only for the use of the intended recipients of this message. If you are not the intended recipient of this message, please notify the sender by return email, and delete this and all copies of this message and any attachments from your system. Any unauthorized disclosure, use, distribution, or reproduction of this message or any attachments is prohibited and may be unlawful. image001.jpg___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Data Domain, Replication and Two Backup Applications
I'm not so sure that using features such as boost would limit your ability to backup to a single data domain appliance from multiple backup sources. If you're just dumping to the DD as a disk target via CIFS or NFS you create a directory (or directories) under /backup and mount the DD to whatever path you want the data to be sent to. Using boost adds an additional directory structure under /backup/ost where again, you just point your disk pools to a specific directory. I would imagine that as long as you point diffrerent backup applications to different directories, you should be fine, regardless of where the data originated. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of William Brown Sent: Saturday, November 26, 2011 12:55 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Data Domain, Replication and Two Backup Applications If you use the DD as 'basic disk', NetBackup has no idea that the file system you are backing up to is a replicating appliance. Equally on the DD the NetBackup media server is just another CIFS or NFS client, and so could be one of many different backup applications. If you start using OST (DD Boost) I suspect you may be more limited, e.g. if you want to use NetWorker and NetBackup at the same time. I don't know. With NetBackup be aware of the licencing for using backup destinations that deduplicate or replicate. They were in the 'enterprise' tier. Depends possibly on how you licence NetBackup (capacity or traditional). -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of redfireball Sent: 24 November 2011 03:46 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Data Domain, Replication and Two Backup Applications Quick question to all Data Domain experts... Can you use a data domain appliance for two backup applications by carving out logical disk space and assigning it separately and replicating it to another appliance at DR site? Target site has same appliance with same capacity n same logical partitioning. Thanks in advance n Happy Thanksgiving. +-- |This was sent by redfireb...@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 This e-mail was sent by GlaxoSmithKline Services Unlimited (registered in England and Wales No. 1047315), which is a member of the GlaxoSmithKline group of companies. The registered address of GlaxoSmithKline Services Unlimited is 980 Great West Road, Brentford, Middlesex TW8 9GS. ___ 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: Data Domain Question
We have a retention period of 2 weeks on our SQL2008 environment which is dumping directly to our DD670. A quick check of our current stats show we are getting 34.02x compression on the contents of this directory. In theory compression will get better the longer you keep the data. We don't have a need for more than 2 weeks worth so that's all we keep. I can probably get some more specifics regarding the amount of data being backed up etc.. if that would help any further. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of ccosta@gmail.com Sent: Tuesday, August 16, 2011 1:03 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Fw: Data Domain Question --Original Message-- To: VERITAS-BU@mailman.eng.auburn.edu Subject: Data Domain Question Sent: Aug 16, 2011 1:59 PM To all, I am interested in finding out what deduplication ratios users are seeing when backing native SQL dumps to a Data Domain array? Having friends who work for EMC, they say 3:1 to 4:1, but I am looking for real numbers that users are seeing not the sales numbers. Please let me know Sent via BlackBerry from T-Mobile ___ 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] DR report email after successful catalog backup is not being generated [ Netbackup 6.5.6 on Solaris 10 ]
Starting from the basics, have you checked that in the catalog policy (under Disaster Recovery), you have the correct email address(es) specified and that you have checked the box stating you want send the DR file in an email attachment to those email addresses ? Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Bhangui, Sandeep - BLS CTR Sent: Friday, May 06, 2011 6:48 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] DR report email after successful catalog backup is not being generated [ Netbackup 6.5.6 on Solaris 10 ] Hi Solaris 10 Master/Media server.running Netbackup Ver 6.5.6.it seems everything functionality wise is working fine but the DR report which is send via email once you do a catalog backup is not being send via email to the address defined in the catalog backup policy. The catalog backup is being done successfully. Mail is working fine on the box as I do receive emails once a backup is completed or if it fails...with the status codes Can someone please let me know what can I check to troubleshoot this issue Thanks in advance. Sandeep ___ 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] Oracle 11G backup with netbackup 6.5.6
You cannot run the oracle_link script when the database is running. That is why your output is still referencing your old 6.5 install. You'll need to bounce the DB in order to link it to your new 6.5.6 client. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Michael Graff Andersen Sent: Tuesday, April 26, 2011 9:30 AM To: pranav batra Cc: Stef Veritas; Veritas Subject: Re: [Veritas-bu] Oracle 11G backup with netbackup 6.5.6 Yes, the libobk file under netbackup it might have been locked by some oracle process, know that we sometimes have to delete it, then upgrade and recreate the symbolic link Other than that I would create the dbclient directory under logs with 777 permissions Hope this helps Regards Michael 2011/4/26 pranav batra pranav_vent...@hotmail.com My main concern here is why it is showing that linking to 6.5 oracle even after upgrading to 6.5.6 channel d1: Veritas NetBackup for Oracle - Release 6.5 (2010042405) We did upgrade agent without stopping the database. Does this has something to do with this ??? Pranav From: sm...@peppas.gr To: pranav_vent...@hotmail.com; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Oracle 11G backup with netbackup 6.5.6 Date: Tue, 26 Apr 2011 09:48:26 +0300 Hi, Open the bphdb and dbbackup logs and rerun the backup. Check the logs. Is your oracle cluster aware? What is the OS? Also post the rman script. If the oracle is installed as cluster aware be sour that you have configure the backup to the service name and you have add the correct send parameters at the rman script. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of pranav batra Sent: Tuesday, April 26, 2011 9:15 AM To: Veritas Subject: [Veritas-bu] Oracle 11G backup with netbackup 6.5.6 Hello Geeks, We recently tried to test oracle 11G backup with netbackup . Earlier we did not know that oracle 6.5 is not supported with 11G. So we linked oracle with netbackup lib files. But as we got to know that 6.5. is not supported we upgraded to 6.5.6 But we still getting error. channel d1: Veritas NetBackup for Oracle - Release 6.5 (2010042405) Starting backup at 25-APR-11 channel d1: starting full datafile backup set channel d1: specifying datafile(s) in backup set including current control file in backup set channel d1: starting piece 1 at 25-APR-11 released channel: d1 RMAN-00571: === RMAN-00569: === ERROR MESSAGE STACK FOLLOWS === RMAN-00571: === RMAN-03009: failure of backup command on d1 channel at 04/25/2011 12:20:49 ORA-19506: failed to create sequential file, name=i9maljov_1_1, parms= ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSAValidateFeatureId: Failed with error: Server Status: unexpected message received Though we have upgraded netbackup client oracle agent to 6.5.6 # DO NOT EDIT THIS FILE ! # * means installed patch was preceded by this patch. # + means that the installed patch installed this patch as a dependency. NB_CLT_6.5.6 installed. +NB_JAV_6.5.6 NB_JAV_6.5.6 installed. *NB_CLT_6.5.6 NB_ORA_6.5.6 installed. *NB_CLT_6.5.6 What is the issue. Please advise. Thanks, Pranav ___ 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] DD LSU question
We misread the guides when setting up our new dd670's about 6 months ago and currently have 9 active LSU's. Prior to using OST on our old DD's we had multiple directories under /backup so we could easily keep tabs on the compression and replication performance of the different apps or systems we were backing up. We setup the LSU's on our new dd670's using OST with the same theory in mind and have not seen any issues with compression or performance so probably won't be changing it. As a side note, with our pre-ost setup we were also successfully using CIFS and NFS simultaneously without realizing that, technically, it wasn't supported either. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of X_S Sent: Wednesday, April 20, 2011 12:18 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] DD LSU question Can someone tell me if the number of LSUs configured on a system effects dedupe ratio and overall performance of the DD box? i see that in best practices it is recommended that one LSU is created per Netbackup environment. i do have more than LSU configured in one NB environment but i wonder if i did utilize only one LSU, if the global and local compression sizes would be better. thanks for your input. +-- |This was sent by xsp...@yahoo.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
Re: [Veritas-bu] DD LSU question
According to the OST / Boost admin guide (http://www.emc.com/collateral/software/white-papers/h7296-data-domain-boost-openstorage-wp.pdf) having multiple LSU's may impact some advanced Netbackup features like media server load balancing and capacity reporting. We are seeing equally impressive compression numbers across our multiple LSU's as we were in our multiple directories under /backup before deploying OST. I wouldn't be overly concerned unless your SE or support give you reason to be. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of X_S Sent: Wednesday, April 20, 2011 1:15 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] DD LSU question thanks, we created multiple lsu's for the same exact reason to keep an eye on ratios of different os's and db's thinking that dedupe and compression would be done across all the data ingested so the existence of multiple lsu's wouldn't matter. i'm hoping this is the case +-- |This was sent by xsp...@yahoo.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
Re: [Veritas-bu] EMC Data Domain OST Vs VTL with NetBackup
The OST plugin will help you with the offsite copy to your duplicate DD appliance because the use of optimized duplication, available when using OST and NBU, reduces the bandwidth used to duplicate images, speeding up the duplication process. Using an SLP (Storage Lifecycle Process) to manage your duplications should allow you to specify a backup destination (in your case your local DD appliance) followed by two duplication targets (one being your 2nd dd appliance and one being a local tape drive). We've never used the VTL option so I'm not sure if you need to have this configured in order to be able to duplicate to tape from a DD appliance. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of sandesh Sent: Thursday, April 14, 2011 9:38 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] EMC Data Domain OST Vs VTL with NetBackup We are in the early stages of implementing EMC Data Domain dedupe appliance and use Symantec NetBackup. I've a couple of questions about it for the experts. Plan is to have a DD appliance in 1 location and replicate data to another DD appliance in another location. Plan is also to generate a tape copy for long term archival at primary location. 1.OST VTL are both being discussed. Which option is most favorable in the industry? Are there any specific advantages that can make or break things? 2.VTL supports LTO3 drives at the most. Does this mean that we need to have LTO3 physical tape drives for duplicate copy or will LTO5 drives work? Thanks in advance. +-- |This was sent by sandesh@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
Re: [Veritas-bu] EMC Data Domain OST Vs VTL with NetBackup
Apologies, SLP is a storage lifecycle policy, not process. I was typing faster than I was thinking ! Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Thursday, April 14, 2011 10:29 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] EMC Data Domain OST Vs VTL with NetBackup The OST plugin will help you with the offsite copy to your duplicate DD appliance because the use of optimized duplication, available when using OST and NBU, reduces the bandwidth used to duplicate images, speeding up the duplication process. Using an SLP (Storage Lifecycle Process) to manage your duplications should allow you to specify a backup destination (in your case your local DD appliance) followed by two duplication targets (one being your 2nd dd appliance and one being a local tape drive). We've never used the VTL option so I'm not sure if you need to have this configured in order to be able to duplicate to tape from a DD appliance. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of sandesh Sent: Thursday, April 14, 2011 9:38 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] EMC Data Domain OST Vs VTL with NetBackup We are in the early stages of implementing EMC Data Domain dedupe appliance and use Symantec NetBackup. I've a couple of questions about it for the experts. Plan is to have a DD appliance in 1 location and replicate data to another DD appliance in another location. Plan is also to generate a tape copy for long term archival at primary location. 1.OST VTL are both being discussed. Which option is most favorable in the industry? Are there any specific advantages that can make or break things? 2.VTL supports LTO3 drives at the most. Does this mean that we need to have LTO3 physical tape drives for duplicate copy or will LTO5 drives work? Thanks in advance. +-- |This was sent by sandesh@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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] EMC Data Domain OST Vs VTL with NetBackup
I just checked with my DD SE and you do not need to have your DD appliance setup as a VTL to be able to duplicate to tape using an SLP. My original post was correct, backup destination will be DD#1, duplicate destinations inside the same SLP will be DD#2 and your tape drive(s). Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of sandesh Sent: Thursday, April 14, 2011 9:38 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] EMC Data Domain OST Vs VTL with NetBackup We are in the early stages of implementing EMC Data Domain dedupe appliance and use Symantec NetBackup. I've a couple of questions about it for the experts. Plan is to have a DD appliance in 1 location and replicate data to another DD appliance in another location. Plan is also to generate a tape copy for long term archival at primary location. 1.OST VTL are both being discussed. Which option is most favorable in the industry? Are there any specific advantages that can make or break things? 2.VTL supports LTO3 drives at the most. Does this mean that we need to have LTO3 physical tape drives for duplicate copy or will LTO5 drives work? Thanks in advance. +-- |This was sent by sandesh@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
[Veritas-bu] RMAN Backup Error
Netbackup Guru's, We have a hot database backup policy configured to backup an oracle database on two separate unix hosts. Both hosts backup using the same schedules and the exact same RMAN backup script. One host completes successfully, the other started giving us the following error after a recent clone. RMAN-03009: failure of backup command on ch02 channel at 03/24/2011 07:20:54 ORA-27192: skgfcls: sbtclose2 returned error - failed to close file ORA-19511: Error received from media manager layer, error text: Failed to process backup file bk_1305_1_746591618 ORA-19502: write error on file bk_1305_1_746591618, block number 9901857 (bloc k size=8192) ORA-27030: skgfwrt: sbtwrite2 returned error ORA-19511: Error received from media manager layer, error text: VxBSASendData: Failed with error: The block mentioned here is one of 2 that it seems to be having issues with (the other is 9901825) but I'm at a loss as to where I should be looking to tie in the block number and RMAN backup piece information in order to find out what file the bad block is located in. The result from a netbackup perspective is that the hot backup never completes on the failing host. It just sits there until it eventually times out or we kill it. As far as we can tell, there are no differences in the RMAN or netbackup configurations which points to a data error of some kind. I'd really appreciate any guidance on the best way to troubleshoot this. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs
Stefanos, I did find a pd.conf file on the media server under\netbackup\bin\ost-plugins which has a Optimized-duplication max bandwidth (KB/Sec) # OPTDUP_BANDWIDTH = 0 setting which can be tweaked to limit the bandwidth used for all optimized duplication jobs originating via that media server. This would appear to do what we need except that it throttles ALL duplication jobs from that media server and after thinking about it, we need to throttle the bandwidth used by duplication jobs originating from a specific policy. In the old Puredisk environment we use to backup our remote sites, there is a bandwidth setting that is based on each individual policy (we have 1 policy per remote site) to avoid the line between the remote sites and our data center being clogged with backup traffic. This feature didn't get integrated into NBU 7 although it's a puredisk engine that manages NBU 7's dedupe and optimized duplication abilities. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: stefanos [mailto:sm...@peppas.gr] Sent: Tuesday, March 08, 2011 7:33 AM To: Mark Glazerman; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs No, you can not set any limit to the traffic between two media servers. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Monday, March 07, 2011 7:23 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs Does anyone know if there is a way to limit the amount of bandwidth used in the duplication portion of a Storage Lifecycle Policy between two Advanced Disk disk pools ? On our data domain appliances we have the ability to set throttle schedules which limit the amount of bandwidth available when duplicating between the two appliances as part of a SLP. Is there an equivalent setting for Advanced Disk disk pools which stop duplication jobs from saturating our line during duplication activity ? Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs
Yes, my question was about Advanced Disk and not puredisk disk pools. My puredisk references were because a lot of the new features in NBU 7.0 (Deduplication, optimized duplication etc..) have been taken from their puredisk product and rolled into Netbackup. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: stefanos [mailto:sm...@peppas.gr] Sent: Tuesday, March 08, 2011 9:09 AM To: Mark Glazerman; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs That's good, Your question was about Advanced Disk disk pools and not about puredisk pools. MSDP is a light edition of puredisk and many futures and parameters are missing. It is a shame that Symantec keep all the knowledge and does not have a document to give us a clue of what we can do with all pd.conf parameters (and there are more hidden on other conf files) Stefanos From: Mark Glazerman [mailto:mark.glazer...@spartech.com] Sent: Tuesday, March 08, 2011 4:24 PM To: stefanos; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs Stefanos, I did find a pd.conf file on the media server under\netbackup\bin\ost-plugins which has a Optimized-duplication max bandwidth (KB/Sec) # OPTDUP_BANDWIDTH = 0 setting which can be tweaked to limit the bandwidth used for all optimized duplication jobs originating via that media server. This would appear to do what we need except that it throttles ALL duplication jobs from that media server and after thinking about it, we need to throttle the bandwidth used by duplication jobs originating from a specific policy. In the old Puredisk environment we use to backup our remote sites, there is a bandwidth setting that is based on each individual policy (we have 1 policy per remote site) to avoid the line between the remote sites and our data center being clogged with backup traffic. This feature didn't get integrated into NBU 7 although it's a puredisk engine that manages NBU 7's dedupe and optimized duplication abilities. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: stefanos [mailto:sm...@peppas.gr] Sent: Tuesday, March 08, 2011 7:33 AM To: Mark Glazerman; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs No, you can not set any limit to the traffic between two media servers. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Monday, March 07, 2011 7:23 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs Does anyone know if there is a way to limit the amount of bandwidth used in the duplication portion of a Storage Lifecycle Policy between two Advanced Disk disk pools ? On our data domain appliances we have the ability to set throttle schedules which limit the amount of bandwidth available when duplicating between the two appliances as part of a SLP. Is there an equivalent setting for Advanced Disk disk pools which stop duplication jobs from saturating our line during duplication activity ? Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Limit Bandwidth Utilization During SLP Duplication jobs
Does anyone know if there is a way to limit the amount of bandwidth used in the duplication portion of a Storage Lifecycle Policy between two Advanced Disk disk pools ? On our data domain appliances we have the ability to set throttle schedules which limit the amount of bandwidth available when duplicating between the two appliances as part of a SLP. Is there an equivalent setting for Advanced Disk disk pools which stop duplication jobs from saturating our line during duplication activity ? Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] using *.dbf in exclude lists
This is indeed a valid issue and one that we were unaware was affecting us until this morning. The bpbkar logs on our clients are showing many many files being incorrectly excluded from our OS backups because of the use of wild cards in our exclude lists. Luckily, we have not run into any issues during DR or restore testing but this is probably down to the fact that we use FLAR's and don't have many, if any, requests for individual file restores. Having said that, there is definitely worry now that if a file level restore was requested, we could easily be missing data. We are looking into amending our exclude lists while we try and find out if this has been fully addressed in 7.0.1 or any pending releases. Thankyou for the heads up !! Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Wednesday, February 23, 2011 7:14 PM To: giris...@yahoo.com; gstaff...@barclaycardus.com; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] using *.dbf in exclude lists Thanks for the heads up. I'll look into this tomorrow. Sent from my HTC on the Now Network from Sprint! - Reply message - From: Girish Jorapurkar giris...@yahoo.com Date: Wed, Feb 23, 2011 18:24 Subject: [Veritas-bu] using *.dbf in exclude lists To: Mark Glazerman mark.glazer...@spartech.com, Stafford, Geoff gstaff...@barclaycardus.com, veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Beware of the following bug in NB 7.0: http://www.symantec.com/business/support/index?page=contentid=TECH135929 From: Mark Glazerman mark.glazer...@spartech.com To: Stafford, Geoff gstaff...@barclaycardus.com; veritas-bu@mailman.eng.auburn.edu Sent: Wed, February 23, 2011 4:30:57 PM Subject: Re: [Veritas-bu] using *.dbf in exclude lists We exclude .dbf, .DBF, .arc and .redo files from our OS backups because RMAN handles all of those during the database backups. No point in backing them up when they won’t be part of any OS restore. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 Pplease don't print this e-mail unless you really need to From:veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Stafford, Geoff Sent: Wednesday, February 23, 2011 3:59 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] using *.dbf in exclude lists I’m hoping I can get a few peoples opinions on using *.dbf (or *.whatever) in exclude lists to avoid backing up Oracle (or whatever) database files. I’ve always been of the opinion that excluding the directory where the database files are is a better method as it doesn’t require NBU to evaluate each and every file that it attempts to backup so you have less of a load on the client and, in theory, there might be an every so slight increase in backup speeds. Our database environment, especially on the development/QA side, is very active/transient and new databases are popping up all the time on existing hosts resulting in backing up tons of tons of hot database files which are absolutely worthless. Putting procedures around creating new databases requiring them to notify us when they create a new database is The Right Way to Do It™ but that’s easier said than done in a dev/qa world. I’m starting to think that the time required to maintain the exclude lists is becoming more expensive than any performance benefits. So, all ye great NBU minds, what are your experiences with using *.dbf and have you noticed any ill effects on the client? ___ Barclays www.barclaycardus.com ___ This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ 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] using *.dbf in exclude lists
We exclude .dbf, .DBF, .arc and .redo files from our OS backups because RMAN handles all of those during the database backups. No point in backing them up when they won't be part of any OS restore. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Stafford, Geoff Sent: Wednesday, February 23, 2011 3:59 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] using *.dbf in exclude lists I'm hoping I can get a few peoples opinions on using *.dbf (or *.whatever) in exclude lists to avoid backing up Oracle (or whatever) database files. I've always been of the opinion that excluding the directory where the database files are is a better method as it doesn't require NBU to evaluate each and every file that it attempts to backup so you have less of a load on the client and, in theory, there might be an every so slight increase in backup speeds. Our database environment, especially on the development/QA side, is very active/transient and new databases are popping up all the time on existing hosts resulting in backing up tons of tons of hot database files which are absolutely worthless. Putting procedures around creating new databases requiring them to notify us when they create a new database is The Right Way to Do It(tm) but that's easier said than done in a dev/qa world. I'm starting to think that the time required to maintain the exclude lists is becoming more expensive than any performance benefits. So, all ye great NBU minds, what are your experiences with using *.dbf and have you noticed any ill effects on the client? ___ Barclays www.barclaycardus.com ___ This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] using *.dbf in exclude lists
Thanks for the heads up. I'll look into this tomorrow. Sent from my HTC on the Now Network from Sprint! - Reply message - From: Girish Jorapurkar giris...@yahoo.com Date: Wed, Feb 23, 2011 18:24 Subject: [Veritas-bu] using *.dbf in exclude lists To: Mark Glazerman mark.glazer...@spartech.com, Stafford, Geoff gstaff...@barclaycardus.com, veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Beware of the following bug in NB 7.0: http://www.symantec.com/business/support/index?page=contentid=TECH135929 From: Mark Glazerman mark.glazer...@spartech.com To: Stafford, Geoff gstaff...@barclaycardus.com; veritas-bu@mailman.eng.auburn.edu Sent: Wed, February 23, 2011 4:30:57 PM Subject: Re: [Veritas-bu] using *.dbf in exclude lists We exclude .dbf, .DBF, .arc and .redo files from our OS backups because RMAN handles all of those during the database backups. No point in backing them up when they won’t be part of any OS restore. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 Pplease don't print this e-mail unless you really need to From:veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Stafford, Geoff Sent: Wednesday, February 23, 2011 3:59 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] using *.dbf in exclude lists I’m hoping I can get a few peoples opinions on using *.dbf (or *.whatever) in exclude lists to avoid backing up Oracle (or whatever) database files. I’ve always been of the opinion that excluding the directory where the database files are is a better method as it doesn’t require NBU to evaluate each and every file that it attempts to backup so you have less of a load on the client and, in theory, there might be an every so slight increase in backup speeds. Our database environment, especially on the development/QA side, is very active/transient and new databases are popping up all the time on existing hosts resulting in backing up tons of tons of hot database files which are absolutely worthless. Putting procedures around creating new databases requiring them to notify us when they create a new database is The Right Way to Do It™ but that’s easier said than done in a dev/qa world. I’m starting to think that the time required to maintain the exclude lists is becoming more expensive than any performance benefits. So, all ye great NBU minds, what are your experiences with using *.dbf and have you noticed any ill effects on the client? ___ Barclays www.barclaycardus.com ___ This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] PureDisk vs. DataDomain
We use both here and have been for over 4 years. We use Data Domain for all of our data center backups and Puredisk (the original appliance based version) for all of our remote file server backups. We did look into Netbackup 7's built in dedupe which uses the puredisk dedupe engine to allow both client side and media server dedupe of backups to any disk storage backends but just couldn't get the compression we get out of the data domain appliances. As an example, our data domains currently house approximately 35 copies of our exchange backups (700GB during a full backup) in 3.8TB of raw. We presented the same amount of storage from a dell equallogic storage array to a netbackup dedupe pool and we couldn't fit 4 copies of that same exchange data. We've done countless reference calls for Data Domain detailing our consideration of Netbackups built in dedupe and our findings. The biggest problem is the Netbackup Puredisk dedupe uses a fixed block algorithm where as the Data Domain's use a variable block algorithm. This allows the Data Domain appliances to generate much greater compression. The backup performance was comparable across both solutions but just like we've seen with our appliance based puredisk environment, restores from the Data Domain's were MUCH faster than from the puredisk storage. Netbackup 7 has improved the restore speeds but it's still not comparable to the 100GB /hour restore speeds we get (simultaneously across multiple platforms / applications) at our Disaster recovery exercises. In our production puredisk environment, if we need to restore a 100GB file server to ship out to a plant it can take up to 10-12 hours to restore. If you have a HUGE pool of money to spend on back end disk then Netbackup 7's built in dedupe may still be an option for you. However, we'd have needed to purchase more than 10X the raw disk capacity of our data domain appliances in order to be able to house the same amount of deduped data that our Data Domain's currently store. As existing Data Domain customers, this was not financially viable and even the lure of a one stop shop for all backup storage was not big enough for us to jump ship after 4+ years as Data Domain users. We started off with two dd430's and later added two dd560's. Now have two DD670's setup in a replication pair and use Storage Lifecycle Policies (SLP's) inside Netbackup coupled with the optional Open Storage (OST) plugin to manage all but a handful of backup policies. The OST plugin lets us make use of the Optimized duplication technology to reduce bandwidth utilization between our main data center and our DR site and the tighter integration with Netbackup gives us additional visibility of both our primary and now also our duplicated images from inside the catalog. Yes... I'm a Data Domain fan but that's not because I'm getting paid to say this stuff. It's because it works flawlessly, has got us out of some real binds and makes my boss look like a rockstar at our twice yearly DR tests. If we'd seen similar numbers from Netbackup then I'd be singing a different tune but for now, Data Domain has my vote. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Fred M Sent: Wednesday, February 09, 2011 10:14 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] PureDisk vs. DataDomain Hi all, My employer is requesting I evaluate PureDisk and DataDomain for de-duplication. While I can setup a demo of each and get the numbers, and ask the sales guys what makes them great and why their competitors aren't, I can't trust that is nothing more than sales drivel. So, I ask you expert users. Can anyone tell me what their experiences are with DataDomain and PureDisk and why you went with that solution from a technical perspective? You know, the typical pro/con deal. Thanks for the help! ~~Fred~~ ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to use the DataDomain system cleaning process
The cleaning process is very easy to administer. You set up each restorer to clean expired data based on a schedule. It can clean as often as you want but in our environment we have it set to clean once a week at 6am on a Tuesday. As long as you are using directory based replication you set up a cleaning schedule on both data domain systems (source and replica). The cleaning process is quite intensive and can take some time if you have a lot of data. The Data Domain systems mark data as cleanable based on the retention parameters passed to it by Netbackup. Once an image expires in Netbackup, it can be marked as cleanable by the data domain. Filesys show space will show the amount marked as cleanable since the last cleaning cycle ran. The command syntax is filesys clean set schedule [daily | monthly | never] day(s) time. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of nguytom Sent: Thursday, February 03, 2011 3:14 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] How to use the DataDomain system cleaning process Hi Tim Ratheeshdas Here my email ngu...@yahoo.com or nguy...@gmail.com , could you send me DD admin guide and Netbackup-DD best practice guide thank you very much for your help, I appreciate that. Tom +-- |This was sent by ngu...@yahoo.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
Re: [Veritas-bu] Catalog Backups not running
Nate, Sorry that my idea seems to have compounded your problem. Might I suggest my original approach but setting it up on a test schedule so you can see quickly if scheduled catalogs will run rather than having to wait or have NBU predict when it thinks it should be running. If you get better results with that, you could setup another new catalog policy with your correct schedules. I also noted from your earlier response that you deleted and recreated the new catalog policy after you'd restarted the NBU services. Support were very specific with me that the current catalog backup policy should be deleted before the services are restarted and the new policy shouldn't be created until after the services are back up. Hope you make some progress because we all know how painful engaging support is on these issues, especially this late in the day !! Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: Tuesday, January 18, 2011 1:03 PM To: Nate Sanders; stefanos Cc: Sanders, Nate; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Catalog Backups not running While trying to recreate your issue yesterday in a test environment I did the same thing. Nbpemreq eventually did show the scheduled catalog backups, but it took a while and did not show the after last backup session incrementals. -Jonathan -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Tuesday, January 18, 2011 1:54 PM To: stefanos Cc: Sanders, Nate; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Catalog Backups not running So I restarted netbackup, verified nbpem was not running, which it wasn't. I deleted and created a new catalog policy with a different name and now bppemreq -predict |grep -i catalog doesn't even show the Full catalog thats supposed to run once a week. Nor are my end of session incrementals running.. I guess it's time to open a support ticket. On 01/18/2011 02:44 AM, stefanos wrote: I have the same problem with my customers from time to time. Stop NBU services. Check if all services are down. Most probable nbpem will still up. Kill it, if you don't you will have the same problem. Start nbu Recheck your schedules -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Monday, January 17, 2011 11:24 PM Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Catalog Backups not running Policy settings: Type: NBU-Catalog Destination: Policy storage: Any_available Policy volume pool: CatalogBackup (there are two tapes in this pool) Schedule (name: Differential-Inc) Type: Differential Incremental Backup Schedule Type: (*) After each backup session Retention: 2 weeks It used to be I'd see about 100 diff-inc backup jobs a day. On 01/17/2011 03:19 PM, Nate Sanders wrote: I ran -updatepolicies and then checked upcoming schedules root@backup1:~$ nbpemreq -predict -date 01/17/2011 20:00:00 Predicted work assuming no job run between now and Mon 17 Jan 2011 08:00:00 PM CST rl client policy schedule type -- -- 03 stage-imagedb01 RMAN_stage_simg01Archive_Logs 1 03 netapp02 NDMP_autoload_subaru_ca Diff_Incr 1 03 stage-cleandb01 RMAN_stage_scln01Archive_Logs 1 03 watson RMAN_prod_dbaweb Archive_Logs 1 03 bzsearch02 RMAN_prod_pbz02 Archive_Logs 1 04 netapp01 NDMP_netapp1vmvol1 Full_Monthly 0 03 gmcert01 RMAN_prod_pgmc01 Archive_Logs 1 03 vplayer01RMAN_prod_pvid01 Archive_Logs 1 03 gmcert02 RMAN_prod_pgmc02 Archive_Logs 1 03 vplayer02RMAN_prod_pvid02 Archive_Logs 1 03 stage-bzsearch01 RMAN_stage_sbz01 Archive_Logs 1 03 stage-imagedb02 RMAN_stage_simg02Archive_Logs 1 03 stage-vplayer01 RMAN_stage_svid01Archive_Logs 1 03 bzsearch01 RMAN_prod_pbz01 Archive_Logs 1 Setting it out past 7 days does show the Full is scheduled to run (which is once a week), but should the Incrementals which are scheduled for after each session show up? On 01/17/2011 03:07 PM, Martin, Jonathan wrote: Have you tried nbpemreq -updatepolicies? What happens if you run nbpemreq -predict -date mm/dd/ HH:MM:SS using
Re: [Veritas-bu] Catalog Backups not running
Nate, I had the exact same problem and support identified a knowledge base article that points to nbpem getting into a looped state which causes policies to be marked as corrupt. In your problems report do you see anything like this... 5/16/20089:00:07 PM unknown nbumaster01.sun.spartech.com Error 1571 Backup backup of client nbumaster01.sun.spartech.com exited with status 2 (none of the requested files were backed up) 5/16/20089:33:43 PM unknown nbumaster01.sun.spartech.com Error 1617 Backup backup of client nbumaster01.sun.spartech.com exited with status 150 (termination requested by administrator) 5/16/20089:33:43 PM unknown nbumaster01.sun.spartech.com Error 1617 Backup [1] suspending further backup attempts for client nbumaster01.sun.spartech.com, policy NBU-Catalog-Hot, schedule Cumulative_Day: exceeded configured number of tries 5/17/20088:27:38 AM unknown nbumaster01.sun.spartech.com Error 2060 Backup backup of client nbumaster01.sun.spartech.com exited with status 227 (no entity was found) 5/17/20088:29:30 AM unknown nbumaster01.sun.spartech.com Error 2063 Backup backup of client nbumaster01.sun.spartech.com exited with status 227 (no entity was found) 5/17/20088:29:30 AM unknown nbumaster01.sun.spartech.com Error 2063 Backup [1] suspending further backup attempts for client nbumaster01.sun.spartech.com, policy NBU_CATALOG_HOT1, schedule Cumulative-Night: exceeded configured number of tries Supports workaround for me was to completely delete the current failing catalog policy, restart the NBU services and recreate a new policy with a different name. This fixed the issue in 6.5.1 and we then moved to 6.5.4 and didn't see the problem again. We're now at 7.0 and haven't seen anything similar in this release. The errors that I saw during a failing catalog backup can be seen below where the db verify failed caused the whole catalog backup to fail. 5/16/2008 9:00:48 PM - Info bpdbm(pid=29892) staging relational database files for catalog backup 5/16/2008 9:00:48 PM - Info bpdbm(pid=29892) staging NBDB backup to /usr/openv/db/staging 5/16/2008 9:00:52 PM - Info bpdbm(pid=29892) done staging NBDB backup to /usr/openv/db/staging 5/16/2008 9:00:52 PM - Info bpdbm(pid=29892) validating NBDB backup in /usr/openv/db/staging 5/16/2008 9:00:53 PM - Error bpdbm(pid=29892) error validating NBDB backup in /usr/openv/db/staging none of the requested files were backed up(2) Hope this helps, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: Monday, January 17, 2011 3:24 PM Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Catalog Backups not running Policy settings: Type: NBU-Catalog Destination: Policy storage: Any_available Policy volume pool: CatalogBackup (there are two tapes in this pool) Schedule (name: Differential-Inc) Type: Differential Incremental Backup Schedule Type: (*) After each backup session Retention: 2 weeks It used to be I'd see about 100 diff-inc backup jobs a day. On 01/17/2011 03:19 PM, Nate Sanders wrote: I ran -updatepolicies and then checked upcoming schedules root@backup1:~$ nbpemreq -predict -date 01/17/2011 20:00:00 Predicted work assuming no job run between now and Mon 17 Jan 2011 08:00:00 PM CST rl client policy schedule type -- -- 03 stage-imagedb01 RMAN_stage_simg01Archive_Logs 1 03 netapp02 NDMP_autoload_subaru_ca Diff_Incr 1 03 stage-cleandb01 RMAN_stage_scln01Archive_Logs 1 03 watson RMAN_prod_dbaweb Archive_Logs 1 03 bzsearch02 RMAN_prod_pbz02 Archive_Logs 1 04 netapp01 NDMP_netapp1vmvol1 Full_Monthly 0 03 gmcert01 RMAN_prod_pgmc01 Archive_Logs 1 03 vplayer01RMAN_prod_pvid01 Archive_Logs 1 03 gmcert02 RMAN_prod_pgmc02 Archive_Logs 1 03 vplayer02RMAN_prod_pvid02 Archive_Logs 1 03 stage-bzsearch01 RMAN_stage_sbz01 Archive_Logs 1 03 stage-imagedb02 RMAN_stage_simg02Archive_Logs 1 03 stage-vplayer01 RMAN_stage_svid01
Re: [Veritas-bu] SLP ??
Pranav, SLP's enable you to duplicate backup images to multiple different locations all the while ensuring that Netbackup retains full visibility of the duplicated images wherever they end up residing. In our environment, where we'd traditionally used Data Domain's built in replication technology, Netbackup was aware of the backup image but was not aware of the duplicate copy on our replica data domain appliance. We still use Data Domain but now, using SLP's, Netbackup is aware of both copies and all the duplication jobs are visible inside the activity monitor. You can also use the same SLP for multiple policies. You just point your policy to it like you'd point it to storage unit and the SLP does the rest. I'm sure there are lots of other benefits but this is at least a start. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of pranav batra Sent: Friday, January 07, 2011 3:11 PM To: Veritas Subject: [Veritas-bu] SLP ?? Hello Geeks, I am looking for some of the advantages of SLP. All I think is that we can duplicate data and with diffrent retention periods? Wat else? Thanks, Pranav batra ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] netbackup for Oracle configuration
Michael is right, The oracle agent comes as part of the netbackup 7 client now. One word of warning though, running the oracle link (on unix located in /usr/openv/netbackup/bin) requires any databases to be down or the link won't work. I'm not sure if there is a sample rman script in the same location as the oracle link but the script can be a bit of a bit*h to manipulate to fit with your own environment. In addition to the rman script, you also need an rman_oratab entry under /var/opt/oracle/ which tells the script the name of the database you're looking to back up. I can provide a copy of our rman script if you'd like to see what we're doing. Thanks, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Michael Graff Andersen Sent: Friday, December 17, 2010 4:57 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] netbackup for Oracle configuration Just installing the Netbackup Client on the Oracle server should be enough, the oracle agent should be a part of the client in 7.0 Regards Michael 2010/12/17 ibby netbackup-fo...@backupcentral.com Thanks Michael, I am sure these are correct steps , only confusion I am having is should I install the netbackup server on the Oracle server or NB client or both , pls clarify. Thanks +-- |This was sent by ishah...@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
Re: [Veritas-bu] import a ZFS filesystem holding images
Bart, I did a quick google search and found this Symantec article. It seemed to me that once you import the zpool housing these images to the other media server, you shouldn't need to import them but instead would need to make the new media server the owner of these images ? if that is the case and you are effectively decommissioning the old media server, the article below should help you out. http://www.symantec.com/connect/forums/move-ownership-image-disk-storage-unit I'm not sure if you should change the ownership of the images before or after you export the zpool. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WALLEBROEK Bart Sent: Thursday, December 02, 2010 5:28 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] import a ZFS filesystem holding images A File system on an HP disk system is presented to multiple SUN Media Servers. This filesystem is used as DSSU (holding DSSU images) Only 1 is accessing the file system. When that Media Server however goes down we want to import that filesystem on another Media Server (SUN import zpool command). Is this supported by Symantec (I created a case but wanted to check the forum as well) ? Will NetBackup know that these images are already known to the catalog and will this work transparently ? Best Regards, Bart WALLEBROEK Backup Admin ___ 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] Netbackup 6.5.4 - 7.0 client upgrade causing issues in SLP driven backups
We recently upgraded a number of our windows server 2003 clients from 6.5.4 to 7.0. These clients are in policies who's backup and subsequent duplication jobs are managed via a SLP. Ever since the upgrade full backups run with no issue but the cumulative incremental backups have started having issues when backing up a drive that has no change, resulting in a 0 byte backup image file. For some reason, although the activity monitor shows the job as completing successfully, output from the nbstlutil stlilist -u image_incomplete | more shows multiple entries for these clients like the one below... Image stlcorpsql02.corp.dir.spartech.com_1289597375 for Lifecycle winos_slp is NOT_STARTED Copy to winos_su is NOT_STARTED Copy to winos_rep_su is NOT_STARTED Image stlcorpex3a.corp.dir.spartech.com_1289602850 for Lifecycle winos_slp is NOT_STARTED Copy to winos_su is NOT_STARTED Copy to winos_rep_su is NOT_STARTED Image stlcorpex4a.corp.dir.spartech.com_1289602879 for Lifecycle winos_slp is NOT_STARTED Copy to winos_su is NOT_STARTED Copy to winos_rep_su is NOT_STARTED These entries do not clear unless we force the cancellation of all pending SLP activity asscociated with the SLP (in this case winos_slp). Querying the backup client on these hosts works fine for all drives backed up during a full backup and all drives during a cumulative backup that had some change data. Any drives that generated a 0 byte file during the cumulative incremental backup give the following error message when querying their data in the netbackup client... WARNING: unable to list the specified files using the current search criteria Support seem at a bit of a loss. Does anyone have any ideas ? Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] nbsl logging on master and media servers
Can anyone tell me what is being logged in the nbsl logs and if I need them ? From what I can gather it's something to do with NOM (which we don't use). We recently stopped sending backups through one of our media servers but have yet to totally decommission it and this morning I came in to find our logs directory on the master server filled with nbsl logs under /opt/openv/logs/nbsl. All it seems to be doing is spawning the same line over and over referring to the media server (stlcorpnbu1) 1,51216,137,132,2160121,1289485178787,11922,1,0:,0:,35:InsecureServerEva luator::allow_peer,2,(513|A33:stlcorpnbu1.corp.dir.spartech.com|A10:10.1 .5.235|u16:3422|) The media server itself is also filling up with nbsl logs. Do I need them, can I delete them and how can I stop nbsl from logging in the future ? Do I just delete the nbsl directory ? Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] nbsl logging on master and media servers
Girish, You’re right on the money with the partially decommissioned media server. We’ve run a whole host of emmcmd commands to clear up stale entries for old media servers, ndmp clients etc and now probably have the cleanest NBU environment we’ve had in a very long time. Some google searches confirmed what you’d mentioned about the importance of the NBSL daemon so we won’t play with the logging levels now we know what was causing NBSL to generate so many logs. Thanks, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Girish Jorapurkar [mailto:giris...@yahoo.com] Sent: Thursday, November 11, 2010 10:11 AM To: Nic Solomons; Mark Glazerman; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Cc: Girish Jorapurkar Subject: Re: [Veritas-bu] nbsl logging on master and media servers NBSL is used by all GUIs (Java, Windows, NOM, OpsCenter) and some CLIs too. So, turning off the logging or deleting 'nbsl' log directory is not a good idea. Instead you may want to address semi-decommissioned media server. You must have removed the media server from one or more configuration (bp.conf?) but not all places (EMM db?) on the master server. Also, NB services on the media server itself may be still running and trying to communicate with the master. You may want to follow supported/recommended way of decommissioning media servers: http://www.symantec.com/connect/forums/netbackup-media-server-decommissioning-tool-now-653-70 HTH, /Girish From: Nic Solomons nic.solom...@attenda.net To: Mark Glazerman mark.glazer...@spartech.com; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Sent: Thu, November 11, 2010 9:57:27 AM Subject: Re: [Veritas-bu] nbsl logging on master and media servers Mark, /usr/openv/netbackup/bin/vxlogcfg -a -p NB -o 132 -s DebugLevel=0 -s DiagnosticLevel=0 Should turn off that logging for you. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: 11 November 2010 14:23 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] nbsl logging on master and media servers Can anyone tell me what is being logged in the nbsl logs and if I need them ? From what I can gather it’s something to do with NOM (which we don’t use). We recently stopped sending backups through one of our media servers but have yet to totally decommission it and this morning I came in to find our logs directory on the master server filled with nbsl logs under /opt/openv/logs/nbsl. All it seems to be doing is spawning the same line over and over referring to the media server (stlcorpnbu1) 1,51216,137,132,2160121,1289485178787,11922,1,0:,0:,35:InsecureServerEvaluator::allow_peer,2,(513|A33:stlcorpnbu1.corp.dir.spartech.com|A10:10.1.5.235|u16:3422|) The media server itself is also filling up with nbsl logs. Do I need them, can I delete them and how can I stop nbsl from logging in the future ? Do I just delete the nbsl directory ? Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. The information contained in this e-mail and its attachments is confidential. It is intended only for the named address(es) and may not be disclosed to anyone else without Attenda's consent. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] A Heads-Up for anyone using OST with Data Domain
Under NFS clients on our DD670's we noticed that /backup/ost was shared out to * and as we're trying to eliminate shares that are wide open (and we were under the misconception that OST was it's own protocol unassociated with NFS) we deleted the share. BOOM !!... all backups to OST storage units instantly start to fail. DO NOT REMOVE THIS NFS SHARE !! If you do, don't try and use the admin guide to re-add it because they have the syntax printed incorrectly. In order to get it back in with the correct permissions do the following... nfs add /backup/ost (insecure) Hope this saves someone the 2 hours we just wasted trying to work out the mess we'd caused ourselves !! Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Oracle hot backup with yearly retention: redo logs?
Like the previous responder said, the retention of the redo logs are controlled by RMAN and not Netbackup. Have the DBA's change the retention of the RMAN backups to match their requirement if a hot backup is the only way you can backup the data. If you can bring down the database so that there are no open tables or transactions being performed, you can perform a full cold backup of all the required filesystems inside Netbackup and then set the retention of that backup to match the new requirements. One thing to note here is that in order for you to capture all the files required to restart the database from this backup, you will need to make sure that any files currently excluded from your OS backups (such as redo logs, dbf's etc..) are not excluded in your cold backup. Your DBA's should know which files they'll need and which ones they won't. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of jjperry Sent: Wednesday, September 22, 2010 2:08 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Oracle hot backup with yearly retention: redo logs? robmod wrote: Hello everybody, we have many oracle instances in archivelog mode. We keep archivelogs for 30 days. Now we have to backup some oracle instance only with full hot backups with long retention (up to 3 years). As oracle man says redo logs are needed for restore, so we have to change the retention of the archivelogs created during long retention hot backup. How would you backup oracle in this way? I would suggest that you take a look at http://www.symantec.com/business/support/index?page=contentid=TECH49868 as a possible reference. While this pertains mostly to NetBackup, the RMAN information on retentions should be independent of the backup product used as it resides in the RMAN setup. From reading the article, not using RMAN myself as that is relegated to the DBAs, it would seem that you would have to change the retention on all backup in RMAN to support just the yearly backups you need to keep. Another way I would suggest that might possibly work is to backup the database offline for the yearly backup instead of the hot backup as it should not require the archive logs at that point, at least it seems that you would not need them with the DB down. +-- |This was sent by jjpe...@water.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
[Veritas-bu] Can I duplicate existing netbackup images using a brand new SLP
We have been backing up elements of an evault environment to an intelligent disk pool in our data center. Does anyone know of a way to setup a new SLP, consisting of this existing disk pool and an offsite disk pool, and use this new SLP to duplicate both new and existing images (which already reside on the local disk pool) to the offsite disk pool ? We know this will work with new backup images written to the original disk pool but we'd really like to be able to send the existing images as well. Any advice on how we can achieve this would be most appreciated. Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question for NetBackup 7.0 Dedup user ORData Domain users
Using the ddboost ost plugin from Data Domain in conjunction with Netbackup moves the metabase comparisons from the data domain appliance to the media server. This dramatically reduces the amount of backup traffic being sent to the data domain and speeds up the backups considerably. We looked at NBU 7's built in dedupe and saw ok numbers on small file, OS type backup data but for applications like exchange where we currently store around 40 full copies in 1.8TB of space on our data domains, we couldn't get 4 copies in the same amount of space using netbackup's dedupe. The fixed block dedupe algorithm of netbackups built in dedupe cannot handle large files as well as the variable block compression algorithms of the data domain. Also.. from a licensing point of view we worked out it was essentially $1000 per TB to license dedupe in Netbackup (Enterprise disk option and dedupe is licensed per TB). This is something you have to factor in, especially if you have a large environment. Replication of this backed up data is something else you'd need to devise a solution for. With data Domain, the replication part is easy. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of stefanos Sent: Wednesday, August 25, 2010 3:02 AM To: 'Travis Kelley'; judy_hinchcli...@administaff.com; cal...@kforce.com; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Question for NetBackup 7.0 Dedup user ORData Domain users The big difference between DataDomain (and all appliances) and nebackup deduplication option is that netbackup can do the process on the client. This will speed up the time of the backup. With DD and netbackup media server deduplication, nothing will change at your backup time, as all your data will travel to the media server. Do not listen to the companies about the deduplication ratio. Your data is unique, and nobody can predict the ratio. Ask for a demo from both companies. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Travis Kelley Sent: Wednesday, August 25, 2010 12:38 AM To: judy_hinchcli...@administaff.com; cal...@kforce.com; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Question for NetBackup 7.0 Dedup user OR Data Domain users Data domain also has a limit to the amount of data one of their units can track but its fairly high. If you need more than 32TB of deduped data in PD you do need to deploy a seperate puredisk environment. Then PD just splits the hash space into chunks and stores data on whichever node it hases to. I'm not sure what their upper limit is but it can scale quite high also. On 8/24/10, judy_hinchcli...@administaff.com judy_hinchcli...@administaff.com wrote: Remember that the built in de-dup as a limit on the amount of data it can keep track of. Over that amount you need to use a de-dup appliance. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Alley, Chris Sent: Tuesday, August 24, 2010 4:09 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Question for NetBackup 7.0 Dedup user OR Data Domain users We are looking to change our backups to a disk based deduplication solution, and 2 of our options are to utilize NetBackup 7.0's built in dedupe (Client and Media server) or to put a Data Domain box in. I wanted to see if I could get some real world feedback on what you guys have been seeing in terms of dedupe rates, performance, etc. For example Data Domain claims we would only see about 5:1 dedupe rate using NetBackup, which seems quite a bit lower than what I would expectand of course they claim they would get about 20:1. I realize that all data is different, which is why I have hopes that several people will reply with what they are seeing. Thanks for your time! ___ 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] Need to find out which media server is backing upwhich client...
Call me a cheat but doesn't the GUI display the media server which handled each backup in the activity monitor ? Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Joseph Despres Sent: Thursday, August 12, 2010 8:59 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Need to find out which media server is backing upwhich client... Other than using bpdbjobs What's a good way to find out which media server is backing up which client? Thanks Joe Despres Backup Engineer CSC 3521 Ribcowski Ct Raleigh, NC 27616 GIS | (o): 1.919.266.1799 | (c): 1.919.931.9674 | jdesp...@csc.com | www.csc.com https://c3.csc.com/groups/netback This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Storage Lifecycle Policies - The end of multi-schedule backup policies ?
We have been playing with the OST plugin for our data domain appliances and have just started looking into using the optimized duplication offering to replicate data between an OST storage unit on Data Domain 1 and another OST storage unit on Data Domain 2. When configuring the Storage Lifecycle Policy, it appears that it is no longer possible to have more than 1 retention period set for the data at each stage of the duplication process. There is 1 retention period for the data written to the 'backup' target in the SLP and another retention period set for the 'duplication' target. Currently, the policy we use to backup this host (and many other hosts) has a 2 month retention on weekly fulls and a 2 week retention on daily fulls. With SLP's it seems that having multiple schedules within a backup policy will no longer be possible unless we have a separate backup policy for each schedule and a separate SLP for each backup policy. Any ideas ? Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Facing Problem with flood of alerts EC-196 netbackup6.5
Some reasons why we have suddenly seen high numbers of 196 errors include... 1) No exclude list on a new client meant that other clients were sat waiting for access to our disk storage units (limited number of concurrent jobs to the same storage unit) while this new client sent huge amounts of useless data to our data domains. All the jobs queued will fail when their backup window closes. 2) Network issues slowed the throughput of our backups to where clients were still waiting to start when their backup window closed. 3) If your storage units / devices were unavailable you'd be getting a different error code although when we were still backing up to tape we'd get 196's if we ran out of scratch tapes and the jobs were sat queued waiting for available media to be loaded into the drives. There could be multiple reasons why you're getting this error. Do you have your jobs on a time or date schedule ? Has there been some schedule creep on other backups which is eating into the window for the clients now failing with 196's ? Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of shekhar deshingkar Sent: Wednesday, August 04, 2010 10:36 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Facing Problem with flood of alerts EC-196 netbackup6.5 Hello, We have setup of one master server so many media server and client list but backup jobs are failed with EC-196 with flood of alerts could you explain any tunning procedure to follow the proper backup scheduled and compltion within specifice window. If you have any info on same please pass. Thanks, Shekhar Dehingkar. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] could not set TCP_NODELAY on socket 1724, h_errno = 10038
We had similar issues and in our environment it seems it's all tied to VSS errors. Sometimes restarting the VSS service on the client and / or hyper-visor was all that was needed. Otherwise rebooting the client always fixed it (but obviously isn't always possible). We tended to get a lot of snapshot errors which accompanied the TCP errors. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Denzo Sent: Wednesday, July 28, 2010 7:14 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] could not set TCP_NODELAY on socket 1724,h_errno = 10038 BELOW ARE THE CONTENTS OF ..\logs\bpbkar 11:03:26.840 AM: [3144.4560] 4 ov_log::OVInit: GENERAL Log Level: 0 11:03:26.840 AM: [3144.4560] 4 ov_log::OVInit: TCP Log Level: 0 11:03:26.841 AM: [3144.4560] 4 ov_log::OVInit: INF - the log mutex: 252 BPBKAR NetBackup Backup/Archive 6.5GA [May 1 2009] Copyright 1993 - 2007 VERITAS Software Corporation All Rights Reserved. 11:03:26.844 AM: [3144.4560] 2 date_debug: DAT - current time: 1280307806, 7/28/2010 11:03:26 AM 11:03:26.844 AM: [3144.4560] 2 date_debug: DAT - 01/01/94 UCT: 757382400, 1/1/1994 2:00:00 AM 11:03:26.844 AM: [3144.4560] 2 date_debug: DAT - 07/01/94 UCT: 773020800, 7/1/1994 2:00:00 AM 11:03:26.844 AM: [3144.4560] 2 WinMain: DAT - standard input handle = 672 11:03:26.845 AM: [3144.4560] 2 WinMain: DAT - standard output handle = 140 11:03:26.845 AM: [3144.4560] 2 WinMain: DAT - standard error handle = 468 11:03:26.852 AM: [3144.4560] 4 tar_backup::V_SetupJobData: INF - dwJobData: 11:03:26.852 AM: [3144.4560] 4 tar_backup::V_SetupJobData: INF - dwJob: 11:03:26.855 AM: [3144.4560] 4 dos_backup::V_PreProcessing: INF - backup privileges enabled, previous = 0 11:03:26.855 AM: [3144.4560] 4 dos_backup::V_PreProcessing: INF - restore privileges enabled, previous = 0 11:03:26.856 AM: [3144.4560] 4 dos_backup::V_PreProcessing: INF - security privileges enabled, previous = 0 11:03:26.856 AM: [3144.4560] 4 dos_backup::V_PreProcessing: INF - tcb privileges enabled, previous = 0 11:03:26.857 AM: [3144.4560] 4 dos_backup::V_PreProcessing: INF - create token privileges enabled, previous = 0 11:03:26.857 AM: [3144.4560] 4 dos_backup::V_PreProcessing: INF - user name: root 11:03:26.857 AM: [3144.4560] 4 dos_backup::V_PreProcessing: INF - no access token: scheduled backup 11:03:26.863 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - BEDS_Init() Enter InitFlags:0x0 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: C: 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: D: 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: E: 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: F: 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: G: 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: H: 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: J: 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Terminal Services 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Windows Network 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: s4zaswsysq01 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Shadow?Copy?Components 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: System?State 11:03:26.897 AM: [3144.4560] 2 ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode 11:03:26.903 AM: [3144.4560] 2 tar_backupt_tfi::create: TAR - Incremental backup using the archive bit 11:03:27.114 AM: [3144.4560] 2 tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received 11:03:27.307 AM: [3144.4560] 2 tar_backup_tfi::setupFileDirectives: TAR - backup filename = ALL_LOCAL_DRIVES 11:03:27.307 AM: [3144.8112] 4 tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds 11:03:27.334 AM: [3144.4560] 2 tar_backup_vxbsa::add: INF - called with '/' 11:03:27.335 AM: [3144.4560] 4 dos_backup::V_VerifyFileSystem: INF - Added: C:\ 11:03:27.335 AM: [3144.4560] 4 dos_backup::V_VerifyFileSystem: INF - Added: D:\ 11:03:27.335 AM: [3144.4560] 4 dos_backup::V_VerifyFileSystem: INF - Added: E:\ 11:03:27.335 AM: [3144.4560] 4 dos_backup::V_VerifyFileSystem: INF - Added: F:\ 11:03:27.335 AM: [3144.4560] 4 dos_backup::V_VerifyFileSystem: INF - Added: G:\ 11:03:27.335 AM: [3144.4560] 4 dos_backup::V_VerifyFileSystem: INF - Added: H:\ 11:03:27.335 AM: [3144.4560] 4
[Veritas-bu] NBU 7.0 Dedupe Stats
Does anyone know how we can find out how much actual data has been backed up when it's been sent to a dedupe disk pool using Media Server Deduplication ? We can see how much space is being taken up on the disk we're sending the data to but can't seem to find an easy way to work out how much data we're deduplicating without adding up the amount of data backed up in each individual backup job. Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Data Domain OST
Renee, We're testing OST as I write this !! We've actually been testing OST and the new dedupe in NBU 7.0. We've been running our exchange backups to an OST storage unit and have seen higher throughput speeds compared to our regular CIFS backups in the limited testing we've done (40mb./sec average compared to 20-25mb/sec). We're leaning towards it being worth the licensing fee to shorten our backup windows, even by a small amount. The built in dedupe works great for windows OS backups but didn’t work too good for our exchange backups (the default fragment size worked against us with exchange data). Also the throughput to disk attached to the media server is much higher than we get to the Data Domain appliances (we hit a peak of 70mb/sec on some of those backups) but they are faster disks so we'd expect this. Our testing seems to be showing that the OST will be used on data that we continue to send to the data domains but we'll be able to push a lot of our backups through a couple of additional media servers to some dumb disk, using a mix of client side and media server dedupe. I'll update some more when we have some more testing completed. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Renee Carlisle Sent: Friday, July 16, 2010 4:24 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Data Domain OST Is anyone out there using a Data Domain with the OST plug in for NetBackup? (Especially if you are running NBU 7) Can someone give me a rough idea what kind of performance numbers you are gettingjust looking for an average mb/s per stream on typical backup jobs. Don't need a lot of detail, just wanting some rough ideas. Thanks Renee ___ 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] Netbackup 7.0 dedup
We have been playing with the new dedup option in a small test environment pushing data from 2 clients through a windows 2008 media server to a 2TB lun presented to that same server. We have things setup to dedup at the media server, not the client and have each of these 2 clients in their own policy. After the initial full backup of these clients, netbackup reported 98-99% deduplication on subsequent fulls we ran which is fantastic. However, even with these numbers inside NBU, the amount of storage being used seems excessive (currently over 80%). Support are telling me that it can take several weeks for the math behind the numbers to actually start accurately reporting the compression figures but I guess I don't understand how 2 clients which total about 850GB and have a minimal change rate, when reporting 98 or 99% compression inside NBU, can be using so much space. Does anyone else have any experience with the dedup option and did you see similar disparity after your initial implementation ? As a point of reference, when setting up the disk pool, we took all the defaults inside the wizard. Thanks in advance Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU7 Real Time Protection
We're also looking at this although we already do something similar by replicating our catalog data using Data Domain appliances. At time of disaster we spin up lights out master and media servers (same hostname and IP's as our production boxes) at our DR site and recover the catalog using the NBU GUI. As I understand it, the Realtime protection element manages this replication directly from inside Netbackup allowing quick recovery of your catalog information at time of disaster. With our current setup, we can have the catalog restored within 25 minutes of getting connectivity to our remote data domain appliance. I'm wondering if there would be a way to have a duplicate DRmaster running at our DR site and have the catalog data replicated to it using this feature ? Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of flyinraptr Sent: Monday, June 21, 2010 6:25 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] NBU7 Real Time Protection Planning a net new implementation of NBU7 - considering options for site DR for the NBU7 Catalog/database. Have not worked with Netbackup RealTime Protection - looking for feedback on whether it is a viable option/ worth the effort etc. +-- |This was sent by greg.p...@wellsfargo.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
Re: [Veritas-bu] RMAN crosscheck
I'm not sure if our DBA's tried this exact method but in our environment, where we back up only to Data Domain, we don't have another repository (eg. Vaulted Tape) to look for any RMAN backup pieces. Once RMAN had expired the images we needed and they had been cleared off the data domain, there was nowhere else where we could look for components to put together a successful restore via RMAN. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Lightner, Jeff [mailto:jlight...@water.com] Sent: Wednesday, May 19, 2010 8:43 AM To: Michael Graff Andersen Cc: Mark Glazerman; Kevin Corley; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck That looks promising. Have you used it successfully? Mark - did you try this when you had your issue? From: Michael Graff Andersen [mailto:mia...@gmail.com] Sent: Wednesday, May 19, 2010 9:05 AM To: Lightner, Jeff Cc: Mark Glazerman; Kevin Corley; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck Think there is, at least according to this page http://ss64.com/ora/rman_crosscheck.html Regards Michael 2010/5/17 Lightner, Jeff jlight...@water.com That's unfortunate. It seems that there ought to be a way to have RMAN rebuild its catalog from NBU much the same the way that NBU can recover images into its catalog from NBU expired but not yet overwritten tapes. From: Mark Glazerman [mailto:mark.glazer...@spartech.com] Sent: Monday, May 17, 2010 12:30 PM To: Lightner, Jeff; Kevin Corley Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck Autobackup is an RMAN setting. We use autobackup and had recovered the controlfile for the attempted restore I talked about earlier. However, because RMAN had already expired the required images from its own catalog, we were unable to recover the data, even with backup images still residing in the Netbackup catalog. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Lightner, Jeff [mailto:jlight...@water.com] Sent: Monday, May 17, 2010 11:27 AM To: Kevin Corley; Mark Glazerman Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck Thanks guys. Is autobackup a setting in RMAN or in NBU? From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kevin Corley Sent: Monday, May 17, 2010 12:23 PM To: Mark Glazerman; Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck As long as you have autobackup enabled, you shouldn't need the rman repository. If netbackup has the images in the catalog, restore the control file from autobackup, which has the rman pieces info and will poll netbackup for the images associated with them. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Monday, May 17, 2010 8:58 AM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck Jeff, I can only really comment on your last question about using expired RMAN images for restores if they are not expired in NetBackup. We had a similar issue a few weeks back where Netbackup could still see images in its catalog of oracle backups (which initiate a RMAN backup via the oracle_backup.sh script) but RMAN had already expired them inside its own catalog. These files were not recoverable by RMAN. We had the DBA's set their retention inside RMAN to match the retention specified inside NBU so that we don't see this mis-match again. Ultimately, RMAN controls the expiration of the images inside its catalog meaning that regardless of the expiration you set for oracle backups inside NBU, RMAN will keep or expire those images, regardless of what Netbackup is trying to tell it. I don't know how you'd configure RMAN to handle your vaulting needs. Would setting the expiration of these images in RMAN to the longest required length of time (4 months for example) mean that the vaulted images would still be good for the max time they'd need to be held on either the Data Domain or tape ? The Netbackup catalog doesn't need to know about the RMAN images for them to still be recoverable by RMAN so you could set a different, shorter expiration inside NBU although this would still leave you with different retentions in the two different catalogs FYI The solaris client we were trying to restore these RMAN images to is running 6.5.4 with a 7.0 master and media server. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun
Re: [Veritas-bu] RMAN crosscheck
We did still have NBU images of the backups that initiated the RMAN backups but once RMAN had expired its own images, these were essentially useless. I don't believe that RMAN is able to query NBU's catalog as part of the crosscheck anyway. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Lightner, Jeff [mailto:jlight...@water.com] Sent: Wednesday, May 19, 2010 8:55 AM To: Mark Glazerman; Michael Graff Andersen Cc: Kevin Corley; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck Thanks. I thought I'd understood you earlier to say you had extant NBU images that you couldn't restore because RMAN said they were expired. If you have no backup images anywhere then nothing's going to recover them even if they aren't marked expired even if it's a standard backup. From: Mark Glazerman [mailto:mark.glazer...@spartech.com] Sent: Wednesday, May 19, 2010 9:50 AM To: Lightner, Jeff; Michael Graff Andersen Cc: Kevin Corley; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck I'm not sure if our DBA's tried this exact method but in our environment, where we back up only to Data Domain, we don't have another repository (eg. Vaulted Tape) to look for any RMAN backup pieces. Once RMAN had expired the images we needed and they had been cleared off the data domain, there was nowhere else where we could look for components to put together a successful restore via RMAN. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Lightner, Jeff [mailto:jlight...@water.com] Sent: Wednesday, May 19, 2010 8:43 AM To: Michael Graff Andersen Cc: Mark Glazerman; Kevin Corley; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck That looks promising. Have you used it successfully? Mark - did you try this when you had your issue? From: Michael Graff Andersen [mailto:mia...@gmail.com] Sent: Wednesday, May 19, 2010 9:05 AM To: Lightner, Jeff Cc: Mark Glazerman; Kevin Corley; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck Think there is, at least according to this page http://ss64.com/ora/rman_crosscheck.html Regards Michael 2010/5/17 Lightner, Jeff jlight...@water.com That's unfortunate. It seems that there ought to be a way to have RMAN rebuild its catalog from NBU much the same the way that NBU can recover images into its catalog from NBU expired but not yet overwritten tapes. From: Mark Glazerman [mailto:mark.glazer...@spartech.com] Sent: Monday, May 17, 2010 12:30 PM To: Lightner, Jeff; Kevin Corley Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck Autobackup is an RMAN setting. We use autobackup and had recovered the controlfile for the attempted restore I talked about earlier. However, because RMAN had already expired the required images from its own catalog, we were unable to recover the data, even with backup images still residing in the Netbackup catalog. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Lightner, Jeff [mailto:jlight...@water.com] Sent: Monday, May 17, 2010 11:27 AM To: Kevin Corley; Mark Glazerman Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck Thanks guys. Is autobackup a setting in RMAN or in NBU? From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kevin Corley Sent: Monday, May 17, 2010 12:23 PM To: Mark Glazerman; Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck As long as you have autobackup enabled, you shouldn't need the rman repository. If netbackup has the images in the catalog, restore the control file from autobackup, which has the rman pieces info and will poll netbackup for the images associated with them. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Monday, May 17, 2010 8:58 AM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck Jeff, I can only really comment on your last question about using expired RMAN images for restores if they are not expired in NetBackup. We had a similar issue a few weeks back where Netbackup could still see images in its catalog of oracle backups (which initiate a RMAN backup via the oracle_backup.sh script) but RMAN had already expired them inside its own catalog. These files were not recoverable by RMAN. We had the DBA's set their retention inside RMAN to match the retention specified inside NBU so that we don't see
Re: [Veritas-bu] RMAN crosscheck
Jeff, I can only really comment on your last question about using expired RMAN images for restores if they are not expired in NetBackup. We had a similar issue a few weeks back where Netbackup could still see images in its catalog of oracle backups (which initiate a RMAN backup via the oracle_backup.sh script) but RMAN had already expired them inside its own catalog. These files were not recoverable by RMAN. We had the DBA's set their retention inside RMAN to match the retention specified inside NBU so that we don't see this mis-match again. Ultimately, RMAN controls the expiration of the images inside its catalog meaning that regardless of the expiration you set for oracle backups inside NBU, RMAN will keep or expire those images, regardless of what Netbackup is trying to tell it. I don't know how you'd configure RMAN to handle your vaulting needs. Would setting the expiration of these images in RMAN to the longest required length of time (4 months for example) mean that the vaulted images would still be good for the max time they'd need to be held on either the Data Domain or tape ? The Netbackup catalog doesn't need to know about the RMAN images for them to still be recoverable by RMAN so you could set a different, shorter expiration inside NBU although this would still leave you with different retentions in the two different catalogs FYI The solaris client we were trying to restore these RMAN images to is running 6.5.4 with a 7.0 master and media server. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: Friday, May 14, 2010 7:12 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] RMAN crosscheck My DBAs are starting to question me about an RMAN crosscheck they are running. Essentially I gather that when they ran it the crosscheck seemed to report even backups run in the last 2 days as expired. On checking the Data Domain unit I can see the images are still there and on running NetBackup commands I see these are NOT expired from NBU's perspective. On doing a search I did find a document at Symantec that talked about RMAN expirations but it only went up through 6.0 so I'm not sure if it is still valid for 6.5. It says essentially that on the NBU side we should set very long retentions (e.g. INFINITY) for all RMAN backup policies then let RMAN keep track of retentions itself. The downside I see to this is we do vaulting of the images on data domain to tape - we set retention on data domain to 1 month then the vault copies get longer retentions (e.g. 3 months for a daily backup). How would we get RMAN to set and keep track of such retention differences? The DBAs have opened a TAR with Oracle to see why the crosscheck is reporting the images as expired but I suspect from the NBU document that the answer will be something like it is expired so far as RMAN is concerned. This also begs the question as to whether RMAN could be used to restore the backups even if they aren't expired so far as NBU is concerned. Does anyone know the answer to that? Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- 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] RMAN crosscheck
RMAN would still need non-expired images in its own catalog to be able to fulfill the requests of the autobackup though right ? Correct me if I'm wrong but whether the images are still in NBU or not, unless they are still in the RMAN catalog the recovery request by RMAN will fail. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Kevin Corley [mailto:kevin.cor...@apollogrp.edu] Sent: Monday, May 17, 2010 11:23 AM To: Mark Glazerman; Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck As long as you have autobackup enabled, you shouldn't need the rman repository. If netbackup has the images in the catalog, restore the control file from autobackup, which has the rman pieces info and will poll netbackup for the images associated with them. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Monday, May 17, 2010 8:58 AM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck Jeff, I can only really comment on your last question about using expired RMAN images for restores if they are not expired in NetBackup. We had a similar issue a few weeks back where Netbackup could still see images in its catalog of oracle backups (which initiate a RMAN backup via the oracle_backup.sh script) but RMAN had already expired them inside its own catalog. These files were not recoverable by RMAN. We had the DBA's set their retention inside RMAN to match the retention specified inside NBU so that we don't see this mis-match again. Ultimately, RMAN controls the expiration of the images inside its catalog meaning that regardless of the expiration you set for oracle backups inside NBU, RMAN will keep or expire those images, regardless of what Netbackup is trying to tell it. I don't know how you'd configure RMAN to handle your vaulting needs. Would setting the expiration of these images in RMAN to the longest required length of time (4 months for example) mean that the vaulted images would still be good for the max time they'd need to be held on either the Data Domain or tape ? The Netbackup catalog doesn't need to know about the RMAN images for them to still be recoverable by RMAN so you could set a different, shorter expiration inside NBU although this would still leave you with different retentions in the two different catalogs FYI The solaris client we were trying to restore these RMAN images to is running 6.5.4 with a 7.0 master and media server. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: Friday, May 14, 2010 7:12 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] RMAN crosscheck My DBAs are starting to question me about an RMAN crosscheck they are running. Essentially I gather that when they ran it the crosscheck seemed to report even backups run in the last 2 days as expired. On checking the Data Domain unit I can see the images are still there and on running NetBackup commands I see these are NOT expired from NBU's perspective. On doing a search I did find a document at Symantec that talked about RMAN expirations but it only went up through 6.0 so I'm not sure if it is still valid for 6.5. It says essentially that on the NBU side we should set very long retentions (e.g. INFINITY) for all RMAN backup policies then let RMAN keep track of retentions itself. The downside I see to this is we do vaulting of the images on data domain to tape - we set retention on data domain to 1 month then the vault copies get longer retentions (e.g. 3 months for a daily backup). How would we get RMAN to set and keep track of such retention differences? The DBAs have opened a TAR with Oracle to see why the crosscheck is reporting the images as expired but I suspect from the NBU document that the answer will be something like it is expired so far as RMAN is concerned. This also begs the question as to whether RMAN could be used to restore the backups even if they aren't expired so far as NBU is concerned. Does anyone know the answer to that? Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- 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
Re: [Veritas-bu] RMAN crosscheck
Autobackup is an RMAN setting. We use autobackup and had recovered the controlfile for the attempted restore I talked about earlier. However, because RMAN had already expired the required images from its own catalog, we were unable to recover the data, even with backup images still residing in the Netbackup catalog. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Lightner, Jeff [mailto:jlight...@water.com] Sent: Monday, May 17, 2010 11:27 AM To: Kevin Corley; Mark Glazerman Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] RMAN crosscheck Thanks guys. Is autobackup a setting in RMAN or in NBU? From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kevin Corley Sent: Monday, May 17, 2010 12:23 PM To: Mark Glazerman; Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck As long as you have autobackup enabled, you shouldn't need the rman repository. If netbackup has the images in the catalog, restore the control file from autobackup, which has the rman pieces info and will poll netbackup for the images associated with them. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Monday, May 17, 2010 8:58 AM To: Lightner, Jeff Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] RMAN crosscheck Jeff, I can only really comment on your last question about using expired RMAN images for restores if they are not expired in NetBackup. We had a similar issue a few weeks back where Netbackup could still see images in its catalog of oracle backups (which initiate a RMAN backup via the oracle_backup.sh script) but RMAN had already expired them inside its own catalog. These files were not recoverable by RMAN. We had the DBA's set their retention inside RMAN to match the retention specified inside NBU so that we don't see this mis-match again. Ultimately, RMAN controls the expiration of the images inside its catalog meaning that regardless of the expiration you set for oracle backups inside NBU, RMAN will keep or expire those images, regardless of what Netbackup is trying to tell it. I don't know how you'd configure RMAN to handle your vaulting needs. Would setting the expiration of these images in RMAN to the longest required length of time (4 months for example) mean that the vaulted images would still be good for the max time they'd need to be held on either the Data Domain or tape ? The Netbackup catalog doesn't need to know about the RMAN images for them to still be recoverable by RMAN so you could set a different, shorter expiration inside NBU although this would still leave you with different retentions in the two different catalogs FYI The solaris client we were trying to restore these RMAN images to is running 6.5.4 with a 7.0 master and media server. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: Friday, May 14, 2010 7:12 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] RMAN crosscheck My DBAs are starting to question me about an RMAN crosscheck they are running. Essentially I gather that when they ran it the crosscheck seemed to report even backups run in the last 2 days as expired. On checking the Data Domain unit I can see the images are still there and on running NetBackup commands I see these are NOT expired from NBU's perspective. On doing a search I did find a document at Symantec that talked about RMAN expirations but it only went up through 6.0 so I'm not sure if it is still valid for 6.5. It says essentially that on the NBU side we should set very long retentions (e.g. INFINITY) for all RMAN backup policies then let RMAN keep track of retentions itself. The downside I see to this is we do vaulting of the images on data domain to tape - we set retention on data domain to 1 month then the vault copies get longer retentions (e.g. 3 months for a daily backup). How would we get RMAN to set and keep track of such retention differences? The DBAs have opened a TAR with Oracle to see why the crosscheck is reporting the images as expired but I suspect from the NBU document that the answer will be something like it is expired so far as RMAN is concerned. This also begs the question as to whether RMAN could be used to restore the backups even if they aren't expired so far as NBU is concerned. Does anyone know the answer to that? Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE
[Veritas-bu] Strange RMAN Behavior
We have a host that houses an oracle instance backed up by 2 separate policies. 1 Policy backups up archivelogs. The second policy backs up the database. Both of these policies call the same RMAN script. Both policies point to the same storage unit group which contains 2 storage units. These storage units are 2 directories on a data domain storage appliance In the activity monitor, both policies show that they run when they are supposed to run and complete without error. The backups logs for all backups managed for these 2 policies show the backups complete without error. However... When querying the Netbackup catalog, We can see images from the archive log backup policy but cannot see a single image for the database policy. Also... looking on the datadomain, we can see the images written by the archive policy but cannot see the images written by the database policy. Both policies are subject to the same RMAN parameters so we are totally baffled as to why one would work successfully and the other would appear to be working fine but never sends any data. The only obvious difference I can see anywhere in this whole setup is in the detailed info for the jobs created by the two policies. In the archive policy (which works) we see the path to the data domain clearly displayed in the job info 4/29/2010 2:53:23 PM - requesting resource DataDomain_OraArchTier1 4/29/2010 2:53:23 PM - requesting resource nbumaster01.sun.spartech.com.NBU_CLIENT.MAXJOBS.oraprod.sun.spartech.com 4/29/2010 2:53:23 PM - requesting resource nbumaster01.sun.spartech.com.NBU_POLICY.MAXJOBS.Solaris_OraArchTier1 4/29/2010 2:53:23 PM - granted resource nbumaster01.sun.spartech.com.NBU_CLIENT.MAXJOBS.oraprod.sun.spartech.com 4/29/2010 2:53:23 PM - granted resource nbumaster01.sun.spartech.com.NBU_POLICY.MAXJOBS.Solaris_OraArchTier1 4/29/2010 2:53:23 PM - granted resource media...@h;Path=/dd/ddstldd560/backup/oracle/arch;MediaServer=nbumed ia01.sun.spartech.com 4/29/2010 2:53:23 PM - granted resource ddnbumedia01_OraArchTier1_1 4/29/2010 2:53:24 PM - estimated 0 Kbytes needed 4/29/2010 2:53:24 PM - started process bpbrm (5715) 4/29/2010 2:53:24 PM - connecting 4/29/2010 2:53:34 PM - connected; connect time: 00:00:10 4/29/2010 2:53:37 PM - begin writing 4/29/2010 3:06:30 PM - end writing; write time: 00:12:53 the requested operation was successfully completed(0) However, in the db backup job, although it appears to assign the storage unit successfully, it never shows this path to the data domain 4/17/2010 12:59:59 AM - requesting resource DataDomain_OraDbTier1 4/17/2010 12:59:59 AM - requesting resource nbumaster01.sun.spartech.com.NBU_CLIENT.MAXJOBS.oraprod.sun.spartech.com 4/17/2010 12:59:59 AM - requesting resource nbumaster01.sun.spartech.com.NBU_POLICY.MAXJOBS.Solaris_OraDbTier1 4/17/2010 12:59:59 AM - granted resource nbumaster01.sun.spartech.com.NBU_CLIENT.MAXJOBS.oraprod.sun.spartech.com 4/17/2010 12:59:59 AM - granted resource nbumaster01.sun.spartech.com.NBU_POLICY.MAXJOBS.Solaris_OraDbTier1 4/17/2010 12:59:59 AM - granted resource ddnbumedia01_OraDbTier1_1 4/17/2010 1:00:00 AM - estimated 0 Kbytes needed 4/17/2010 1:00:00 AM - started process bpbrm (16780) 4/17/2010 1:00:01 AM - connecting 4/17/2010 1:00:01 AM - connected; connect time: 00:00:00 4/17/2010 6:13:01 AM - end writing the requested operation was successfully completed(0) Has anyone seen anything like this before ? This is baffling us as the oracle backup script called by Netbackup, the RMAN parameters on the host and the storage units are all the same for both of these policies but we can see data from one and nothing from the other. I should also point out that we have an OS backup that runs on the host which also writes to the data domain without issue. Any help greatly appreciated, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Strange RMAN Behavior
$RMAN_LOG_FILE echo BACKUP ENDED $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo $RMAN_LOG_FILE fi x=x+1 if [ x = 10 ]; then EXIT 0 fi done [r...@oraprod] / Also... here is the log from the hot database backup that is running every morning at 1am but not sending any data anywhere. [r...@oraprod] /var/adm/log/bkup_logs vi prod1159_042910.out prod1159_042910.out 31880 lines, 1726279 characters BACKUP STARTED /usr/openv/netbackup/bin/oracle_backup.sh initiated backup of prod1159 started on Thu Apr 29 01:00:09 CDT 2010 RMAN: /1159/prod1159db/9.2.0/bin/rman ORACLE_SID: prod1159 ORACLE_USER: oracle ORACLE_HOME: /1159/prod1159db/9.2.0 TNS_ADMIN: /1159/prod1159db/9.2.0/network/admin/prod1159_oraprod NB_ORA_FULL: 1 NB_ORA_INCR: 0 NB_ORA_CINC: 0 NB_ORA_SERV: nbumaster01.sun.spartech.com NB_ORA_POLICY: Solaris_OraDbTier1 Hot backup requested Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have mail. RMAN 2 3 4 5 6 7 8 9 10 11 12 13 14 15 RMAN RMAN (c) 1995, 2002, Oracle Corporation. All rights reserved. connected to target database: PROD1159 (DBID=3702129868) connected to recovery catalog database RMAN 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Starting backup at 29-APR-10 starting full resync of recovery catalog full resync complete allocated channel: ORA_SBT_TAPE_1 channel ORA_SBT_TAPE_1: sid=691 devtype=SBT_TAPE channel ORA_SBT_TAPE_1: Veritas NetBackup for Oracle - Release 6.5 (2007111606) allocated channel: ORA_SBT_TAPE_2 channel ORA_SBT_TAPE_2: sid=210 devtype=SBT_TAPE channel ORA_SBT_TAPE_2: Veritas NetBackup for Oracle - Release 6.5 (2007111606) allocated channel: ORA_SBT_TAPE_3 channel ORA_SBT_TAPE_3: sid=250 devtype=SBT_TAPE channel ORA_SBT_TAPE_3: Veritas NetBackup for Oracle - Release 6.5 (2007111606) allocated channel: ORA_SBT_TAPE_4 channel ORA_SBT_TAPE_4: sid=400 devtype=SBT_TAPE channel ORA_SBT_TAPE_4: Veritas NetBackup for Oracle - Release 6.5 (2007111606) channel ORA_SBT_TAPE_1: starting incremental level 0 datafile backupset channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset input datafile fno=00429 name=/1159/prod1159data/applsysd08.dbf input datafile fno=00400 name=/1159/prod1159data/applsysd03.dbf /ENDED channel ORA_SBT_TAPE_4: sid=312 devtype=SBT_TAPE channel ORA_SBT_TAPE_4: Veritas NetBackup for Oracle - Release 6.5 (2007111606) channel ORA_SBT_TAPE_1: starting archive log backupset channel ORA_SBT_TAPE_1: specifying archive log(s) in backup set input archive log thread=1 sequence=9073 recid=9067 stamp=717570006 channel ORA_SBT_TAPE_1: starting piece 1 at 29-APR-10 channel ORA_SBT_TAPE_1: finished piece 1 at 29-APR-10 piece handle=b_p2lcafva_1_1 comment=API Version 2.0,MMS Version 5.0.0.0 channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:56 Finished backup at 29-APR-10 Starting Control File Autobackup at 29-APR-10 piece handle=c-3702129868-20100429-02 comment=API Version 2.0,MMS Version 5.0.0.0 Finished Control File Autobackup at 29-APR-10 RMAN Recovery Manager complete. Script /usr/openv/netbackup/bin/oracle_backup.sh ended successfully on Thu Apr 29 05:02:15 CDT 2010 BACKUP ENDED Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: Stafford, Geoff [mailto:gstaff...@barclaycardus.com] Sent: Thursday, April 29, 2010 3:24 PM To: veritas-bu@mailman.eng.auburn.edu Cc: Mark Glazerman Subject: RE: Strange RMAN Behavior Can you post the send statement from the rman scripts? Are you defining NB_ORA_POLICY? Date: Thu, 29 Apr 2010 15:14:25 -0500 From: Mark Glazerman mark.glazer...@spartech.com Subject: [Veritas-bu] Strange RMAN Behavior
[Veritas-bu] Changing backup retention periods
We've had a request to extend the retention period on backups from one of our hosts so that data needed for some troubleshooting won't expire before it can be used. Currently the retention period for this data is 1 week. If I change the retention period in the policy that backed up this data to 2 weeks, will this change be applied to both future and past backups handled by this policy ? Essentially I'm trying to work out if this change will be applied retro-actively to existing backup images ? Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NBU 7.0 hotfix 7.0.0.1 for Microsoft Hyper-V
Good morning forum., The release notes for NBU 7.0 say that hotfix 7.0.0.1 is needed (see page 76 of ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Serv er/340098.pdf) Does anyone know where we get this from. We've contacted Datalink support who we use for tier 1 and 2 support on our Symantec products and they have yet to get back to us with where we can find this patch. Fileconnect doesn't have anything either. I thought NBU 7.0 was supposed to work with Hyper-V out the box, how come we need to apply a hotfix to get it working ?? Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] VMware backups to remote VMware Backup proxy server
Is backing VMware machines feasible to a remote VMware Backup proxy server over a T1 line ? We're about to virtualize some clients at a remote facility (Ripon, WI) and have been advised by support (datakink) that we won't be able to use our ESX server as the backup proxy server and that we should make the current NBU media server (St. Louis, MO) the proxy server for the VMware backups. We're talking about 4 Virtual hosts with about 200GB of data between them. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VMware backups to remote VMware Backup proxy server
Thanks for your input. We normally use puredisk for all of our remote server backups so this is the first time that we’ve looked into backing up a remote client through Netbackup. Ed’s math certainly opened my eyes to the fact that ANY type of backup of these clients is going to be ugly. Back to the drawing board me thinks !! Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com] Sent: Tuesday, November 17, 2009 4:13 PM To: Mark Glazerman Cc: veritas-bu@mailman.eng.auburn.edu; veritas-bu-boun...@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VMware backups to remote VMware Backup proxy server I don't think you would like the results of this solution. As you know, a snapshot of the vm is copied to the backup proxy's holding tank and it isn't released on the ESX server until this is completed. I'm pretty sure you would end up with snapshots being released before the copy process is done, and thus you would get failed backups. Best practice is to get these done as quickly as possible. Even doing a normal backup with the client on the vm will take forever, based on Ed's math. 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/ 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. Mark Glazerman mark.glazer...@spartech.com Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 11/17/2009 10:03 AM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] VMware backups to remote VMware Backup proxy server Is backing VMware machines feasible to a remote VMware Backup proxy server over a T1 line ? We’re about to virtualize some clients at a remote facility (Ripon, WI) and have been advised by support (datakink) that we won’t be able to use our ESX server as the backup proxy server and that we should make the current NBU media server (St. Louis, MO) the proxy server for the VMware backups. We’re talking about 4 Virtual hosts with about 200GB of data between them. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ 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] Backing up a VMWare host - Any tips ?
We are about to deploy VMware to a remote location where we will convert 4 or 5 physical windows hosts into a number of VM machines which will then reside on one physical client. I have done some reading and it appears that NBU best practice calls for a VM proxy server to handle the backing up of the VMDK's of the VM machines. However, presenting shared storage between our NetBackup environment and this remote location is not an option. What is the best way for us to back up these VM's through NetBackup (6.5.4) other than installing a standard NBU client on them all which, in our minds, would do away with many of the advantages of running VMware in the first place ? We have available enterprise client licenses for the VMware host (physical box) and our master server is currently backing up a number of Microsoft HyperV hosts which I believe uses some of the same snapshot technology that the VM machines will need to use. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to use the DataDomain system cleaning process
Data Domain appliances run a cleaning cycle on a schedule set by the system administrators. In our environment (2xDD560's and 2xDD430's) we run a clean every Monday at 8am which takes about 2 hours to complete. You can run a clean as often as you want. The cleaning cycle takes its cues from whatever backup software you use (in our case Netbackup). If netbackup says that a backup image can be expired the Data Domain appliance marks those blocks as allowed to be overwritten next time data is written to the device. All data expiration on the Data Domain appliances uses the retention policies setup in whatever wrote the data to the appliance. I can't find a way to look at the admin guides without having a Data Domain support login. Sorry. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of nguytom Sent: Thursday, October 29, 2009 12:03 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] How to use the DataDomain system cleaning process Hi All, I hear DataDomain has DataDomain system cleaning process, anyone knows about it please let me know (command line and how to run the cleaning process, also you can please share me DataDomain OS Admin Guide, I don't have access to DataDomain account because I like to learn on it before we implan datadomain in our system. Thanks. +-- |This was sent by ngu...@yahoo.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
Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4
We've resolved this. It was an oversight on our part. The admin who setup both of these boxes linked the standard location for catalog data from /usr/openv/netbackup/db to another filesystem. We'd blown away the netbackup install on the remote test server and hadn't recreated this link. After recreating the link tha catalog restore was successful. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Tuesday, September 22, 2009 1:16 PM To: Justin Piszcz Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4 Justin, Thanks for your reply. Your mention of the exact same error message being linked to a server with dual NIC's hit home because we have added an additional network interface to allow this server to communicate with our data domains over a private network. We're looking into whether the different hostnames associated with these interfaces may be the problem. Thanks for giving us some food for thought. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: Justin Piszcz [mailto:jpis...@lucidpixels.com] Sent: Tuesday, September 22, 2009 12:25 PM To: Mark Glazerman Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4 Hi, When you are recovering the catalog are you recovering it to the exact same location as you have on your existing master server? 1. if /usr/openv - /mypartition 2. then on the restore server you have to have the same thing with the same hostname as well, or else it won't work. 3. Did you include the DR file as well? But that failure looks a bit strange.. http://www.symantec.com/connect/forums/total-meltdown-unablle-recover-nbdb http://seer.entsupport.symantec.com/docs/285935.htm Etrack Incident = ET834802 Description: Catalog recovery from a hot catalog backup would fail with the following error when the entry for EMMSERVER in bp.conf was different than the SERVER name for the master server, but, they were actually the same machine. This would occur when there were two NICs in the master server. Failed to find last NBDB backup image record for client serverName with policy policyName (227) Has anything changed in your environment besides the 6.5.4 upgrade? Justin. On Tue, 22 Sep 2009, Mark Glazerman wrote: We upgraded to 6.5.4 about 4 months ago and have just started preparing for our first DR test at this version level (previous successful tests at 6.5.1). We have a support call open with datalink because we have so far been unable to restore our catalog to our test master server. The catalog restore (initiated with bprecover -wizard) restores all the client images (25GB or so) but pukes every time with the following error... 12:58:19.201 [13861] 16 bprecover: ERR - Failed to find last NBDB backup image record for client nbumaster01.sun.spartech.com with policy NBU_CATALOG_HOT (227) 12:58:19.221 [13861] 16 bprecover: Failed to recover catalog (227) Has anyone out there seen anything similar since upgrading to 6.5.4 ? As a point of reference our test master server is configured and patched exactly like our production box. Our worry is that besides issues in testing, we may have exposed a huge hole in our production restore capabilities with regard to a master server loss. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ 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] Catalog restore failing after upgrade to 6.5.4
We upgraded to 6.5.4 about 4 months ago and have just started preparing for our first DR test at this version level (previous successful tests at 6.5.1). We have a support call open with datalink because we have so far been unable to restore our catalog to our test master server. The catalog restore (initiated with bprecover -wizard) restores all the client images (25GB or so) but pukes every time with the following error... 12:58:19.201 [13861] 16 bprecover: ERR - Failed to find last NBDB backup image record for client nbumaster01.sun.spartech.com with policy NBU_CATALOG_HOT (227) 12:58:19.221 [13861] 16 bprecover: Failed to recover catalog (227) Has anyone out there seen anything similar since upgrading to 6.5.4 ? As a point of reference our test master server is configured and patched exactly like our production box. Our worry is that besides issues in testing, we may have exposed a huge hole in our production restore capabilities with regard to a master server loss. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4
Justin, Thanks for your reply. Your mention of the exact same error message being linked to a server with dual NIC's hit home because we have added an additional network interface to allow this server to communicate with our data domains over a private network. We're looking into whether the different hostnames associated with these interfaces may be the problem. Thanks for giving us some food for thought. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: Justin Piszcz [mailto:jpis...@lucidpixels.com] Sent: Tuesday, September 22, 2009 12:25 PM To: Mark Glazerman Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Catalog restore failing after upgrade to 6.5.4 Hi, When you are recovering the catalog are you recovering it to the exact same location as you have on your existing master server? 1. if /usr/openv - /mypartition 2. then on the restore server you have to have the same thing with the same hostname as well, or else it won't work. 3. Did you include the DR file as well? But that failure looks a bit strange.. http://www.symantec.com/connect/forums/total-meltdown-unablle-recover-nbdb http://seer.entsupport.symantec.com/docs/285935.htm Etrack Incident = ET834802 Description: Catalog recovery from a hot catalog backup would fail with the following error when the entry for EMMSERVER in bp.conf was different than the SERVER name for the master server, but, they were actually the same machine. This would occur when there were two NICs in the master server. Failed to find last NBDB backup image record for client serverName with policy policyName (227) Has anything changed in your environment besides the 6.5.4 upgrade? Justin. On Tue, 22 Sep 2009, Mark Glazerman wrote: We upgraded to 6.5.4 about 4 months ago and have just started preparing for our first DR test at this version level (previous successful tests at 6.5.1). We have a support call open with datalink because we have so far been unable to restore our catalog to our test master server. The catalog restore (initiated with bprecover -wizard) restores all the client images (25GB or so) but pukes every time with the following error... 12:58:19.201 [13861] 16 bprecover: ERR - Failed to find last NBDB backup image record for client nbumaster01.sun.spartech.com with policy NBU_CATALOG_HOT (227) 12:58:19.221 [13861] 16 bprecover: Failed to recover catalog (227) Has anyone out there seen anything similar since upgrading to 6.5.4 ? As a point of reference our test master server is configured and patched exactly like our production box. Our worry is that besides issues in testing, we may have exposed a huge hole in our production restore capabilities with regard to a master server loss. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Duplicate master server hosed - advice ?
We have a duplicate NBU master server at a third part site that we use for DR. We're recently upgraded to 6.5.4 in production and wanted to upgrade the DR master server before an upcoming test. We made the mistake of deleting all the images from master server prior to starting the upgrade and this has basically hosed the EMM database to the point where neither the upgrade to 6.5.4 or the uninstall scripts for 6.5.1 keep failing. We thought we would be able to restore a catalog and it's associated images to get a working EMM database but because the catalogs have been backed up with NBU 6.5.4 and the master server we're trying to import them to is at 6.5.1 this isn't working either. What are the risks associated with deleting the /usr/openv/netbackup directory so we can do a fresh install of NBU 6.5 and then patch it to 6.5.4 ? What other directories or files would I need to remove from this duplicate server before trying to install from scratch ? Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] EVault Licensing
We've just upgraded our NBU environment to 6.5.4 and want to start testing the evault policy option which comes with this release. Can anyone tell me if our support partner (Datalink) is correct in saying that a standard application / database pack is all we need to be able to backup our evault client using this new policy type ? At the moment we can't even find this policy type on our master which implies we probably need an additional license of some kind too. Just trying to get it straight in my head before we approach datalink. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] EVault Licensing
Renee, Thanks for such a quick response. In addition to this DB pack on the client, do we also need a license on the master server to enable the new Evault policy type ? Thanks in advance, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Renee Carlisle [mailto:rcarli...@serverwarecorp.com] Sent: Wednesday, September 09, 2009 10:30 AM To: Mark Glazerman; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: RE: EVault Licensing Yes, it is just a DB agent...keep in mind if you have EV 8 a couple of the new databases are not picked up yet with 6.5.4 and you have to do some manual integration to get those database, that will be fixed in NBU 7 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Wednesday, September 09, 2009 11:25 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] EVault Licensing We've just upgraded our NBU environment to 6.5.4 and want to start testing the evault policy option which comes with this release. Can anyone tell me if our support partner (Datalink) is correct in saying that a standard application / database pack is all we need to be able to backup our evault client using this new policy type ? At the moment we can't even find this policy type on our master which implies we probably need an additional license of some kind too. Just trying to get it straight in my head before we approach datalink. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup 6.5 Catalog backup - Issue???
Dennis, What do you have as your backup selection inside your catalog policy. We have always used the default backup selection in our catalog policies (1 Daily full, daytime cumulative every hour, night time cumulative every 3 hours) and a quick look at our policy shows we have specified CATALOG_DRIVEN_BACKUP as the backup selection. I can’t find anything that confirms exactly what is backed up by this backup selection but we also do our DR testing at Sungard in Philly and have successfully restored our catalog multiple times. I also went into the backup and restore GUI and took a look at some of our catalog backups and they all seem to get the list of files you were talking about under /usr/openv (db, netbackup, var, volmgr). Under /volmgr/database I see the following .devices_ready globDB ltidevs poolDB robotic_def ruleDB volDB I don't know if it makes any difference but we don't backup up anything to tape (all backups go to Data Domain restorers). The one time we did try a DR exercise from tape we couldn't get the catalog restore to work. That helped put together a pretty convincing business case to move to disk based backups and we've been 100% successful every time since then !! Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of judy_hinchcli...@administaff.com Sent: Wednesday, July 22, 2009 5:41 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Netbackup 6.5 Catalog backup - Issue??? I just checked by catalog tape ( I always do fulls) And I do find /usr/openv/netbackup/db on the tape listing class and images and other items. So I checked the catalog config and see in the file list that I specify the catalog to backup that dir. My list Master:/usr/openv/netbackup/db Master:/usr/openv/volmgr/database Master:/usr/openv/var Media:/usr/openv/netbackup/db Media:/usr/openv/volmgr/database Media:/usr/openv/var Master:NETBACKUP_RELEATIONL_DATABASE_FILES What is in your list? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dennis Peacock Sent: Wednesday, July 22, 2009 5:04 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Netbackup 6.5 Catalog backup - Issue??? We are running Solaris 10 boxes, Netbackup 6.5.3.1 1 master server 4 media servers SL8500 tape library with T10Kb drives Just got back from a Disaster Recovery Exercise at Sungard in Philly. What we discovered is: Full Catalog backup does NOT backup /usr/openv/db but DOES backup /usr/openv/netbackup, /usr/openv/var, /usr/openv/volmgr. Differential/Incremental Catalog backup DOES backup the following: /usr/openv/db /usr/openv/netbackup /usr/openv/var /usr/openv/volmgr The difference is the FULL backup misses the /usr/openv/db directory and it's files, while the DIFF/INCR does backup the /usr/openv/db directory. So what's the big deal? In a DR Exercise, you normally bring your FULL catalog backup with you and recover the catalog from that FULL. What it does NOT put back are the Media Pools that are outside the Netbackup default media pools. This means that once your recovery of the catalog is done? You have nothing but the standard default media pools and not your production media pools for your backups and any RMAN backups. Anybody seen this or know if I'm just off my rocker or is Netbackup really missing part of the catalog for DR Recovery? Inquiring minds want to know. +-- |This was sent by dpe...@acxiom.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
[Veritas-bu] modify backup_exit_notify.sh script
My shell scripting is shaky at best so I'm hoping that one of you may be able to help me out. I'm wondering how I would go about editing the /usr/openv/netbackup/bin/backup_exit_notify.sh script so that it doesn't inform me via email of successfully completed backups. Basically I'm only interested in backups that complete with a 1 or higher. I have modified our bp.conf to keep 3 months of jobs in the activity monitor so will be able to check here for successful backups. I really only need to be informed if a backup has failed. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Keeping more job history in the Activity Monitor
Does anyone know how to keep more job history in the activity monitor in 6.5.3 ? I've looked through the settings of the master server and can't find anything that jumps out at me. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Can you reassure my understanding.
We tested this and you are right that you will likely run into problems doing an entire system restore via netbackup. Even with the best will in the world, there is bound to be some kind of configuration file which will mess things up on the running system during the restore. Will the servers at site 2 be the same architecture / patch level / NICS etc ? Unless you have everything 100% the same you'll run into snags. Also... make sure that when you lay the data down you don't lay down the Netbackup files or you'll hose your restore (as we found out !!). If the servers will have identical names and IP's etc... why not just build them as if they were the servers in your home data center but with duplicate (but empty) file systems. In a DR situation all you'd need to restore would be your data files into those empty filesystems. The OS stuff would be as if they were your servers in your home data center. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of John Nardello Sent: Tuesday, June 02, 2009 1:37 PM To: dave.mark...@fjserv.net; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Can you reassure my understanding. Most servers get really ticked off if you try to overwrite the running OS files - assuming they'll let you do it at all. Probably because an overwrite is effectively a delete and then create. So great, what happens when you restore that critical library file that Solaris was using to run ? Or heck, when you restore bpbkar ? Or inetd ? If the CSA guy refuses to back down though, no sweat, ask for a proof of concept test. Let's see what really happens when we do it this way. If only because it ought to be fun to see exactly how messed up the destination server gets. =) And don't sign off on it as the full DR method until you get one. Bare metal restores != file-level restores. - John Nardello -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dave Markham Sent: Tuesday, June 02, 2009 3:50 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Can you reassure my understanding. Guys i'm after a bit of backup as am perhaps doubting myself now. I'm having a bit of a row with a CSA (solutions architect) at our company. A backup design has been done where 2 sites have Solaris clients configured with the same name and ip, and one site is just disconnected from the network. There is a Netbackup Server 6.5.3 (Windows) which backs up the connected clients from site 1. What they want for a DR test is this :- 1. Disconnect the clients from site1 on the network. 2. Enable the network connections of clients on site2 (with same name and ip of site1 clients) 3. Restore to the running Solaris server through netbackup of a client image taken on site 1. My understanding was you wouldn't ever try and restore a whole system from file system based backups to a running solaris OS. Is that correct still? I also can see all sorts of problems having the client names the same and same ips. Arp tables etc. I'd personally have the client names referenced differently in Netbackup regardless of the hostnames which could be the same? Cheers ___ 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] Flash Backup
Guys, Would this be a good option for backing up a Symantec E-vault environment ? We've tried backing up E-vault through a regular backup and it just shuts down the NBU services as it tries to manage the millions of files in the vault. Thanks in advance, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jim Horalek Sent: Monday, May 11, 2009 12:02 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Flash Backup Its called the Enterprise Client now. Jim -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts Sent: Monday, May 11, 2009 9:28 AM To: Baumann, Kevin Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Flash Backup On Mon, May 11, 2009 at 11:12 AM, Baumann, Kevin kbaum...@akamai.com wrote: Does anyone know where I can download Flash Backup for Netbackup? We have a directory with over 12 million small files in it and support recommended this product... You need to purchase the advanced client (aka the snapshot client). It's not an expensive client but it's tiered based on the size of the client server. The client is installed by default in Windows but the Advanced Client needs to be installed separately for Unix. Make sure you read and follow the installation instructions. There are bunch of caveats but once installed correctly, it works very well. .../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] Backing up multiple Oracle db's from a single host
I don't have anywhere near as many DB's as you but we do backup multiple DB's on a single host. I don't think that restarting a failed job from inside the GUI just restarts a backup on the failed DB. I think that will restart a backup of all the DB's covered by the policy. When we want granularity with regard to DB backups on the same server we have to break them into individual policies which use an RMAN script on the backend to actually run the backup. I tend to just copy the existing catch all policy to a new one and rename a new copy of the RMAN script which it calls to reflect the dayabase it's backing up. For example Solaris_OraTier2 with /usr/openv/netbackup/bin/rman_backup.sh was the setup for the catchall policy. Now I have Solaris_OraTier2_tst11510 calling usr/openv/netbackup/bin/rman_backup_tst11510.sh to backup a specific DB on that host. You'll also need separate /usr/openv/netbackup/bin/rman_oratab files for each backup of a specific DB. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Patrick Sent: Friday, May 01, 2009 4:04 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Backing up multiple Oracle db's from a single host I don't know the answer to your question, but I do have a suggestion. Why not have one script for each DB on the client in addition to the one your using now, and if a DB backup fails run that script from the client? This will keep your policy number down but allow the DBA to re-run individual backups if needed. Just a thought. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of nellis Sent: 30 April 2009 22:23 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Backing up multiple Oracle db's from a single host Hello everyone, first I'll go ahead and apologize for such a long post. I'd like to ask everyone; what works best for those of you backing up multiple Oracle db's from a single host. I have several Oracle 10g servers I backup. Each has anywhere from 1 to 20 db instances. I use a single policy and a common path script name to backup the Oracle servers. This for me keeps the number of policies I have to manage down to a minimum. Our dba's have asked for one policy to be setup per DB. The reasoning behind this is that they want the flexibility to restart a failed backup without the restart initiating a backup of all DB's on servers. I told them that what they should be doing on failed DB backups is from the activity monitor, right click on the failed Job ID and select restart. Here is where my lack of in depth knowledge of how NBU works with the Oracle RMAN API when a single stream fails. They asked, how does NBU know to just restart the backup for the DB that failed? The best high level reply I could come up with was that NBU tracks which DB piece it's backing up in a log and when a restart is initiated, it's able to request a backup of just the DB which that piece was associated with via calls to the Oracle RMAN API. In other words, restarting a single failed Jod ID from activity monitor for a backup stream associated with an Oracle backup does not mean that NBU looks at the policy and executes the backup script specified in the backup selection for all servers or just one server which is a member of that policy. Am I wrong? How does a restart work with Oracle? How do you backup Oracle servers which host multiple instances? What are the advantages and disadvantages if any with one policy per instance? Having a policy for each to me sounds like a nightmare in more than one way but I'd REALLY appreciate anyone's input here. Thanks in advance to everyone that replies! +-- |This was sent by norman_el...@discovery.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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup Master server hardware - Solaris
Our NBU master used to be on a Sun SPARC V490 running Solaris 9. Very solid but also pretty costly. When we found a better use for the V490 we looked around and finally settled with an HP DL385G2 running Solaris 10 x86 with 4GB of memory. The server is actually faster than the older SPARC box and we haven't had any reliability issues. We did manage to get the same HP box to run NBU on Linux using Fedora core but this was not an approved configuration and gave us no end of trouble. When Veritas finally approved configurations running Solaris on X86 we jumped on it and haven't looked back since !! Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of judy_hinchcli...@administaff.com Sent: Wednesday, April 22, 2009 11:16 AM To: adam.mel...@woodside.com.au; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Netbackup Master server hardware - Solaris I have had both windows and AIX masters. I like AIX better (could be some favoritism here as I am an AIX admin), I boot the server less often. Had to boot the windows master a little more then I liked. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mellor, Adam A. Sent: Tuesday, April 21, 2009 11:12 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Netbackup Master server hardware - Solaris good morning, I am Interested in asking the community thier opinions for what hardware platform works best for master only netbackup servers. We currently are running our master in a master media configuration (with two additional media servers) and it is time to refresh the master server hardware. I am going to be performing some tests to benchmark some of the hardware we may use for a replacement master only server. for this i am also interested in some of the tests i can run to give an indication of the server performance. I was thinking of restoing the catalogue to the test hardware and timing some of the more intensive commands such as bpimmedia and bplist. does anybody have other or perhaps even better suggestions ?. I'll post results as i complete tests tests if anybody is interested. At the moment it looks like i'll get to test the Sun M300, T5220 and one of the new Intel Nehalem systems. Thanks Adam M. NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Jumping back into the NBU pool
Our NBU master is a HP DL385 G2 and our main media server is an HP DL380 G5, both running Solaris 10 and NBU 6.5.1 We used to run our master and media servers on Sun hardware but for the price, these HP's absolutely scream. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Schaefer, Harry Sent: Friday, March 27, 2009 7:43 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Jumping back into the NBU pool I have not been a NBU engineer for about 3 years, but may be getting back into the mix soon with a small but useful setup. We have about 12 Solaris 3-4 Win2003 servers we need backed up that are on an isolated network. They will have pretty slender policies which will not require a whole lot of index space. Probably something like 1-2 full's a week with incrementals in between and 2-3 week retention. Anyway, looking for some suggestions on a master/media spec that could handle this. Along with that client load, there will probably be SAN attached disk and a pair of LTO4 tape drives. I don't have experience in small environments and I don't want to overkill it. Any ideas would be welcome. :-) Harry S. Atlanta ___ 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] Jumping back into the NBU pool
Nope... Solaris 10 x86 Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: Jeff Lightner [mailto:jlight...@water.com] Sent: Friday, March 27, 2009 9:50 AM To: Mark Glazerman; Schaefer, Harry; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: RE: [Veritas-bu] Jumping back into the NBU pool By Solaris do you mean OpenSolaris? These are Intel boxes. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Friday, March 27, 2009 10:34 AM To: Schaefer, Harry; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Jumping back into the NBU pool Our NBU master is a HP DL385 G2 and our main media server is an HP DL380 G5, both running Solaris 10 and NBU 6.5.1 We used to run our master and media servers on Sun hardware but for the price, these HP's absolutely scream. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Schaefer, Harry Sent: Friday, March 27, 2009 7:43 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Jumping back into the NBU pool I have not been a NBU engineer for about 3 years, but may be getting back into the mix soon with a small but useful setup. We have about 12 Solaris 3-4 Win2003 servers we need backed up that are on an isolated network. They will have pretty slender policies which will not require a whole lot of index space. Probably something like 1-2 full's a week with incrementals in between and 2-3 week retention. Anyway, looking for some suggestions on a master/media spec that could handle this. Along with that client load, there will probably be SAN attached disk and a pair of LTO4 tape drives. I don't have experience in small environments and I don't want to overkill it. Any ideas would be welcome. :-) Harry S. Atlanta ___ 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 Please consider our environment before printing this e-mail or attachments. -- 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] Clean up disk space on Data Domain
We had an issue where we were almost maxed out on one of our Data Domain appliances. We went about it in two ways. We went into NBU and expired images via NBU that we knew should have been expired already. Our issue came about after an NBU upgrade when the catalog lost track of a large number of backup images. Because of this problem, even after expiring images inside NBU, we still had images on the Data Domain that we didn't need any more. To fix this we just mounted the Data Domain's backup directory on one of our unix boxes and manually deleted the images from inside the Data Domain itself. I wouldn't advise doing this unless you are 100% sure you know what you're doing but it worked well for us. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Randy Doering Sent: Wednesday, March 18, 2009 12:55 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Clean up disk space on Data Domain What we do when space gets tight on our DataDomain is to identify Images that are soon to expire within NBU. Go ahead and pre-expire them, then afterwards kick off a clean. In our case, we use VTL and pre-expire the volumes that are soon to expire (we have 3 month retention), go out to the DD and vtl export/vtl tape del; followed by a vtl tape add/vtl import. Randy From: dmehta netbackup-fo...@backupcentral.com To: VERITAS-BU@mailman.eng.auburn.edu Sent: Wednesday, March 18, 2009 12:54:43 PM Subject: [Veritas-bu] Clean up disk space on Data Domain Hi, We are using NBU 6.5.3 and all our backups are going to Data Domain. One of our backend disk is at 100% and we want to get some space back. However we do not know how can we get it faster other than running the clean process of DD, even after which we will be getting 265 GB space. Any help would be appreciated. Thanks, Dushyant Mehta +-- |This was sent by dushyant_me...@symantec.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
Re: [Veritas-bu] how to copy backupsfromdatadomaintotapew/netbackup6.5
That is indeed correct... in the summer of 2008 we were quoted $12,500 per year for an OST license on a DD560 plus an extra $2800 for 1 year of platinum support. You need a license per restorer so we would have needed 2. At the time I understood that it was of more use for folks still vaulting data to tape from the DD's. I understand that when combined with the new DDOS release, OST now provides considerable performance improvements with regard to throughput. We may revisit the idea if the prices have changed. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jeff Lightner Sent: Wednesday, March 11, 2009 8:33 AM To: Hickman, Tony; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] how to copy backupsfromdatadomaintotapew/netbackup6.5 OST apparently costs $$$ -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Hickman, Tony Sent: Wednesday, March 11, 2009 9:02 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] how to copy backups fromdatadomaintotapew/netbackup6.5 There has been a great deal of what looks to be valuable information tossed about on here. I am very glad I posted my original concerns to this mail list. I was out of the office yesterday so I will most likely dedicate my day to decifering some of this information and following up on my problem. Whenever I do get this resolved I will gladly let the list know what steps I have used. Thank you all for your time and responses. B/R, Tony H. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of smpt Sent: Tuesday, March 10, 2009 5:49 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] how to copy backups from datadomaintotapew/netbackup6.5 From what I know, quantum DXi7500 has an option path to tape and sends the data to the tapes from fiber channel. I will implement it to a customer within the next month. Also with the latest firmware, DXi7500 use OST to replicate to another DXi7500 and netbackup is aware of the replication. I don't know if this is over fiber of ip, but the direct duplication to tapes is over fiber stefanos -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of cpreston Sent: Tuesday, March 10, 2009 4:41 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] how to copy backups from data domaintotapew/netbackup6.5 Wilkinson, Alex wrote: What is an OST interface ? The OpenSTorage interface, a new way to use your Data Domain boxes (and other boxes that support it) with NetBackup. It's not NFS or CIFS, it is its own transport. It is also not VTL. Think of it as a more intelligent DSU. In the case of DD Quantum, the data is sent over IP. With Falconstor, the data is sent over Fibre Channel. With DD boxes (which is what started this conversation), the first improvement you'll get simply by switching from NFS/CIFS to OST is a significant increase in performance. With all systems that support OST, you also get what NBU calls optimized deduplication, where NBU tells one OST device to copy a given backup to another OST device. The OST device (in this case, the DD box) will use dedupe and replication to get the data there. Once there, it informs NBU. Now NBU knows about both copies, just as if it had duplicated it via bpduplicate. Nice, huh? The nice thing that OST is supposed to support is tape-out functionality, where an OST device can copy it's backup to tapes and tell NBU which tapes got which backups. Again, just as if it NBU did the copy. Here's my blog post about OST: http://www.backupcentral.com/content/view/198/47/ +-- |This was sent by wcplis...@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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended
Re: [Veritas-bu] NBU 6.5.1 restores miss files
Travis, Sorry for missing out that detail. We initiated all of our restores through the GUI. I just took a look at the tech note you mentioned and was certainly interested at what it talked about. This would certainly explain our issue. However, I followed the steps to see if there was a similar mismatch in our production environment. I chose a directory with 8 files in it and initiated a restore of those files to a different test directory on the same server. All 8 files were restored. I don't know if the problem mentioned in the tech note happens with EVERY restore or just randomly but this very limited test seems to imply that we don't have that problem here. Thanks, Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: Travis Kelley [mailto:travis.kel...@etrade.com] Sent: Tuesday, January 20, 2009 8:04 AM To: Mark Glazerman Cc: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU 6.5.1 restores miss files You didn't mention how your performed the restore. Bob already suggested using the command line. In case you are using the java admin gui I'll point you over to a technote showing a problem we had where files weren't restored. I believe this only applies if you are using the java admin gui. http://seer.entsupport.symantec.com/docs/313460.htm Mark Glazerman wrote: Len, Thanks for your interest in our issue… - When you say that all your backup data resides on 2 Data Domain storage devices, I assume you mean just the backup media , tape or disk pool, and not the disk unit holding the restored data? All backup data created by netbackup is sent straight to one of 2 DataDomain restorers in our home data center. That data is then replicated to identical DataDomain appliances in our DR hosting site in Philadelphia. All of the images that we restore during either a DR exercise or a regular recovery of some kind come from the DataDomain appliances. The DataDomain appliances are not used for primary storage or as target for any restored data. All data was being restored to SAN attached disk on each host. - Did Netbackup report a failure to restore files? If so what reason was it reporting. NetBackup did not report any errors during the restores. Our signal that files / data was missing was that after restoring what we believed to be entire mountpoints, we would be short when compared to the amount of data in our production environments, sometimes by up to 10GB. - You talk about finding that missing files were found after the servers were turned over to your DBA’s. Do you mean missing files showed up without doing a restore? If so what file systems were you using? Windows 2003 ntfs, solaris zfs, Linux ext3? Local disk or remote? I didn’t word this very well. While it was obvious data was missing if we were GB’s short, some files or binaries needed by our DBA’s for RMAN recoveries etc.. were not seen to be missing until they were unable to do what they needed to. The files didn’t show up on their own, their absence was identified after the data restores had apparently completed successfully. This was almost exclusively an issue with data being restored to unix boxes into both VxFS and ZFS file systems on SAN attached disk - So are you talking about a failure of Netbackup or server/filesystems or both? I don’t think we’re talking of a failure of the filesystems and NetBackup didn’t fail completely. Once a file or directory was identified as missing after a restore, we would always drill down in Netbackup to make sure that the file was actually there to be restored. They always were and were which means that NetBackup is working from a backup point of view. We were then able to successfully restore these specific files or directories if we drilled down to the specific file or sub directory. In that respect, NBU didn’t fail from a restore point of view either because we were able to restore everything we wanted to, just not always the first time around !! It is indeed an interesting problem and thankfully was one that we were able to work around. I haven’t raised this question with veritas yet but plan to do so if some more testing in our home data center generates similar results. *Mark Glazerman* Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to *From:* Len Boyle [mailto:len.bo...@sas.com] *Sent:* Monday, January 19, 2009 2:47 PM *To:* Mark Glazerman; Veritas-bu@mailman.eng.auburn.edu *Subject:* RE: NBU 6.5.1 restores miss files Hello Mark, I have a few questions about your report. - When you say that all your backup data resides on 2 Data Domain storage devices, I assume you mean just the backup media , tape
[Veritas-bu] NBU 6.5.1 restores miss files
I've just got back to the office after a 24 DR test and wanted to get this question out there before I forget. We found during our testing that even if an entire directory tree was selected to be restored, after the restore finished we would be missing random files and directories. Re-running the restore with the same parameters would almost always lay down additional data which should have been restored the first time around. Once we turned these servers over to our DBA's to run their RMAN restores, we spent several hours completing additional requests for individual files to be restored which had been missed earlier on. When we would drill down to check that these files existed we always found that they were there. For reference, all of our backup data resides on 2 Data Domain storage devices so it isn't an issue with missing media. Has anyone else seen anything like this ? Thanks, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU 6.5.1 restores miss files
Len, Thanks for your interest in our issue... - When you say that all your backup data resides on 2 Data Domain storage devices, I assume you mean just the backup media , tape or disk pool, and not the disk unit holding the restored data? All backup data created by netbackup is sent straight to one of 2 DataDomain restorers in our home data center. That data is then replicated to identical DataDomain appliances in our DR hosting site in Philadelphia. All of the images that we restore during either a DR exercise or a regular recovery of some kind come from the DataDomain appliances. The DataDomain appliances are not used for primary storage or as target for any restored data. All data was being restored to SAN attached disk on each host. - Did Netbackup report a failure to restore files? If so what reason was it reporting. NetBackup did not report any errors during the restores. Our signal that files / data was missing was that after restoring what we believed to be entire mountpoints, we would be short when compared to the amount of data in our production environments, sometimes by up to 10GB. - You talk about finding that missing files were found after the servers were turned over to your DBA's. Do you mean missing files showed up without doing a restore? If so what file systems were you using? Windows 2003 ntfs, solaris zfs, Linux ext3? Local disk or remote? I didn't word this very well. While it was obvious data was missing if we were GB's short, some files or binaries needed by our DBA's for RMAN recoveries etc.. were not seen to be missing until they were unable to do what they needed to. The files didn't show up on their own, their absence was identified after the data restores had apparently completed successfully. This was almost exclusively an issue with data being restored to unix boxes into both VxFS and ZFS file systems on SAN attached disk - So are you talking about a failure of Netbackup or server/filesystems or both? I don't think we're talking of a failure of the filesystems and NetBackup didn't fail completely. Once a file or directory was identified as missing after a restore, we would always drill down in Netbackup to make sure that the file was actually there to be restored. They always were and were which means that NetBackup is working from a backup point of view. We were then able to successfully restore these specific files or directories if we drilled down to the specific file or sub directory. In that respect, NBU didn't fail from a restore point of view either because we were able to restore everything we wanted to, just not always the first time around !! It is indeed an interesting problem and thankfully was one that we were able to work around. I haven't raised this question with veritas yet but plan to do so if some more testing in our home data center generates similar results. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Len Boyle [mailto:len.bo...@sas.com] Sent: Monday, January 19, 2009 2:47 PM To: Mark Glazerman; Veritas-bu@mailman.eng.auburn.edu Subject: RE: NBU 6.5.1 restores miss files Hello Mark, I have a few questions about your report. - When you say that all your backup data resides on 2 Data Domain storage devices, I assume you mean just the backup media , tape or disk pool, and not the disk unit holding the restored data? - Did Netbackup report a failure to restore files? If so what reason was it reporting. - You talk about finding that missing files were found after the servers were turned over to your DBA's. Do you mean missing files showed up without doing a restore? If so what file systems were you using? Windows 2003 ntfs, solaris zfs, Linux ext3? Local disk or remote? - So are you talking about a failure of Netbackup or server/filesystems or both? A very interesting problem. Thanks len From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark Glazerman Sent: Monday, January 19, 2009 3:03 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU 6.5.1 restores miss files I've just got back to the office after a 24 DR test and wanted to get this question out there before I forget. We found during our testing that even if an entire directory tree was selected to be restored, after the restore finished we would be missing random files and directories. Re-running the restore with the same parameters would almost always lay down additional data which should have been restored the first time around. Once we turned these servers over to our DBA's to run their RMAN restores, we spent several hours completing additional requests for individual files to be restored which had been missed earlier on. When we would drill down to check
Re: [Veritas-bu] RMAN backup status
current'; BACKUP filesperset 20 FORMAT 'al_%s_%p_%t' ARCHIVELOG ALL DELETE INPUT; BACKUP format 'cntrl_%t_%s_p%p' current controlfile; } CROSSCHECK BACKUP; CROSSCHECK ARCHIVELOG ALL; DELETE NOPROMPT EXPIRED BACKUP; DELETE NOPROMPT OBSOLETE; EXIT fi # Initiate the command string if [ $CUSER = root ] then su - $ORACLE_USER -c $CMD_STR $RMAN_LOG_FILE RSTAT=$? else /usr/bin/sh -c $CMD_STR $RMAN_LOG_FILE RSTAT=$? fi # --- # Log the completion of this script. # --- if [ $RSTAT = 0 ] then LOGMSG=ended successfully else LOGMSG=ended in error fi echo $RMAN_LOG_FILE echo Script $0 $RMAN_LOG_FILE echo $LOGMSG on `date` $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo BACKUP ENDED $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo $RMAN_LOG_FILE echo $RMAN_LOG_FILE fi x=x+1 if [ x = 10 ]; then EXIT 0 fi done ### Hope that this is helpful for you. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of nbujohnson Sent: Saturday, January 10, 2009 7:23 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] RMAN backup status Hi All, I am using netbackup-rman template to backup our oracle databases i am need of a script which will give me status report of rman failures (includes client name ,db name date/time error output etc). Please let me know if anyone using any script like this. Thanks, John +-- |This was sent by nbujohn...@googlemail.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
Re: [Veritas-bu] NBU6.5.2a Solaris 10 Hot Catalog backup failing
We periodically get the 227 error and that is often accompanied by an entry in the problem report (search for the master server having the issue) which implies that the catalog policy has exceeded it's maximum number of configured attempts. This will just randomly occur and after that point it won't run a scheduled backup but will let me submit manual catalog backups. It notmally only complains about 1 schedule inside the catalog policy (We have a night and day schedule within the catalog policy). Our fix for this requires the catalog policy to be deleted and then cycling of all the NBU services. Once NBU is back up create a new catalog policy and normally things are fine again. We found that this would normally coincide with our master server getting beat up with regard to CPU and memory so we now have a script which restarts the NBU services on a weekly basis to clear out any old or lingering NBU processes which might be hanging onto resources. Hope this is somewhat helpful. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marianne Van Den Berg Sent: Monday, December 01, 2008 3:16 AM To: Justin Piszcz Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU6.5.2a Solaris 10 Hot Catalog backup failing Looks like we have a resource problem - cpu utilization on master sitting at 100% all the time. Might be a combination of VBR data collection on master and 6.5.2 being more resource intensive... Anybody with similar experience? Regards M. -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: 29 November 2008 23:50 To: Marianne Van Den Berg Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NBU6.5.2a Solaris 10 Hot Catalog backup failing On Sat, 29 Nov 2008, Marianne Van Den Berg wrote: Nope - no entries in critical section. Catalog backups have been working fine after 6.5.2 upgrade (about 3 weeks ago); been failing last 4 days. -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: 29 November 2008 19:26 To: Marianne Van Den Berg Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU6.5.2a Solaris 10 Hot Catalog backup failing On Sat, 29 Nov 2008, Marianne Van Den Berg wrote: Hi All Clustered NBU 6.5.2a master server (with EEB's) on Solaris 10. Tcp_fusion disabled. Hot Catalog backups (the last stream backing up the images and the parent) have been failing for a couple of days now with all sorts of errors - 50, 41, 25, 227. This particular stream failed with 41 after backing up 41Gb: Error bpbrm (pid=26181) db_FLISTsend failed: network connection timed out (41). Master server is doing network backup to media server (also on 6.5.2). Has anybody seen this? Ideas? Advise? Do you have policies in the critical section of the catalog backup policy? Justin. Next step I would perform is to verify your catalog (bpdbm) check consistency 2 and look for any bad images. Justin. ___ 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] Data Domain vs Quantum DXi
http://finance.google.com/finance?client=obq=NYSE:QTM I have $1… I’ll take 3 shares and my change please. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of oersted Sent: Friday, November 07, 2008 2:11 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Data Domain vs Quantum DXi if you can wait a little while , there will be some interesting solutions in this arena soon. Robin Small wrote: Thanks to the folks that commented on EMC's Avamar, it was helpful. I'm curious now about DataDomain Quantum DXi. We run XioTech SANs and they're bundling a DD960(something) head on to the XioTech SAN. We're also using ADIC (now Quantum) for our Tape hardware. So those two bubbled up to the top. I'm meeting with our Quantum sales engineer guys on Monday to talk about it, and I was watching a DD/XioTech webinar about their offering that looks cool. Both look appealing. I'm curious for the dedup users out there what your experience has been with either DD or Quantum. I've been poking through Curtis' blogs about the subject, so I get it that the Quantum can do either inline or post, and the DD is pure inline. My RPO isn't as critical (most of my users are happy with the prior night's data), so PostProcessing isn't a game-changer. Thanks, ~ Robin +-- |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
Re: [Veritas-bu] Data Domain vs Quantum DXi
That’s why we've been using Data Domain for over 2 years and couldn't be happier with the product. I have to confess to not knowing a huge amount about Quantum but reading some of the earlier replies, I wonder why anyone would replace tape with a disk based storage unit, only to configure that DSU to act just like a bunch of tape drives. The NFS / CIFS options from DD work very well for our mixed environment (Solaris and Windows) backing up Exchange, Oracle, SQL etc... Anyways.. perhaps my stock comment wasn't too helpful but I can say that we haven't regretted our data domain purchase once in over 2 years. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: Nardello, John [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2008 5:00 PM To: Mark Glazerman Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Data Domain vs Quantum DXi Careful Mark, remember that you get what you pay for. =) - John Nardello -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Glazerman Sent: Friday, November 07, 2008 12:41 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Data Domain vs Quantum DXi http://finance.google.com/finance?client=obq=NYSE:QTM I have $1... I'll take 3 shares and my change please. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of oersted Sent: Friday, November 07, 2008 2:11 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Data Domain vs Quantum DXi if you can wait a little while , there will be some interesting solutions in this arena soon. Robin Small wrote: Thanks to the folks that commented on EMC's Avamar, it was helpful. I'm curious now about DataDomain Quantum DXi. We run XioTech SANs and they're bundling a DD960(something) head on to the XioTech SAN. We're also using ADIC (now Quantum) for our Tape hardware. So those two bubbled up to the top. I'm meeting with our Quantum sales engineer guys on Monday to talk about it, and I was watching a DD/XioTech webinar about their offering that looks cool. Both look appealing. I'm curious for the dedup users out there what your experience has been with either DD or Quantum. I've been poking through Curtis' blogs about the subject, so I get it that the Quantum can do either inline or post, and the DD is pure inline. My RPO isn't as critical (most of my users are happy with the prior night's data), so PostProcessing isn't a game-changer. Thanks, ~ Robin +-- |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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] / + Cross All Mnt Pts Vs. ALL_LOCAL_DRIVES
Nathan, We use ALL_LOCAL_DRIVES with the allow multiple streams and it works well for both backups and restores. Because our databases are backed up using RMAN we exclude database related files during OS backups as we know we'll get the required database files during their own backups. One note of caution regarding the use of ALL_LOCAL_DRIVES if you are using ZFS on your unix clients and NBU 6..5 or 6.5.1 though. We found out (luckily) that in 6.5 and 6.5.1 they removed the ability for NBU to back up ZFS file systems using ALL_LOCAL_DRIVES as the backup selection. Our root filesystems (on UFS) would back up just fine but it would ignore the ZFS file systems. This was fixed by an engineering binary in 6.5.1 and I believe has been addressed in later versions (6.5.2 onwards !!). Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Kippen Sent: Tuesday, October 21, 2008 4:25 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] / + Cross All Mnt Pts Vs. ALL_LOCAL_DRIVES I'm just looking to see what the recommendation out there is for backing up unix-based servers. In the past I've always backed up a unix client using / in my selection list and using cross all mount points + exclude lists. As I was browsing through the Admin guide I read that ALL_LOCAL_DRIVES could be used on unix-based clients as well. I'm interested to know how people out there backup their unix clients. We use cross all mount points so to make sure that an Admin doesn't create something on a client that needs to be backed up that he doesn't tell us [backup admins] about. I'm looking into using the ALL_LOCAL_DRIVES directive with allow multiple streams so I can stream out my unix clients by filesystem thus getting more i/o throughput by having the backups read from multiple physical disks at the same time. ... This opposed to using / + NEW_STREAM .. since I don't really know what directories are actual filesystems. (I don't admin the majority of the clients I backup.) Thanks, ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Process which runs while a job is running
I am wanting to write a script to place in the crontab of our master server which will restart the NBU services once a week. I plan to have the script issue nbpemreq -suspend_scheduling but then need a way for it to check for any backups still running before issuing /etc/init.d/netbackup stop. Does anyone know if there is a process I can have the script grep for which won't be there once all the backups have completed ? I don't want to stop the NBU processes if there are backups still running. We do plan to have the script run during a period when no backups are running but we all know how backups can randomly overrun their expected windows !! In case anyone is curious, our master server has some kind of semi regular memory issue which arises about once every 10 days or so and can be resolved by restarting the NBU services. My plan is to proactively do this on a weekly basis in the hope that it will stop the master server rejecting connections due to a lack of swap (like it did last night during my daughters softball game !!). Thanks Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Process which runs while a job is running
Thanks for all your responses.
After a bit of help from our resident scripting expert I've come up with
the following and thought I would share in case anyone else needs to
restart NBU on a regular basis.
#!/usr/bin/ksh
## This script restarts NetBackup Once A Week To Try And Avoid The
Master Server Crashing ##
#
nbpemreq -suspend_scheduling
t_p=`bpdbjobs -summary | egrep nbumaster01 | grep -v grep | awk '{print
$4}'`
while [t_p -ne 0]
do
t_p=`bpdbjobs -summary | egrep nbumaster01 | grep -v grep | awk '{print
$4}'`
sleep 10
done
/etc/init.d/netbackup stop
echo NetBackup services have been stopped | mailx -s NetBackup
services have been stopped [EMAIL PROTECTED]
sleep 120
/etc/init.d/netbackup start
echo NetBackup services have been restarted | mailx -s NetBackup
services have been restarted [EMAIL PROTECTED]
I'm going to run it as a cron job at 2pm every Sunday.
Thanks again,
Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
P please don't print this e-mail unless you really need to
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Glazerman
Sent: Friday, September 19, 2008 8:20 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Process which runs while a job is running
I am wanting to write a script to place in the crontab of our master
server which will restart the NBU services once a week. I plan to have
the script issue nbpemreq -suspend_scheduling but then need a way for it
to check for any backups still running before issuing
/etc/init.d/netbackup stop.
Does anyone know if there is a process I can have the script grep for
which won't be there once all the backups have completed ? I don't want
to stop the NBU processes if there are backups still running. We do
plan to have the script run during a period when no backups are running
but we all know how backups can randomly overrun their expected windows
!!
In case anyone is curious, our master server has some kind of semi
regular memory issue which arises about once every 10 days or so and can
be resolved by restarting the NBU services. My plan is to proactively
do this on a weekly basis in the hope that it will stop the master
server rejecting connections due to a lack of swap (like it did last
night during my daughters softball game !!).
Thanks
Mark Glazerman
Enterprise Storage Administrator
Spartech Corporation
Desk: 314-889-8282
Fax: 314-854-8282
Cell: 618-520-3401
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
http://www.spartech.com http://www.spartech.com/
P please don't print this e-mail unless you really need to
This e-mail and any files transmitted with it are confidential, are
intended solely for the use of the addressee, and may be legally
privileged. If you have received this email in error please notify the
sender immediately, and do not copy or forward it.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Process which runs while a job is running
Jeff,
When I tested the script on our master server it didn't send out the
notification that the services had been stopped until all the NBU
services had been brought down. I know that when our server gets hung
up it can take a while to get the services stopped and sometimes I have
to use bp.kill_all to get everything to shut down. However, as the
script appears to wait until everything is down before starting
everything up again, it looks like I don't have to overcomplicate my
script (or overtax my brain on a Friday !!).
Thanks
Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
P please don't print this e-mail unless you really need to
From: Jeff Lightner [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2008 10:33 AM
To: Mark Glazerman; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Process which runs while a job is running
You might want to put in a loop after the stop that checks to see if all
processes are actually stopped (e.g. check bpps -a output) and run
installdir/ bin/goodies/bp.kill_all to kill any remaining if it finds
them and repeat until it does (with sleeps between to give all processes
time to die). You may need to put in a routine to make it page you
(send email to your cell phone if you don't have a pager) if all
processes haven't died after a certain number of attempts.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Glazerman
Sent: Friday, September 19, 2008 11:15 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Process which runs while a job is running
Thanks for all your responses.
After a bit of help from our resident scripting expert I've come up with
the following and thought I would share in case anyone else needs to
restart NBU on a regular basis.
#!/usr/bin/ksh
## This script restarts NetBackup Once A Week To Try And Avoid The
Master Server Crashing ##
#
nbpemreq -suspend_scheduling
t_p=`bpdbjobs -summary | egrep nbumaster01 | grep -v grep | awk '{print
$4}'`
while [t_p -ne 0]
do
t_p=`bpdbjobs -summary | egrep nbumaster01 | grep -v grep | awk '{print
$4}'`
sleep 10
done
/etc/init.d/netbackup stop
echo NetBackup services have been stopped | mailx -s NetBackup
services have been stopped [EMAIL PROTECTED]
sleep 120
/etc/init.d/netbackup start
echo NetBackup services have been restarted | mailx -s NetBackup
services have been restarted [EMAIL PROTECTED]
I'm going to run it as a cron job at 2pm every Sunday.
Thanks again,
Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
P please don't print this e-mail unless you really need to
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Glazerman
Sent: Friday, September 19, 2008 8:20 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Process which runs while a job is running
I am wanting to write a script to place in the crontab of our master
server which will restart the NBU services once a week. I plan to have
the script issue nbpemreq -suspend_scheduling but then need a way for it
to check for any backups still running before issuing
/etc/init.d/netbackup stop.
Does anyone know if there is a process I can have the script grep for
which won't be there once all the backups have completed ? I don't want
to stop the NBU processes if there are backups still running. We do
plan to have the script run during a period when no backups are running
but we all know how backups can randomly overrun their expected windows
!!
In case anyone is curious, our master server has some kind of semi
regular memory issue which arises about once every 10 days or so and can
be resolved by restarting the NBU services. My plan is to proactively
do this on a weekly basis in the hope that it will stop the master
server rejecting connections due to a lack of swap (like it did last
night during my daughters softball game !!).
Thanks
Mark Glazerman
Enterprise Storage Administrator
Spartech Corporation
Desk: 314-889-8282
Fax: 314-854-8282
Cell: 618-520-3401
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
http://www.spartech.com http://www.spartech.com/
P please don't print this e-mail unless you really need to
This e-mail and any files transmitted with it are confidential, are
intended solely for the use of the addressee, and may be legally
privileged. If you have received this email in error please notify the
sender immediately, and do not copy or forward it.
--
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
[Veritas-bu] Recommended patches for Sol 10 x86 master server
Ladies and Gents, Does anyone know if a list exists that details all the recommended OS patches for a Solaris 10 x86 (s10x_U5wos_10 x86) master server running NBU 6.5.1 ? We're getting some occasional errors which we're thinking might be down to missing OS patches but I don't know where to start looking at what we might be missing. Thanks in advance. Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Most recent stable release?
We're running 6.5.1 on a Solaris x86 master and apart from a ZFS issue (which was fixed with engineering binaries) we don't have any ongoing problems. 6.5.2 and 6.5.2a seem to be releases that fixe lots of issues for some and create additional problems for others. Mark J Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, August 21, 2008 6:46 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? On Thu, Aug 21, 2008 at 6:04 AM, [EMAIL PROTECTED] wrote: Watch out for this one with 6.5.1 on Windows: http://seer.entsupport.symantec.com/docs/301175.htm The technote says that this is fixed in 6.5.2. Right now I'm caught between that one and the completely broken 6.5.2A - http://seer.entsupport.symantec.com/docs/305609.htm The technote says that there's an EEB available for this. 6.5.2A is *NOT completely broken. Many years, us included, are running it in full production. You'd think they'd test this stuff before release by ,say, trying to run a backup or something... This has been discussed before. Your comment is unwarranted and low shots like this don't encourage Symantec employees or other users to help you. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Mount Points and Jobs
I just talked to my windows admin and we're pretty sure that adding specific paths to your backup selections should add additional streams to your backup. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of sauderd Sent: Friday, August 15, 2008 10:35 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Mount Points and Jobs When backing up Unix servers, allowing multiple data streams will cause Netbackup's stream discovery to create one job for each mounted filesystem. However on Windows, it creates one job for each drive letter, regardless of the number of mounted filesystems beneath each drive letter. We are creating separate filesystems and mount points on Windows precisely because it breaks backups into smaller, more managable jobs. Does anyone know a way to get Netbackup's stream discovery to create one job for each mounted filesystem on Windows? (i.e. more granular than one job per drive letter) If that's not possible, I'm considering ways to do my own stream discovery via scripts and kick off one job per filesystem myself (and turning off the Cross Mount Points option). Anyone have experience with that approach? (I'm already aware of mountvol.) +-- |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
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
Ed, As Phil and myself have proved, there are backup admins out there who have no idea that their ZFS filesystem data is unprotected. Not everyone has the opportunity to test restores and it's only through sheer luck that we'd been given a server to use as a test box about a week before I made my discovery. I agree 100% that as a matter of urgency, Symantec should have distributed the technote much earlier than they did once they identified this issue. I hope that there were not too many other admins who had to go through the same stages of disbelief that we did when faced with backups that never errored out but also didn't actually back up any data !! The potential levels of exposure for NBU customers worldwide is mind boggling and really shouldn't have ever happened. I am just thankful that some of the Symantec engineering team also subscribe to this mailing list and that they were able to make a fix available so quickly. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Friday, August 08, 2008 6:49 AM To: Weber, Philip Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks On Fri, Aug 8, 2008 at 3:16 AM, Weber, Philip [EMAIL PROTECTED] wrote: Thanks for highlighting this problem to the list, as we for one hadn't even picked up that our zfs filesystems were no longer backing up. We now have the engineering binaries, and our account manager at Symantec has kindly chased up the TechAlert which should have been issued. I had a meeting earlier this week with NetBackup engineers followed by some managers. I raised the issue of technotes being released too late and used this as an example. The fix is already in 6.5.2 which has been out for a couple of months. In my opinion, the technote should have been released when the bug was acknowledged by engineering - not a couple of months after the fix is out. Symantec gave customers like you no warning that NetBackup was silently failing to back up data when your policies were configured correctly. They knew your data was not being backed up. They knew that unless you went out and manually verified each mount point that there was no way for you to know that the data was no longer being backed up. They chose not to tell you. That's simply irresponsible. They heard my message. Whether or not they act on it is now up to them. You may want to ask your account manager to suggest to product management that these technotes be issued in a more timely fashion - the more pressure on them, the better. I suspect that there's a few political battles to be fought internally over this .../Ed ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] ZFS backup problems
This isn't really a patch. It's more of an admittance of guilt from Symantec that they broke something in 6.5 which was working as far back as 5.1. I won't be following them blindly down the 6.5.2 path. Our workaround will work fine until the next big release. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of tsufan Sent: Wednesday, August 06, 2008 11:17 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] ZFS backup problems I believe Symantec released a patch on this issue today. http://entsupport.symantec.com/docs/303000 This might help you out. +-- |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
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
Fixed !!... Symantec have outdone themselves (strange to say I know !!). Engineering created two binaries to replace the bpbkar and bpmount files in /usr/openv/netbackup/bin. Once this was done I was able to successfully backup ZFS filesystems on my test box with ALL_LOCAL_DRIVES as the only backup selection. No need to specify all the possible zfs filesystems on all clients in the policy as I had been doing. The real test will come tonight when the policy will try and kick off proper but I'm confident that they've fixed our issue without the need for upgrading everything to 6.5.2 !! Anyone who's had similar issues is advised (by engineering) to contact support and to reference technote 303000 (http://seer.entsupport.symantec.com/docs/303000.htm) and ask to be sent the engineering binaries that ARE available. The binaries appear to work on both 6.5 and 6.5.1 clients (at least they are on our systems). Just thought I'd update everyone on a successful resolution to a very annoying issue. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 please don't print this e-mail unless you really need to -Original Message- From: bob944 [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 3:02 PM To: veritas-bu@mailman.eng.auburn.edu Cc: Mark Glazerman Subject: RE: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks I didn't say that Exclude lists don't work for directories. I said that Include lists don't work for directories. [...] No. Include lists work exactly the same way as exclude lists; directories and/or files are valid. Reference the Veritas NetBackup System Administrator's Guide, Vol I for syntax rules. This misunderstanding might be attributed to way the *_list rules are applied. Note that an exclude list can only exclude items that are in the policy's selection list (obviously). And that an include list can only include items that were excluded by an exclude list. (Perhaps that's the logic in Symantec renaming the include list to exceptions to the exclude list.) Stated another way, the selection list defines the universe of data to be backed up. Excludes subtract from the universe. Includes reinstate only items from the set of excluded items. You can see the processing steps in the client's bpbkar log. Logging level 0 will show each directive as it is encountered; level 1 and higher will show the process more clearly via the PrintFile lines. From that I can infer the reason the rules are as they are (above): bpbkar processes the selection list and only mentions exclude_list items when they match its current path; include_list entries are only mentioned when they match the current exclude_list item. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
Domink, The problem with exclude lists is that if you start having a different exclude list for each server, it quickly becomes a nightmare keeping those lists current and up to date. Also, because ALL_LOCAL_DRIVES doesn't recognize the ZFS filesystems, the only way to have them included was to start listing the mountpoints in the backup selections tab of the policy. We tried looking at include lists also but those only work for individual files, not whole directories. This brought us to our workaround where we had to specify every possible zfs mountpoint in the backup policy and then make sure that each of those directories existed on every server (to avoid the 71's). That has worked like a charm over the weekend so will have to do until there is a release of NBU which includes ZFS under the ALL_LOCAL_DRIVES backup selection Thanks Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 1:17 AM To: Mark Glazerman Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks You couldn't use exclude lists ??? Mark Glazerman [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/08/2008 11:34 PM To Veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Incase anyone is considering implementing any ZFS in their environment which they want to back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the backup selection does NOT cover ZFS filesystems. We have a number of Sun boxes which have various test and development oracle instances which are housed inside ZFS file systems. We blew away one of these test instances the other day (after doing a full OS backup and the required RMAN backups) but when we went to restore the data from the ZFS filesystems, NBU didn't have anything under the uppermost directory. A quick check of other systems with ZFS showed the same issue.We spent the better part of 2 days playing around with the include_list's and exclude_list's but nothing worked. In order to backup ZFS file systems you must explicitly add the ZFS directories into the backup selections of the backup policy. This fix was also confirmed by Symantec support who were also happy to tell me that ZFS isn't officially supported by NBU yet. This on its own should work great if you have a single policy backing up a single server with all it's ZFS under the same parent directory. However, if like us, you have a backup policy which backs up multiple servers, each with their own uniquely named ZFS file systems, you need to get a bit creative. The policy in question backs up 15 Sun boxes with a total of 6 differently named ZFS file systems spread amongst them. If you just list the file systems in the backup selections, NBU looks for each of those different filesystems on each server and spits out an error code 71 (None of the files in the file list exist) for every directory it can't find. The only way we could work out to avoid these errors (and there were a lot of them) was to create every missing directory on every server and then touch a tiny file inside each of these directories. Now when the policy runs, it sees each directory (as listed in the backup selection) on each server and doesn't moan about anything. Perhaps not the neatest of fixes but it works. Apologies for the wordy post, just thought I'd put this info out there in case anyone else is moving towards ZFS. Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu National Australia Bank Ltd - ABN 12 004 044 937 This email may contain confidential information. If you are not the intended recipient, please immediately notify us at [EMAIL PROTECTED] or by replying to the sender, and then destroy all copies of this email. Except where this email indicates otherwise, views expressed in this email are those of the sender and not of National Australia Bank Ltd. Advice in this email does not take account of your objectives, financial situation, or needs. It is important for you to consider these matters and, if the e-mail refers to a product(s), you should read
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
Jeff, I didn't say that Exclude lists don't work for directories. I said that Include lists don't work for directories. We have Exclude lists in place on each server so that the filesystem backups don't back up archive and redo logs which are backed up separately by RMAN. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 8:46 AM To: Mark Glazerman; [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks In general exclude lists work for directories as well as files so I'm not sure why you stated they don't work for the former. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Glazerman Sent: Monday, August 04, 2008 8:53 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Domink, The problem with exclude lists is that if you start having a different exclude list for each server, it quickly becomes a nightmare keeping those lists current and up to date. Also, because ALL_LOCAL_DRIVES doesn't recognize the ZFS filesystems, the only way to have them included was to start listing the mountpoints in the backup selections tab of the policy. We tried looking at include lists also but those only work for individual files, not whole directories. This brought us to our workaround where we had to specify every possible zfs mountpoint in the backup policy and then make sure that each of those directories existed on every server (to avoid the 71's). That has worked like a charm over the weekend so will have to do until there is a release of NBU which includes ZFS under the ALL_LOCAL_DRIVES backup selection Thanks Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 1:17 AM To: Mark Glazerman Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks You couldn't use exclude lists ??? Mark Glazerman [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/08/2008 11:34 PM To Veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Incase anyone is considering implementing any ZFS in their environment which they want to back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the backup selection does NOT cover ZFS filesystems. We have a number of Sun boxes which have various test and development oracle instances which are housed inside ZFS file systems. We blew away one of these test instances the other day (after doing a full OS backup and the required RMAN backups) but when we went to restore the data from the ZFS filesystems, NBU didn't have anything under the uppermost directory. A quick check of other systems with ZFS showed the same issue.We spent the better part of 2 days playing around with the include_list's and exclude_list's but nothing worked. In order to backup ZFS file systems you must explicitly add the ZFS directories into the backup selections of the backup policy. This fix was also confirmed by Symantec support who were also happy to tell me that ZFS isn't officially supported by NBU yet. This on its own should work great if you have a single policy backing up a single server with all it's ZFS under the same parent directory. However, if like us, you have a backup policy which backs up multiple servers, each with their own uniquely named ZFS file systems, you need to get a bit creative. The policy in question backs up 15 Sun boxes with a total of 6 differently named ZFS file systems spread amongst them. If you just list the file systems in the backup selections, NBU looks for each of those different filesystems on each server and spits out an error code 71 (None of the files in the file list exist) for every directory it can't find. The only way we could work out to avoid these errors (and there were a lot of them) was to create every missing directory on every server and then touch a tiny file inside each of these directories. Now when the policy runs, it sees each directory (as listed in the backup selection) on each server and doesn't moan about anything. Perhaps not the neatest of fixes but it works. Apologies for the wordy post, just thought I'd put this info out there in case anyone else is moving towards ZFS. Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential
