Understood. Sorry I couldn't help.
From: Armenti, Joseph [mailto:[email protected]] Sent: Wednesday, September 12, 2012 2:20 PM To: Mark Glazerman; [email protected]; [email protected] 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:[email protected]] Sent: Wednesday, September 12, 2012 3:19 PM To: Armenti, Joseph; [email protected]; [email protected] 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:[email protected]] Sent: Wednesday, September 12, 2012 2:18 PM To: Mark Glazerman; [email protected]; [email protected] 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: [email protected] [mailto:[email protected]] On Behalf Of Mark Glazerman Sent: Wednesday, September 12, 2012 3:15 PM To: [email protected]; [email protected] 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=content&id=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: [email protected] [mailto:[email protected]] On Behalf Of Wayne T Smith Sent: Wednesday, September 12, 2012 2:08 PM To: [email protected] 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 <[email protected]> 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 - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
