Re: [Veritas-bu] NetBackup Standard or Enterprise

[Clausen, Matt R[EQ]]

>From a licensing perspective, if you were doing a standalone instance then yes 
>the Standard version would be fine. Since you are incorporating it into an 
>existing Enterprise instance, you would need an Enterprise NetBackup server 
>license since this server would most likely be a media server for that LAN.

Matt Clausen
Network Systems Administrator
EMBARQTM
Voice: 407-741-0553  |  Wireless: 850-284-2435  |  Fax: 407-741-0455
Email: matthew.r.clau...@embarq.com
500 N. New York Ave., Winter Park, FL 32789
Mailstop: FLWNTC0103 - 1019
Voice | Data | Internet | Wireless | Entertainment
This e-mail is the property of EMBARQ and may contain confidential and 
privileged material for the sole use of the intended recipient(s). Any review, 
use, distribution or disclosure by others is strictly prohibited. If you are 
not the intended recipient (or authorized to receive for the recipient), please 
contact the sender and delete all copies of the message.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WEAVER, Simon 
(external) [simon.wea...@astrium.eads.net]
Sent: Monday, August 24, 2009 2:27 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] NetBackup Standard or Enterprise

Morning all,
Dealing with Symantec is NOT easy, when trying to price up a new NBU Server.

Could anyone help me on this, because Symantec seem to be lost (Their sales 
teams) on this...

I have a large NBU Environment, and I have inherited a small LAN that I want 
part of the NBU Environment.

It has 2 Servers. One will be attached to a HP Tape Library. The other Server I 
want to backup over the LAN.
So in summary, it will backup itself, and one other Server.

Will a STANDARD NBU Server still integrated in the current Enterprise NetBackup 
environment that I have? It is all still part of one Domain and one large 
Network, but its just a remote site.

Just wondered what the real difference was? I know that certain features like 
SSO / Database online stuff wont work, but if anyone could clarify this for me, 
it would help.


Regards

Simon

This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Netbackup Master server hardware - Solaris

[Clausen, Matt R[EQ]]

There's a white paper out there when Sun was using a T5220 as a media server 
streaming to about 6-8 StorageTek 1 drives. When we refreshed our NetBackup 
infrastructure in one location, we did something very similar to this where I 
have a T5220 as a media server streaming to 6 LTO-4 FC drives in our SL500 
library. I couldn't be happier with the performance to be honest, this setup 
flies!

Your biggest performance upgrade though might come from moving your master 
server off to dedicated hardware and let the master/media server be strictly a 
media server. Right now my master server is running on an older SunFire v480 
and it couldn't be happier.


From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mellor, Adam A.
Sent: Wednesday, April 22, 2009 12:12 AM
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] Why netbackup auto overwrite?

[Clausen, Matt R[EQ]]

How are you getting a single media ID to hold 3TB? The largest tape  
capacity I know of is the LTO-4 at 1.2TB per tape...

On Mar 5, 2009, at 8:31 PM, "KinAn"  wrote:

>
> No,no Because at dayn+1 I see tape ID 01 have ~3TB, but dayn+2 I  
> see tape ID 01 have only 300GB :(. And when i go to Restore,  
> select see all, I only see data has backup at night n+1.
>
> +-- 
> 
> |This was sent by kinan_kaz...@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] Using Fiber Channel Drives in 6.5

[Clausen, Matt R[EQ]]

What's sgscan showing? You may need to go through the whole sg driver 
installation process so the drives are visible to NBU.


From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Thompson, Jeff
Sent: Wednesday, March 04, 2009 3:05 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Using Fiber Channel Drives in 6.5

We've recently purchased a Scaler i500 with 2 fiber channel drives.  This is 
being connected via HBA to our RHEL 3 Master Server (running the 2.4 kernel).  
I have verified that the OS sees the card and drives but I can't get them 
installed in NBU.  I'm guessing that I'm missing a SAN license, is this 
correct?  Thanks!
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] NetBackup LiveUpdate Troubleshooting

[Clausen, Matt R[EQ]]

Check the webserver logs for the LiveUpdate repository. That's how I found out 
that NBU was hanging up with trying to get the miniflg.tri file due to a MIME 
issue.


From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Snyder, 
Nicholas A (IT)
Sent: Wednesday, March 04, 2009 1:28 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NetBackup LiveUpdate Troubleshooting


Anyone with any troubleshooting tips for NetBackup LiveUpdate?

I have a functioning LiveUpdate server/policy that has worked for numerous 
hosts.  However, 1 particular host seems to always fail.  The LiveUpdate policy 
on seems to run forever.  Watching the available logs on the client seem to 
show that the client is simply waiting.  Any thoughts?

I've killed the process and re-attempted multiple times;
I've uninstalled/re-installed the NetBackup client;
The same results...always "hanging" at "Loading guard file".  The same 
LiveUpdate policy has worked successfully for similar hosts.


- snip from /opt/Symantec/LiveUpdate/liveupdt.log -
Mar 4, 2009 4:09:08 PM Java LiveUpdate launched with the command line = -c 
/usr/openv/netbackup/nblu.conf
Mar 4, 2009 4:09:08 PM Using character set UTF-8
Mar 4, 2009 4:09:08 PM Command-line Product Selections to update:
Mar 4, 2009 4:09:08 PM (ProdName, Version, Lang, ItemSeqName, SeqNum)
Mar 4, 2009 4:09:08 PM Debug - Caught exception looking for root user. 
Exception text => java.lang.NullPointerException
Mar 4, 2009 4:09:08 PM Java Version 1.4.2_13.
Mar 4, 2009 4:09:08 PM Linux 2.4.21-47.0.1.ELvmnix
Mar 4, 2009 4:09:08 PM Java LiveUpdate version 3.5 Build 32.
Mar 4, 2009 4:09:08 PM ProductInventory: parsed default inventory file: 
/etc/Product.Catalog.JavaLiveUpdate
Mar 4, 2009 4:09:08 PM Inventory File Product Selections to update:
Mar 4, 2009 4:09:08 PM (ProdName, Version, Lang, ItemSeqName, SeqNum)
Mar 4, 2009 4:09:08 PM   NetBackup_LUA, 6.5, English, Update, 20070709
Mar 4, 2009 4:09:08 PM   NetBackup_JAV, 6.5, English, Update, 20070709
Mar 4, 2009 4:09:08 PM   NetBackup_ENC, 6.5, English, Update, 20070709
Mar 4, 2009 4:09:08 PM   NBClient_Linux, 6.5, English, Update, 20070709
...
Mar 4, 2009 4:09:09 PM Extracting liveupdt.grd
Mar 4, 2009 4:09:09 PM Total number of bytes read is 12,465
Mar 4, 2009 4:09:09 PM Extracting liveupdt.sig
Mar 4, 2009 4:09:09 PM Total number of bytes read is 2,267
Mar 4, 2009 4:09:09 PM Unzipping completed
Mar 4, 2009 4:09:09 PM Loading guard file:  
/tmp/1236182948771/nbclient$5flinux_6.5_english_livetri.zip1236182949090/liveupdt.grd

Mar 4, 2009 4:09:09 PM The zip entry is liveupdt.tri
Mar 4, 2009 4:09:09 PM The zip entry is liveupdt.grd
Mar 4, 2009 4:09:09 PM The zip entry is liveupdt.sig
Mar 4, 2009 4:09:09 PM Unzipping netbackup$5fjav_6.5_english_livetri.zip into 
/tmp/1236182948771/netbackup$5fjav_6.5_english_livetri.zip1236182949108 ...

Mar 4, 2009 4:09:09 PM The zip file downloaded is a catalog file
Mar 4, 2009 4:09:09 PM Extracting liveupdt.tri
Mar 4, 2009 4:09:09 PM Total number of bytes read is 928
Mar 4, 2009 4:09:09 PM Extracting liveupdt.grd
Mar 4, 2009 4:09:09 PM Total number of bytes read is 5,877
Mar 4, 2009 4:09:09 PM Extracting liveupdt.sig
Mar 4, 2009 4:09:09 PM Total number of bytes read is 2,267
Mar 4, 2009 4:09:09 PM Unzipping completed
Mar 4, 2009 4:09:09 PM Loading guard file:  
/tmp/1236182948771/netbackup$5fjav_6.5_english_livetri.zip1236182949108/liveupdt.grd

- snip from /usr/openv/netbackup/logs/nbliveup/log.030409 -
16:09:03.038 [29900] <4> nbliveup main: INITIATING nbliveup
16:09:03.038 [29900] <4> nbliveup main: argv[0] = 
/usr/openv/netbackup/bin/nbliveup
16:09:03.038 [29900] <4> nbliveup main: argv[1] =
16:09:03.038 [29900] <2> makeSocketLinger: setsockopt SO_LINGER on 1 ok
16:09:03.039 [29901] <4> nbliveup main: INITIATING nbliveup
16:09:03.039 [29901] <4> nbliveup main: argv[0] = 
/usr/openv/netbackup/bin/nbliveup
16:09:03.039 [29901] <4> nbliveup main: argv[1] =
16:09:03.039 [29901] <4> nbliveup main: argv[2] = -f
16:09:03.039 [29901] <2> makeSocketLinger: setsockopt SO_LINGER on 1 ok
16:09:03.039 [29901] <4> nbliveup main: /usr/openv/netbackup/bin/bpclusterutil 
doesn't exist
16:09:03.039 [29901] <4> nbliveup read_util: Searching file 
/usr/openv/netbackup/nblu.conf for logfile=
16:09:03.040 [29901] <4> nbliveup main: Java log file is 

16:09:03.040 [29901] <4> nbliveup read_util: Searching file /etc/Symantec.conf 
for BaseDir=
16:09:03.040 [29901] <4> nbliveup main: Symantec base path is 
16:09:03.040 [29901] <4> nbliveup main: Skipping cluster utility calls.
16:09:03.040 [29901] <4> nbliveup main: Stopping all NBU daemons.
16:09:03.040 [29901] <4> nbliveup execute_cmd: Executing 

16:09:03.041 [29900] <4> nbliveup copy_and_fork: forked /usr/openv/var/nbliveup 
(pid=29901)
16:09:08.393 [29901] <2> nbliveup execute_cmd: After call of 
/usr/openv/netbackup/bin/bp.kill_all FORCEKILL SKIPNBLU, status = 0, errno = 9

Re: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type UNKNOWN

[Clausen, Matt R[EQ]]

There is one caveat to the SL500 that you might want to check into.  
Make sure that when the Sun engineer configured your SL500 they set it  
to export the entire barcode. By default the SL500 will only export  
the left 6 characters or so which plays havoc with your barcode and  
media id rules.

On Feb 18, 2009, at 11:55 AM, "WEAVER, Simon (external)" 
 wrote:

> Hi Justin
> Correct. LTO3 Drives and Tapes in TLD(0) Robot
> LTO4 Drives and Tapes in TLD(1) Robot
>
> When I do an inventory on TLD(1) It see's the tapes, but the tapes are
> in Scratch. So I am happy with that. Plus I checked the label  
> reference
> for LTO4, and I think this is where there might be a snag.
>
> The drives are known as HCART - As we discussed for LTO4 Drives.
>
> The Label's for LTO3 are shown in NetBackup as L3 - where  is
> the last 4 digits of the barcode (ie: 0345L3)
> The Label's for LTO4 are shown in Netbackup as AAAxxx - where AAA is
> letters and xxx is numbers (ie: EII500) No mention of L4 at the end,
> even though the label shows an L4.
>
> Running a job on the new robot shows a 96 - which makes me think it
> could be barcode related. Defined new Policy, with correct storage  
> unit,
> but job still fails. But reverting the policy back to its existing
> storage unit shows its all ok.
>
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Wednesday, February 18, 2009 4:30 PM
> To: WEAVER, Simon (external)
> Cc: Dean; veritas-bu@mailman.eng.auburn.edu
> Subject: RE: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type  
> UNKNOWN
>
> Simon,
>
> Device mappings: good.
>
> Yes, both robots share the same scratch pool.
>
> Do you have LTO-4 in one library and LTO-3 in the other or something?
>
> Justin.
>
> On Wed, 18 Feb 2009, WEAVER, Simon (external) wrote:
>
>> Well device mappings seems to have worked, and I have 2 robots (TLD0
>> and
>> TLD1) and seems to work.
>>
>> However, do both robots share the same scratch pool? I got a status
>> 96, so wonder if it is linked to hcart not having any barcode rules
>> assigned??
>>
>> Simon
>>
>> -Original Message-
>> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
>> Sent: Wednesday, February 18, 2009 3:15 PM
>> To: WEAVER, Simon (external)
>> Cc: Dean; veritas-bu@mailman.eng.auburn.edu
>> Subject: RE: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type
>> UNKNOWN
>>
>> Yes,
>>
>> But the last update is April 11th 2008, you need to see if the LTO-4
>> entries are in there.
>>
>> The one for 6.0 is still maintained and that is what I used and then
>> it showed the proper drive type.
>>
>> You could try manually adding it in the file if its not included in
>> 5.1, but I have not tried it personally.
>>
>> Justin.
>>
>> On Wed, 18 Feb 2009, WEAVER, Simon (external) wrote:
>>
>>> Would this be the one from the KB Site?
>>>
>>> http://seer.entsupport.symantec.com/docs/297103.htm
>>>
>>>
>>>
>>> -Original Message-
>>> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
>>> Sent: Wednesday, February 18, 2009 3:00 PM
>>> To: WEAVER, Simon (external)
>>> Cc: Dean; veritas-bu@mailman.eng.auburn.edu
>>> Subject: Re: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type
>>> UNKNOWN
>>>
>>> Although when I had the problem I was running 6.x, I think 6.0MP4 or
>>> MP5 did not include the mapping (device mapping file) and when I
>>> updated it, it recognized the drive, it should not be UNKNOWN, I
>>> think
>>
>>> that means your device mapping file is too old, try updating it
> first.
>>>
>>>
>>> On Wed, 18 Feb 2009, Justin Piszcz wrote:
>>>
 Simon, I had the same problem.

 Your first problem is you need to install the latest device
 configuration file.
 Your second problem is LTO-4, yes, it is type: 'hcart'

 Justin.

 On Wed, 18 Feb 2009, WEAVER, Simon (external) wrote:

> Further to my email, found this
>
> http://seer.entsupport.symantec.com/docs/295519.htm
>
> Anyone confirm if this is right for a 5.1 MP5 environment??
>
> 
>
> From: veritas-bu-boun...@mailman.eng.auburn.edu
> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
> WEAVER, Simon (external)
> Sent: Wednesday, February 18, 2009 1:50 PM
> To: Dean
> Cc: veritas-bu@mailman.eng.auburn.edu
> Subject: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type
> UNKNOWN
>
>
> Hi All,
> Seem to be having problems, using the Device Configuration Wizard
> on
>>
> NBU
> 5.1 MP5 on Win2k3 SP1 and SL500 LTO4 Drives.
>
> Although its in the Fabric, Device Manager, and used the HP
> Drivers,
>>
> everything looks great, apart from the DCU Wizard, which is
> reporting
>>>
> back the "Drive Type" for the LTO4 is "Unknown".
>
> I went to this link:
> http://seer.entsupport.symantec.com/docs/287850.htm
>    bu

Re: [Veritas-bu] Netbackup Live Update.

[Clausen, Matt R[EQ]]

There is a critical step that's missing from the IIS Web Server setup for 
LiveUpdate (and one that took me weeks to get figured out):

You need to add a new MIME type of .flg of type application/octet-stream

I don't think you need that for Apache, but not sure.


From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Renee Carlisle
Sent: Thursday, February 12, 2009 2:06 PM
To: Ed Wilts; Michitsch, John
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Netbackup Live Update.

OK, first rule...forget the documentation Symantec gives you for this 
process..unfortunately it is not great.  Here is what we use to get http going 
for lu for either Windows or Unix.  We have had no problem with it now that we 
have the process down..and have been able to patch application clusters...so 
not sure what other people have seen there.  Hope this helps:

OK, we usually use http.  The disk share method is for Windows only and Unix 
clients can't get to the patches, which kind of defeats the purpose in my 
opinion.  So, we stick with http...here is the process we use:

For unix live update server http access:


1.  Pull down patches to lu server/dir, unzip all in same dir (no subdirs 
for each patch bundle)
2.  turn on http on lu server
/etc/init.d/apache start (first copy /etc/apache/httpd-example.conf 
--> httpd.conf)

3.  ln -s  /var/apache/htdocs/ or 
where ever www root is, above is default, this setting can be determined from 
the apach.conf file in /etc/apache/apache.conf
4.  install nblu on any
/usr/openv/netbackup/bin/install_nblu
when prompted type in:
url=http://

5.  Create lu policies per normal documentation and go

For windows live update server http access:


1.  Install IIS, need windows install cd, control panel/add remove 
programs/windows components/application services/IIS (must go into details at 
each level to unselect and select components you want for IIS and www)
2.  Start www service
3.  Launch IIS manager, highlight default web site, right click, new 
virtual dir.
4.  Put all patches in wwwroot\liveupdate (c:\inetpub\wwwroot\create 
virtual dir in IIS for liveupdate
5.  Unzip all in same dir (no subdirs)
6.  SET LU_SERVER=http:///liveupdate  (in 
installdir/symantec/liveupdate/LU_install.bat, then run it, make sure you have 
3 exe's in there with it, LUCheck, LU_Registration LUSetup, all 4 files on NBU 
windows install cd)

**NOTES:  keep all dir names and servernames lower case for unix/windows

Renee Carlisle
ServerWare Coporation

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts
Sent: Thursday, February 12, 2009 12:10 PM
To: Michitsch, John
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Netbackup Live Update.

On Wed, Feb 11, 2009 at 12:56 PM, Michitsch, John 
mailto:jmich...@gannett.com>> wrote:
Is anyone using this to upgrade client agents.  All things I've seen/read are 
negative about the product.  We wasted many hours trying to get it to work on 
version 6.5 when it first came out.  6.5.3 is supposed to fix some issues, I 
don't want to go down the LU road again without the possibility of success!  
Anyone have it up and running successfully?

There are many caveats to getting this going properly and some are severe 
enough that we're not able to implement it for us for some of the clients.  We 
had a lengthy discussion with the developers of the client deployment packages 
at the last Symantec Tech Day in December so they're aware of the restrictions.

One of the biggest gotchas for us is that it's pretty much unusable in a 
cluster environment.  One of its checks is to see if the client is actually 
doing a backup before it tries to upgrade itself.  If you have multiple names 
for your hosts - and this is the case for close to 100% of the cluster users - 
this check can fail and your backup and/or upgrade job will fail.

In general, the NetBackup support for cluster clients is pretty poor.  Yeah, 
Symantec has hacked "support" in there but it's simply the case of not breaking 
in a cluster but that's about it.  LiveUpdate is just another example of where 
Symantec's cluster "support" fails to solve the problems properly.
.../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] printout Vault profile

[Clausen, Matt R[EQ]]

/opt/openv/netbackup/bin/vltadm

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Doug
Sent: Wednesday, February 11, 2009 1:32 PM
To: Stump, Bob A; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] printout Vault profile

Where is vltadm ?

Doug Preston

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Stump,
Bob A
Sent: Wednesday, February 11, 2009 9:46 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] printout Vault profile



I know I can get the information using vltadm but that takes several
steps and just writes to the outout to the screen.


-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Stump,
Bob A
Sent: Wednesday, February 11, 2009 11:08 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] printout Vault profile


NetBackup 6.5.3 w/Vault Solaris 9 master server

How can I use the command line to printout the vault profiles? 
Is there a bppllist  -U equivalent?

I miss the old dup_param scripts sigh

Bob Stump FNIS


_

The information contained in this message is proprietary and/or
confidential. If you are not the 
intended recipient, please: (i) delete the message and all copies; (ii)
do not disclose, 
distribute or use the message in any manner; and (iii) notify the sender
immediately. In addition, 
please be aware that any message addressed to our domain is subject to
archiving and review by 
persons other than the intended recipient. Thank you.
_

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_

The information contained in this message is proprietary and/or
confidential. If you are not the 
intended recipient, please: (i) delete the message and all copies; (ii)
do not disclose, 
distribute or use the message in any manner; and (iii) notify the sender
immediately. In addition, 
please be aware that any message addressed to our domain is subject to
archiving and review by 
persons other than the intended recipient. Thank you.
_

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Netbackup Live Update.

[Clausen, Matt R[EQ]]

I have successfully gotten it working with a IIS 6.0 Web Server and a Solaris 
10 Client. So far it looks pretty sweet, I'm actually gearing up for a full out 
deployment of it soon now that I have my test case working.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Michitsch, John
Sent: Wednesday, February 11, 2009 1:56 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Netbackup Live Update.

Is anyone using this to upgrade client agents.  All things I've seen/read are 
negative about the product.  We wasted many hours trying to get it to work on 
version 6.5 when it first came out.  6.5.3 is supposed to fix some issues, I 
don't want to go down the LU road again without the possibility of success!  
Anyone have it up and running successfully?

Thanks,

Johnny

_

The information contained in this message is proprietary and/or confidential. 
If you are not the 
intended recipient, please: (i) delete the message and all copies; (ii) do not 
disclose, 
distribute or use the message in any manner; and (iii) notify the sender 
immediately. In addition, 
please be aware that any message addressed to our domain is subject to 
archiving and review by 
persons other than the intended recipient. Thank you.
_

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Netbackup Live Update.

[Clausen, Matt R[EQ]]

The two are vastly different. NBU LiveUpdate probably could not co-exist on a 
SAV LU Server because the files which identify which packages to get would not 
contain information about the other product (i.e. a NBU LU Server would not 
contain information on SAV and vice-versa). Because there are checksums 
involved in the process, manually editing and combining the files in question 
(like the livetri files) would not work.

-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, February 11, 2009 4:13 PM
To: jmich...@gannett.com; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Netbackup Live Update.

I have not tried it yet, I need to talk to hour virus guy because he has
Symantec live update set up and I want to make sure we don't step on
each other.  So I had not even tried.


-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
Michitsch, John
Sent: Wednesday, February 11, 2009 12:56 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Netbackup Live Update.

Is anyone using this to upgrade client agents.  All things I've
seen/read are negative about the product.  We wasted many hours trying
to get it to work on version 6.5 when it first came out.  6.5.3 is
supposed to fix some issues, I don't want to go down the LU road again
without the possibility of success!  Anyone have it up and running
successfully?

Thanks,

Johnny

_

The information contained in this message is proprietary and/or
confidential. If you are not the 
intended recipient, please: (i) delete the message and all copies; (ii)
do not disclose, 
distribute or use the message in any manner; and (iii) notify the sender
immediately. In addition, 
please be aware that any message addressed to our domain is subject to
archiving and review by 
persons other than the intended recipient. Thank you.
_

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
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 compatibility

[Clausen, Matt R[EQ]]

Why not go with the SL500 but with the Base+Drive modules only? That would give 
you the base module with 2 drives and cartridge slots and a Drive Expansion 
Module with up to 4 more drives (you'd only use 2) and the cartridge slots in 
that module. That way you have a path for future expansion as well if you need 
to add more cartridge expansion modules down the road.


From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Boris Kraizman
Sent: Thursday, February 05, 2009 10:58 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] DR compatibility

Hi Folks,

I am working on a DR solution for my company. I use StorageTek SL500 and L180 
with LTO3 fiber attached. Netbackup is tuned with 256K data buffers. Now, I 
need a smaller tape unit at my active DR site to support reading LTO3 tape 
media from the primary sites. I looked at SL48, it looks like I can go just 
with 2xLTO3 full height drives in it to get the same fiber speed. I used a 
StorageTek L20 in the past with Ultra 160 SCSI LVD and I could not read tapes 
written with 256k data buffers. And based on the sizing for the business 
applications in the DR, I would need 4 tape drives at least. I would 
appricaite, if anybody would give their recommendations.

Thank you,
Boris
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Decommission a library

[Clausen, Matt R[EQ]]

Remove the media from the L700e and have NetBackup inventory the robot. This 
will put all the tapes into standalone.

Then put the tapes into the SL500 and inventory the new robot, NetBackup will 
see the tapes in that new robot and adjust the locations accordingly.

This of course assumes you are using a master + many media configuration.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Klebba, Don
Sent: Wednesday, February 04, 2009 2:15 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Decommission a library

We're currently running NBU 6.5.2a on a Solaris master server. We have a L700e 
in our primary data center
And a SL500 attached to a Solaris media server in our remote data center. We're 
thinking of getting rid of
The L700e and doing all of our tape backups in the remote data center. My 
question is, what do I do with
All the media that is assigned to the L700e. Is there a easy way to relocate 
that media to the SL500?

Don Klebba
Quicken Loans
Storage Management Team
donkle...@quickenloans.com
phone: (734)805-7791



___
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] Windows Mount points & ALL_LOCAL_DRIVES

[Clausen, Matt R[EQ]]

Is D:\data something special (like a disk attached at a mountpoint or a SAN 
volume)?

You might be able to do this as your backup selections:

ALL_LOCAL_DRIVES
D:\data


From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Marianne Van 
Den Berg
Sent: Wednesday, February 04, 2009 9:45 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Windows Mount points & ALL_LOCAL_DRIVES

Hi All

We have the following scenario:

3  local volumes on Windows 2003 server:
C:\
D:\
D:\data

Policy is configured to backup ALL_LOCAL_DRIVES.
C and D are getting backed up, not D:\data.

Admin Guide says NOT to use ALL_LOCAL_DRIVES and Cross Mount Points together.

How is everyone else backing up Windows mount points?

I'm sure it will work if we explicitly specify them all in the file list, but 
we do not want to run the risk of missing data if a Sysadmin adds another mount 
point.

NetBackup 6.5.2a.

Regards

Marianne
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Enterprise Vs Standard license

[Clausen, Matt R[EQ]]

NetBackup Standard = Allowes a Single Combined Master+Media Server
NetBackup Enterprise = Allows Multiple Master/Media Servers

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of reddi72
Sent: Tuesday, February 03, 2009 5:41 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Enterprise Vs Standard license


We are in the process of re-evaluating all our netbackup licenses . Can anyone 
please tell me what is difference between Netbackup enterprise license Vs 
Netbackup  Standard license ?

P.S. Master and media run on the same box for all the Netbackup servers in our 
environment

+--
|This was sent by smitharedd...@hotmail.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] Netbackup 6.5.3

[Clausen, Matt R[EQ]]

If NetBackup is going to back up files on a server, you need the client 
software. The entire NetBackup suite is Client/Server based where the server 
connects to the client and basically sucks the files back to the server to 
place into the appropriate storage based on the policy.

I'm not sure what you mean by restoring from the master server. Does that mean 
you're going to restore files to the master server then copy them back to the 
original server? That's kind of defeating the purpose of using a client/server 
based backup solution. With the client installed, NetBackup would place the 
files back on the target server with the correct permissions and ownership thus 
reducing the chance of a mistake along those lines. If you didn't want to 
overwrite the original files, you can have the server (acting through the 
client) put the restored files in a separate directory to move into place that 
way.


From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Obenschain, 
Charles T.
Sent: Tuesday, February 03, 2009 4:41 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Netbackup 6.5.3

I have a really basic question.
Do you need to load the client software on the server that you are backing up 
if you are NOT going to restore files from the "Client" server?  I will be 
restoring files only from the master server.
Also, what processes run on the "client" if no client software is loaded so 
that NBU can get the information for the backup?

Charley Obenschain

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Netbackup 6.5 and Quantum Scalar 50

[Clausen, Matt R[EQ]]

Mailslots are not treated as a normal slot as far as NetBackup is concerned. 
You need to have an empty slot for the tape to go into before NetBackup can 
then move it into a drive or import it into the library. As a general rule of 
thumb, I will usually allocate one empty slot per mailslot in my libraries.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of thgreatoz
Sent: Tuesday, February 03, 2009 1:49 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Netbackup 6.5 and Quantum Scalar 50



bob944 wrote:
> 
> I don't know your hardware, but are you selecting "Empty media sccess
> port prior to updating" in the inventory GUI?
> 
> If the Scalar 50 is like some other small scalar that I saw in a demo,
> when you put tapes in the slid-out magazine, a little dialog comes up on
> the control panel asking you to choose between X and Y.  One of those is
> "system," IIRC.  And I think the one you want is the "pushbutton" on the
> right side.  Without doing that, tapes stay in the magazine.



When I select that option, I get 
"media access port request reported that the robotic library is full:

  *** Failed to find an available slot to inject to ***"

whether or not there is any media in either of the passthrough ports.

+--
|This was sent by kocon...@dialogue-marketing.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] Confusing disk staging methods

[Clausen, Matt R [EQ]]

Here are the basics:

1. Basic Disk Staging

Backup to Disk First then a Destaging schedule duplicates the backup image to 
tape media. Once the image is successfully destaged to tape, it is then removed 
from the disk depending on how your low/high water marks are set. You need 
enough disk space with this though to basically store all your backups until 
the images can be successfully destaged.

2. Storage Lifecycle Policies

Basically these define the backup/duplication relationships based on the 
"level" of the SLP defined in the policy. The nice thing about these is you 
define the schedule once and it handles it from there backing up and 
duplicating based on the directives in the policy. The caveat here is that you 
need Advanced Disk Staging units which means the Flexible Disk Option (Read 
). This is basically Vault without the reporting/management 
functionality.

3. Multiple Copies

When a backup runs, it makes multiple copies based on what you tell it. Think 
of it as multiple destinations for a backup at the time the policy runs.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of ssloh
Sent: Wednesday, December 17, 2008 9:00 PM
To: veritas-bu
Subject: [Veritas-bu] Confusing disk staging methods

Hi folks,

Could help to elaborate what are the differences & scenarios apply between
1. Basic Disk staging
2. Storage Lifecycle Policies
3. Multiple copies

After reading the NBU guide getting more and more confusing.

Thanks
___
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] 6.5 linux client software help

[Clausen, Matt R [EQ]]

Dave,

The 6.5_CLIENTS2 tarball should be the one you need. That should be the one 
with the Linux client files in it (1 is HP-UX, AIX, etc. and 3 is mostly 
Solaris). The file you downloaded is the actual NetBackup installation for a 
master or media server.

Once you install the client, then you would install the 6.5.X CLT and JAV 
patches.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dave Markham
Sent: Wednesday, December 17, 2008 8:19 AM
To: Spearman, David
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] 6.5 linux client software help

Cheers i am just downloading NetBackup_6.5_Linux2.4.tar.gz  from the
fileconnect site after getting a serial number from the project manager.

Issue is i only need the client software, so am a bit unsure how or what
needs installing as i have always pushed software out from unix master
or media servers before.

I'm assuming getting the linux tar file is the master server software
but gives the option to install client only? Question then is do i
assume i dont need the 6.5_CLIENTS1,2 or 3 tars, plus the patches from
the ftp site for linux suggest i need the CLT patch as a prerequisite,
but i've only installed these on masters before and updated clients.
With the master being windows i'm a bit stuck.

I'm trying to read documentation but as you probably know it sends you
all over the place referencing diff docs etc.

Cheers


Spearman, David wrote:
> Dave,
>
> Assuming you have access to the licensing portal you can download all
> the "master" software from there. It is still a painful thing to wind
> your way through but it is available. After that the patches can be
> downloaded from the ftp site.
>
>
> https://licensing.symantec.com/acctmgmt/index.jsp
>
> David Spearman
> County of Henrico
>
> -Original Message-
> From: veritas-bu-boun...@mailman.eng.auburn.edu
> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dave
> Markham
> Sent: Wednesday, December 17, 2008 8:05 AM
> To: veritas-bu@mailman.eng.auburn.edu
> Subject: [Veritas-bu] 6.5 linux client software help
>
> Guys i'm being put under pressure by management to assist in a system,
> i've had nothing to do with design and build, to get a linux redhat
> client installed for NBU 6.5
>
> As far as i can ascertain the master/media is a windows server. I'm a
> solaris engineer and know if the master were unix i could simply push
> the correct client software out to the linux client. With windows i
> assume this is not possible??
>
> Which brings me to where to i get the linux 6.5 client software from? I
> don't have the media.
>
> On the symantec site i see various patches for 6.5.1 CLT containing all
> the client binaries, but this is normally installed on the unix server
> isn't it? Can this just be installed on a linux client as is with no
> previous version on it?
>
> Any pointers would be appreciated
>
> Dave
> ___
> 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] 6.5.3 on the FTP site

[Clausen, Matt R [EQ]]

Are you running this under Solaris? If so, have you turned off tcp fusion?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stafford, Geoff
Sent: Thursday, December 04, 2008 11:53 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] 6.5.3 on the FTP site

Just wondering if anyone has seen any issues with DSSU relocation
hanging?  Seen it a few times this week where the relocation job will
hang for several hours after it finishes reading an image then never
starts the next.  Once or twice it has "woken up", other times I've left
it out there for 10-12 hours and nothing.

Too early to proclaim it's a bug, just wondering if anyone else is
seeing this?

Geoff Stafford
Barclaycard US
Data Protection Engineering
office:
mobile:

Date: Wed, 3 Dec 2008 14:59:24 +0100
From: "Haberl, Max" <[EMAIL PROTECTED]>
Subject: Re: [Veritas-bu] 6.5.3 on the FTP site
To: 
Message-ID:

<[EMAIL PROTECTED]
>

Content-Type: text/plain;   charset="us-ascii"

I got the first BUG. YE

Ok, it's just the JAVA GUI, but it's something they should see at the
first check.

Try to open the Activity Monitor, Filter, Advanced Search and then try
to do a search for a Policy.

This really sucks.


Cheers
Max



--


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] Reg: LTO3

[Clausen, Matt R [EQ]]

Regarding the tape-drive based compression though, I think by default the drive 
does not compress (actually I'm fairly positive this is the case). The driver 
has to instruct the tape drive to enable hardware compression. In the case of 
solaris, this is done based on which device you are physically sending the 
backups to.

/dev/rmt/0 <-- The Tape Drive with no options.
/dev/rmt/0cbn <-- What you should be using. Enables HW compression and tells 
the tape drive to not automatically rewind.

The key being the 'c' in the device name. If you don't have that, then under 
Solaris the drive will not compress using its internal hardware compression.

Keep in mind though, if you are sending non-compressible binary files, 400GB is 
what you are going to get, regardless of if the client or drive is doing the 
compression. If you're sending highly compressible files (images for example) 
then you will get very good compression and your tape capacity will lean closer 
to the 800GB mark. If you're sending a mixture, then you will get somewhere 
between the two (depending on the type of files).

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz
Sent: Friday, November 21, 2008 10:48 AM
To: Haberl, Max
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Reg: LTO3



On Fri, 21 Nov 2008, Haberl, Max wrote:

> Hi Justin,
>
> as far as i understand you enabled the compression in the policy right ?
No, compression is handled by the tape drive in hardware.  The compression
in the policy that you are referring to is whats referred to as client-side
compression, the data is compressed on the client before it is 'shipped' to
the netbackup media server, this can actual reduce actual compression rates
on the media itself because its sending a somewhat pre-compressed file to the
drive which cannot be compressed as well as it could be if it were a regular
file.  You would only want to use that option to save on bandwidth or if you
are backing up a host on a slow link.

> If yes, the benefit of the drive internal compression is around 0 cause you 
> still write a compressed tar file on tape.
See above.

>
> That means that the visible size of "bpmedialist -m " is already the 
> compressed size.
That command will show you how much is written on the tape once full then you
can calcuate the ratio based on an LTO-3 tape being 400GiB.

>
> Cheers
> Max


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] How to find out who cancelled a Backup in NBU

[Clausen, Matt R [EQ]]

What version of NetBackup as well? If it's 6.5.X you might be able to check the 
unified logs in /opt/openv/logs and see if they tell you anything. I know 
whenever I do policy manipulations they show up in there.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hudson, Steve
Sent: Friday, November 14, 2008 10:27 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] How to find out who cancelled a Backup in NBU

Folks I have searched many many logs on my SUN box but I can't seem to find out 
who cancelled a job this morning at 443 AM. Do you Gurus know of a way to do 
this??? Thanks.


Steve Hudson
Enterprise Storage
Iron Mountain
745 Atlantic Ave
Boston, MA 02111
Phone: (617) 535-2849

[EMAIL PROTECTED]


Visit the new www.ironmountain.com
Tour Iron Mountain




The information contained in this email message and its attachments is intended 
only for the private and confidential use of the recipient(s) named above, 
unless the sender expressly agrees otherwise. Transmission of email over the 
Internet is not a secure communications medium. If you are requesting or have 
requested the transmittal of personal data, as defined in applicable privacy 
laws by means of email or in an attachment to email you must select a more 
secure alternate means of transmittal that supports your obligations to protect 
such personal data. If the reader of this message is not the intended recipient 
and/or you have received this email in error, you must take no action based on 
the information in this email and you are hereby notified that any 
dissemination, misuse, copying, or disclosure of this communication is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by email and delete the original message.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Refreshing trial license for media server

[Clausen, Matt R [EQ]]

Run /opt/openv/netbackup/bin/admincmd/get_license_key then delete the old trial 
key and Add the new one.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dbergen
Sent: Thursday, November 13, 2008 1:27 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Refreshing trial license for media server


I've had a 90 day trial license installed for a new media server which has 
expired, I got another trial license but can't figure out how to apply it to 
the existing test media server, anyone?

dj

+--
|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] MySQL Backups via Snapshot Client?

[Clausen, Matt R [EQ]]

Has anyone used the Snapshot client (or snapshotting in general) to backup a 
MySQL database? I have some 24/7 MySQL databases that I can't shutdown to 
export all their files (these are some very large databases and it would take 
too much time) and I've been looking for a better way to back them up.

Any ideas? - Thanks!

Matt Clausen
Network Systems Administrator
EMBARQTM
Voice: 407-741-0553  |  Wireless: 850-284-2435  |  Fax: 407-741-0455
Email: [EMAIL PROTECTED]
500 N. New York Ave., Winter Park, FL 32789
Mailstop: FLWNTC0103 - 1019
Voice | Data | Internet | Wireless | Entertainment
This e-mail is the property of EMBARQ and may contain confidential and 
privileged material for the sole use of the intended recipient(s). Any review, 
use, distribution or disclosure by others is strictly prohibited. If you are 
not the intended recipient (or authorized to receive for the recipient), please 
contact the sender and delete all copies of the message.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Which license should we buy ?

[Clausen, Matt R [EQ]]

Generally you should run this by your Symantec sales rep. since they are always 
the foremost authority in what you need in terms of licensing.

This is what I think you will need, but again, check with your sales rep.

You need 3 NetBackup Enterprise Licenses... which ones depend on your 
hardware... UNIX vs. Linux vs. Solaris(x64) vs. .

You'll most likely need the Exchange Agent if you want to do online backups of 
your Exchange store.

RMAN backups you don't need anything special if all you're doing is dumping an 
ORACLE RMAN based backup and then backing up the files it outputs. If you need 
to connect to the database as a client and back it up that way, the Oracle 
Agent may be required (which since you list SQL backups - you may need anyways 
but that depends on the database type -- Sybase, Informix, etc.)

SAN clients - A few ways to handle this, if your media server is attached to 
the SAN, then you just have it do the backups of the SAN data. If you need to 
back up a client attached to the SAN then you do a normal client-based backup.

NDMP (even a few) will most likely require the NDMP Add-on.

You also don't have other licenses listed that you will need:

Tape Drive Licenses for the number of drives per robot (i.e. if it's a robot 
with 4 drives you need 4 tape library drive licenses). Standalone tape drives 
do not require this license.

Client Licenses (each client needs a license)

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 12:31 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Which license should we buy ?


 Hi
I am new to NBU licensing for NBU 6.5.2 release. We are planning to
backup following application .. and NBU infrastructure will consists of
one NBU master and 2 NBU media server.
1). Unix ( hp ,aix,linux,solaris and IRix ) os backup.
2). exchange backup
3). RMAN backup
4). SQL backup
5). Few SAN client
6). FEW ndmp backup

THX


___
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

[Clausen, Matt R [EQ]]

I have to disagree with the ALL_LOCAL_DRIVES being a good thing in some 
circumstances. I recently went from using ALL_LOCAL_DRIVES to specifying each 
of my disk slices (/, /usr, /var, /opt, etc.) and breaking them out with 
NEW_STREAM on my UNIX servers for a very simple reason. Using ALL_LOCAL_DRIVES 
and multiple streams will thrash the disks on that type of machine.

Think of it like this You have several disk slices or partitions, but they 
all share a single "disk". When you do ALL_LOCAL_DRIVES + Multiple Streams then 
you are in fact initiating a stream per partition/slice. This can be upwards of 
4-5 streams hitting a single disk which means the head is jumping around all 
over the place to provide the data flow and wearing your disk out.

I've been to a few of the NetBackup classes, and in every one I've been told to 
never let the number of streams exceed the number of spindles in the physical 
hardware you're backing up. With specifying my directories individually I can 
regulate the streams so that I am not overtaxing my disk hardware. If I have 
say / + /usr + /var on one disk mirror, then I can specify those directories 
then the NEW_STREAM and then my /opt directory which is a ZFS pool on another 
set of disks. This way I am not running the risk of thrashing the disks and 
reducing their service life prematurely.

Your mileage my vary of course; there are arguments for both sets of thinking. 
I just found what the instructors were saying to be a very compelling argument 
to avoid ALL_LOCAL_DRIVES for my UNIX servers and keep using it mainly for my 
Windows servers where each drive is generally a physical drive.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean
Sent: Wednesday, October 22, 2008 3:01 AM
To: Nathan Kippen; Veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] "/" + Cross All Mnt Pts Vs. ALL_LOCAL_DRIVES

We use ALL_LOCAL_DRIVES and "allow multiple streams" everywhere,
regardless of the O/S.

Where there is a database that needs to be backed up seperately, it
will have it's own policy just for that database, on that client, and
the backup selection list might look like :

/opt/oracle
/oradata/db1
/oradata/db2
/oradata/db3

Then, we back up the rest of the client in a more generic "catch all"
policy ... say a policy named "unix_system_prod", which contains many
clients and has ALL_LOCAL_DRIVES in it's selection list.

We setup an exclude list for that particular client, for only the
"unix_system_prod" policy, which contains the entries listed above, so
that we're not backing up the db files twice.

ALL_LOCAL_DRIVES is a good thing! It means never having to say "Umm...
sorry... we don't have a backup. The Unix guy didn't tell us when he
added that /super_critical mountpoint 3 years ago."


On Wed, Oct 22, 2008 at 8:24 AM, Nathan Kippen <[EMAIL PROTECTED]> wrote:
> 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 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] DSSU De-Staging Hanging

[Clausen, Matt R [EQ]]

Upgrade to NBU 6.5.2A, it fixed a lot of issues with duplication.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan
Sent: Wednesday, October 22, 2008 9:06 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] DSSU De-Staging Hanging

All,

NBU 6.5.1 on Win2k3

I've got a problem with a certain Media server's DSSU Destaging jobs just 
hanging.  It looks to me as if the first destaging job finishes writing its 
images to disk, but it never completes which hangs up the next destaging jobs 
(different dssu).  I'm unable to cancel the first destaging job and can only 
clear it by restarting services on the master.  I'm inclined to rebuild the 
media server which is having other OS related issues, but I'm not certain this 
isn't a master server issue.  Any ideas before I escalate to Symantec Tech 
Support?

Thanks,

-Jonathan Martin
Intersil Corp.
Servers and Security Operations

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Limit bandwidth

[Clausen, Matt R [EQ]]

Yes there is (for NBU 6.5.X anyways),

Under the Master/Media Server properties, click on the Bandwidth menu option 
and then you can put in the IP address you want to throttle. The value is in 
KB/sec so 2.5MB/sec would be 2500 KB/sec.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baumann, Kevin
Sent: Tuesday, October 21, 2008 9:13 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Limit bandwidth

All,

Is there a way to limit bandwidth?  I have a master server that is down and I 
want to backup a unix client over the WAN.  But, I would like to limit that to 
2 MB/sec.

Thanks in advance.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Media Administration - Automating Ejection of Duplicate Copies to be offsited

[Clausen, Matt R [EQ]]

The Enterprise Base license does NOT include vault. You have to purchase the 
Vault Base license which will then give you the 4 drives to start with.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffery Price
Sent: Monday, October 20, 2008 2:03 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Media Administration - Automating Ejection of Duplicate 
Copies to be offsited

Hello List.

I have a VERY basic question regarding media operations.  NBU 6.5.2a W2K3 x64 
master+media, SSO, NDMP.  There is a single Tape Library w/ 4 LTO-4 Drives.

Let's say I have a policy to backup a server, and want to make an additional 
copy to offsite.  I understand that I need to have:

Volume Group for Offsite Volumes
Volume Pool for Offsite Volumes

In the policy, I can just create multiple copies in different Volume Pools.

Is there a way to automate the ejection of the offsite volumes without the 
Vault Option?

On another note, read in a previous post that NBU Enterprise Base allows for 
vault operations for up to 4 drives.

Is there a good document that anyone could suggest reading for an overview of 
media operations?

Thanks.

--Jeff


This communication is for use by the intended recipient and contains 
information that may be privileged, confidential or copyrighted under law. If 
you are not the intended recipient, you are hereby formally notified that any 
use, copying or distribution of this e-Mail, in whole or in part, is strictly 
prohibited. Please notify the sender by return e-Mail and delete this e-Mail 
from your system. Unless explicitly and conspicuously stated in the subject 
matter of the above e-Mail, this e-Mail does not constitute a contract offer, a 
contract amendment, or an acceptance of a contract offer. This e-Mail does not 
constitute consent to the use of sender's contact information for direct 
marketing purposes or for transfers of data to third parties.

This email has been scanned for all viruses by the MessageLabs service.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Duplicating Large Images to Multiple Copies Fails After 20 Minutes

[Clausen, Matt R [EQ]]

What version of 6.5 are you running? 6.5.1?


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Monday, October 20, 2008 2:52 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Duplicating Large Images to Multiple Copies Fails After 
20 Minutes


This one has me stuck.  We recently upgraded to NBU 6.5 and did not experience 
this problem with 5.1.  I have several images on tape I need to duplicate to 
two copies on other tapes so that I can send them off-site.  However, whenever 
I try to run the duplication job (just manually kicked off), it fails after 20 
minutes every time (almost to the second).  These images are fairly large 
(about 100GB).  Here is what I've figured out so far:

-Running the duplication job with any smaller image that takes less than 20 
minutes succeeds just fine
-Running the large duplication job with just a single copy works fine.
-Running the large duplication job with any combination of storage units or 
tape drives makes no difference.

Looking at the logs while this happens, I noticed that right as the job begins 
to fail, I get a lot of lines like this:

13:41:25.826 [9151] <2> drivename_open: Called with Create 1, file 
PP-L700-SDLT01
13:41:25.826 [9151] <2> drivename_lock: lock failed
13:41:25.826 [9151] <2> drivename_close: Called for file PP-L700-SDLT01
13:41:25.878 [9152] <2> drivename_open: Called with Create 1, file 
PP-L700-SDLT08
13:41:25.878 [9152] <2> drivename_lock: lock failed
13:41:25.878 [9152] <2> drivename_close: Called for file PP-L700-SDLT08
13:41:30.827 [9151] <2> drivename_open: Called with Create 1, file 
PP-L700-SDLT01
13:41:30.827 [9151] <2> drivename_lock: lock failed

It's always at that mysterious 20 minute mark and if I'm trying to make more 
than 1 copy.  It's like there's some limit somewhere that was implemented on 
6.5.  Has anyone else experienced this?

Thanks,
Brian Beaird
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Duplicating Image

[Clausen, Matt R [EQ]]

I think what he means is that if he uses in-line copies, he loses one tape 
drive per in-line copy which due to the small backup windows would be a 
problem. I would seriously look into Storage Lifecycle Policies, because then 
you can configure a policy to do a backup at 8PM and then instruct the same 
policy to do a duplication later on that evening. The only caveat is that you 
can't use Basic Disk units (Standard disk storage, disk staging units, etc.). 
If you have the Advanced Disk options, then this isn't a problem. For something 
simple like this though, backup to tape followed by a duplication, it would fit 
the bill quite nicely.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston
Sent: Saturday, October 18, 2008 2:47 AM
To: [EMAIL PROTECTED]; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Duplicating Image

Have you tested inline copy?  My experience has been that it doesn't impact 
performance as much as you might think.



Curtis Preston  |  VP Data Protection
GlassHouse Technologies, Inc.

T: +1 760 710 2004 |  C: +1 760 419 5838 |  F: +1 760 710 2009
[EMAIL PROTECTED] |  www.glasshouse.com
Infrastructure :: Optimized
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, October 17, 2008 7:50 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Duplicating Image

Because if we do inline,it will impact to performanceand we have short windows
backup time.

- Original Message -
From: oersted <[EMAIL PROTECTED]>
Date: Saturday, October 18, 2008 4:41 am
Subject: [Veritas-bu]  Duplicating Image
To: VERITAS-BU@mailman.eng.auburn.edu

>
> why not just write two copies inline?
>
>
>
>
> Roedy boy wrote:
> > Hi All,
> > Is there any change to duplicate image on tape to another tape
> using schedule/policy (not using vault). for exp : I want to run
> backup on 8pm and the duplicate the image on 10pm.
> >
> > Thanks
> > Roed
>
>
> +---
> ---
> |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





This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Duplicating Image

[Clausen, Matt R [EQ]]

If you're going straight to tape (i.e. not using disk staging) then you can use 
a Storage Lifecycle Policy to do this.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A Darren Dunham
Sent: Friday, October 17, 2008 10:50 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Duplicating Image

On Thu, Oct 16, 2008 at 07:33:40PM -0700, Roedy boy wrote:
> Is there any change to duplicate image on tape to another tape using
> schedule/policy (not using vault). for exp : I want to run backup on
> 8pm and the duplicate the image on 10pm.

I don't know any way to use the netbackup scheduler to do it.  Easiest
would be to use cron to kick off a bpduplicate job.

--
Darren
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] NBU cross-site

[Clausen, Matt R [EQ]]

I'm curious though From a Disaster Recovery perspective, are you 
replicating a master across sites to avoid the master server being the single 
point of failure? If so, what are you using to do it?


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew White
Sent: Tuesday, October 07, 2008 5:44 PM
To: Ed Wilts
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] NBU cross-site

I agree with Ed,

I have media servers scattered around the entire country without any issues.
On Fri, Oct 3, 2008 at 10:19 AM, Ed Wilts <[EMAIL PROTECTED]> wrote:
On Thu, Oct 2, 2008 at 3:56 PM, spaldam <[EMAIL PROTECTED]> wrote:
Second, I wouldn't run master/media servers across a WAN; especially since NOM 
has the ability to manage multiple Master servers from a centralized console.  
If you lose the WAN, you done and all you backups fail.

I disagree - we have media servers scattered in multiple locations connected to 
our main master and it's been working fine for a long time.  Simply put, don't 
lose the WAN - we have redundant paths to all of our locations with media 
servers.  If we lose WAN connectivity to our remote offices, they're in a world 
of hurt anyway and backups are the least of their problems.

--
.../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

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Vault licensing with 6.5

[Clausen, Matt R [EQ]]

Generally you license the number of drives in the library that will be 
participating in Vaulting operations.

The Base License gives you the Vault functionality plus 4 drives that can be 
used for vaulting purposes (in-line tape duplication, ejection, multiple 
catalog backups, etc.)
Each additional drive requires an additional Vault Tape Drive license.

The Unlimited License is just that, unlimited Vault Drives (but not 
Library-based Robotic Drives - you still need to license those separately).

Here are some examples on how I believe this works (I'm still setting this up 
myself since my company just purchased Vault):

If you had a single site, with a single library that has 4 drives in it. All 
you need is the Base License and you're done. Those 4 drives can be used for 
backup/restore functions and vault functions.

If you had two sites, each with a library that had 2 drives in it. All you need 
is the base license since 2 drives in one site are handled by half the base 
license and the other 2 drives are handled by the other half.

If you had multiple sites, each with multiple libraries, you could purchase the 
base license, then additional drive licenses to cover those drives that would 
get used for vault. So in my case, I have the base license + 2 additional drive 
licenses for one site, 2 more drive licenses for another site and 2 more for 
yet another site. This is independent of the robotic drive licenses which is 6 
for one site, 4 for another (2 libraries) and 4 for another (2 libraries).

Your best bet if you are still confused would be to talk to a Symantec Sales 
Rep. and they can walk you through what you would need licensing wise... but I 
think it's pretty straightforward once you understand that the base gives you 4 
drives to use, and then you purchase additional drives beyond that.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts
Sent: Tuesday, October 07, 2008 9:20 AM
To: Dean
Cc: List Veritas List
Subject: Re: [Veritas-bu] Vault licensing with 6.5

If I remember correctly, the Vault Base license includes either 2 or 4 tape 
drives.  You then license each tape drive that can participate in a vault 
operation beyond that.  It doesn't matter if you're actually duplicating or 
just ejecting.
On Mon, Oct 6, 2008 at 10:26 PM, Dean <[EMAIL PROTECTED]> wrote:

Does anyone know how licensing works for Vault with NBU 6.5 ?

I see there is a "VAULT BASE" license, then and "ADDITIONAL DRIVE"
license, as well as "UNLIMITED".

Is a Vault license required for each and every tape drive under the
master server and it's media servers, or is the number of licenses
required somehow tied to the Vault duplication process?

Thanks in advance,
Dean

.../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] Storage Lifecycle Policies

[Clausen, Matt R [EQ]]

SLPs can essentially mimic all the functionality of vault without the nice 
reports that vault can generate. Though in order to use them, you have to have 
"intelligent" hardware (VTLs, AdvancedDisk, Tape Libraries, etc.) instead of 
"dumb" hardware (BasicDisk).

You can pretty much craft the SLP to stage to disk, destage from disk, 
duplicate to disk or tape, etc. all from a single SLP and apply it to multiple 
policies. Kind of nice really, but disappointing that in order to use this 
feature you pretty much have to buy expensive hardware or add-on products.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Stewart
Sent: Thursday, August 28, 2008 5:28 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Storage Lifecycle Policies

I've been trying to play with a few of the newer features in 6.5 and was 
looking at storage lifecycle policies.

I've been playing with a test bed of 2 RHEL 4 with netbackup 6.5.2

1)  Has anyone see the error "Intermittent connectivity lost with server.  
Please..." with creating said lifecycle policies?

2) Assuming I can ever get he ability to create them how does this feature 
compare with say Vault?  Just to give you some background the plan would be to 
use VTLs on site and have the images duplicate to a remote facility over our 
SAN's WDM connection.


Steven

Steven Stewart
NC State University
OIT/Provisioning
___
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] Disc Staging Area Full

[Clausen, Matt R [EQ]]

It would be far better to do a catalog search for the images in question and 
have netbackup expire them immediately. Manually deleting the image files (even 
if they will expire in a few days) can have unintended consequences especially 
for catalog consistancy. Once the images are expired, NetBackup (if you're 
using 6.x anyways) should immediately launch an Image Cleanup job to delete the 
expired images. If you're using NetBackup 5.x they should be deleted after 
midnight (I believe that's when it does its cleanup).

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Crowey
Sent: Monday, August 25, 2008 11:34 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Disc Staging Area Full


A couple of weeks ago I had a synthetic backups snafu (which is fixed now) that 
meant it started doing a big differential dump to our disc staging area.

Like I said, snafu fixed, but images still there - and while due to expire in 
next day or two, I've run out of space now.

Can I safely delete these images manually?

+--
|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] sgscan cannot see robot after library power cycle

[Clausen, Matt R [EQ]]

Have you run a devfsadm? Also, what Solaris kernal are you running? There was 
an issue with a patch that basically destroyed the sg driver.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Karl Rossing
Sent: Friday, August 22, 2008 11:31 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] sgscan cannot see robot after library power cycle

T1000 S10U4 master

There was a power outage on the library and now sgscan cannot see the robot.
/dev/sg/c0t5l0: Processor: "SUN StorEdge 3120  D"
/dev/sg/c0t8l0: Disk (/dev/rdsk/c1t8d0): "SEAGATE ST33LSUN300G"
/dev/sg/c0t9l0: Disk (/dev/rdsk/c1t9d0): "SEAGATE ST33LSUN300G"
/dev/sg/c1t1l0: Tape (/dev/rmt/0): "HP  Ultrium 3-SCSI"
/dev/sg/c2t0l0: Disk (/dev/rdsk/c0t0d0): "ATA HITACHI HDS7280S"

I'm thinking of running
/usr/sbin/modinfo | grep sg
126 7bb72da8   1718  97   1  sysmsg (System message redirection (fan)
188  13d4320   35d0 285   1  sg (SCSA Generic Revision: 3.6)
232 7b7cc000   2168  49   1  msgsys (System V message facility)
232 7b7cc000   2168  49   1  msgsys (32-bit System V message facilit)
/usr/sbin/modunload -i 188
/usr/sbin/modload sg


The machine in question also servers up NFS home directories. I don't want 
those to drop.

Do you think that will bring the robot back? Are there side effects to doing 
this?

Karl













CONFIDENTIALITY NOTICE:  This communication (including all attachments) is 
confidential and is intended for the use of the named addressee(s) only and may 
contain information that is private, confidential, privileged, and exempt from 
disclosure under law.  All rights to privilege are expressly claimed and 
reserved and are not waived.  Any use, dissemination, distribution, copying or 
disclosure of this message and any attachments, in whole or in part, by anyone 
other than the intended recipient(s) is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately, 
delete this communication from all data storage devices and destroy all hard 
copies.
___
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] Calendar Schedules over Midnight & 6.5.2 issue

[Clausen, Matt R [EQ]]

It terminated because the next day is not a Run day. With a calendar backup, 
the checked day(s) denote the run day.

In the case you just asked about, if say Friday AND Saturday are checked 
this will lead to an intended or unintended consequence because if the job 
finishes on Friday, the checkbox on Saturday will launch a new job backing up 
the same policy.

Its always where the job STARTS that matters, not where it ends NetBackup 
will never cancel a job at the end of the window, only deny new ones from 
starting.

Matt Clausen
Network Systems Administrator
EMBARQTM
Voice: 850-847-0148  |  Wireless: 850-284-2435  |  Fax: 850-656-6133
Email: [EMAIL PROTECTED]
132 N. Calhoun St., Tallahassee, FL 32301
Mailstop: FLTLHI0101-AGENT
Voice | Data | Internet | Wireless | Entertainment
This e-mail is the property of EMBARQ and may contain confidential and 
privileged material for the sole use of the intended recipient(s). Any review, 
use, distribution or disclosure by others is strictly prohibited. If you are 
not the intended recipient (or authorized to receive for the recipient), please 
contact the sender and delete all copies of the message.

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Jorge Fábregas [EMAIL 
PROTECTED]
Sent: Thursday, August 21, 2008 9:42 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Calendar Schedules over Midnight & 6.5.2 issue

On Thursday 21 August 2008 09:21:45 pm Clausen, Matt R [EQ] wrote:
> The job queues, starts, runs into an issue and re-queues itself except this
> time doesn't get to start until after midnight Here is where the
> Retries Allowed after Runday checkbox comes in.

Thanks Matt for that wonderful explanation.  Just to clarify...  so what was
the real reason the job exited with status "196"?  because it reached the end
of the day (midnight) or because the next day wasn't a runday?

Imagine this same scenario..if Saturday is also a runday... will the queued
job exit at midnight with "196" (even though Saturday is runday) and then NB
will launch a new job at midnight right?

thanks,
Jorge
___
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] Calendar Schedules over Midnight & 6.5.2 issue

[Clausen, Matt R [EQ]]

The single most important thing to remember with calendar based backups is that 
after midnight, it's a new day

So consider these scenarios:

You have a backup job which kicks off every Friday, and the backup window opens 
at 6PM and closes at 6AM the following day.

The job queues, starts and finishes before midnight. You will get a Status Code 
0 (Successful Completion)

The job queues, starts and finishes well after midnight. You will get a Status 
Code 0 (Successful Completion) because the job started during the allocated 
backup window. Only starting a job matters with the window, not how long it 
runs... except in the next two cases.

The job queues, starts, runs into an issue and re-queues itself, starts and 
finishes before midnight. You will again get a Status Code 0.

The job queues, starts, runs into an issue and re-queues itself except this 
time doesn't get to start until after midnight Here is where the Retries 
Allowed after Runday checkbox comes in.

If that box is checked, then the job will start (provided it is not outside the 
6AM close of the backup window) and you will hopefully get a Status Code 0.
If that box is NOT checked, then your job will exit with a Status Code 196 (Job 
Not Attempted because backup window closed) regardless of the backup window 
closing at 6AM because with the calendar backup, the job can only run on the 
day its assigned to... unless that little box is checked.

Hope this clears things up a bit.

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Jorge Fábregas [EMAIL 
PROTECTED]
Sent: Thursday, August 21, 2008 9:06 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Calendar Schedules over Midnight & 6.5.2 issue

Hello everyone,

I'm new on this list and also starting with Netbackup so bare with me :)

As I was trying to understand what goes on when I have a calendar-based
schedule with a window that spans midnight I just found out there are some
issues with this & the latest 6.5.2.  Please check this scenario...

I perform a full-weekly on Friday (Friday is the only runday) and the window
goes from Friday 6pm until Monday 5am.  Assuming "Retries allowed after
runday" is unchecked and that by Friday midnight the job is still queued...
Will the job exit with a 196 exit-status at midnight?  Is this the behaviour
now with 6.5.2? Was it always like this?

I used to think that by entering the queue (at Friday 6pm) it was going to
stay there , even after midnight, just as long as it was within the window
timeframe AND because it was started on its runday..it would stay there even
though the next day wasn't a runday.  Apparently this changed in 6.5.2 (based
on what I've been reading) and it seems this is the correct behaviour ?

Thanks in advance,
Jorge
___
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] Windows 2008 Client

[Clausen, Matt R [EQ]]

I doubt it. The OS Compatibility Matrix says that for Windows 2008, the minimum 
client is 6.5.2... Now, you MIGHT be able to use 6.5.1, but I doubt it. I'm 
pretty sure that there will be code changes introduced with the 6.5.2 client 
that allows it to work under Windows 2008. If you have a dev-box around 
somewhere though that's Windows 2008 you can try the 6.5.1 client there to see 
if it works.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora
Sent: Tuesday, August 19, 2008 12:54 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Windows 2008 Client


I'm at 6.0 and was really hoping to upgrade to 6.5.1 next week and not very 
anxious to go to 6.5.2 just yet from what I'm reading.  The server team decided 
to start rolling out 2008 Server servers without checking for compatibility so 
now I have clients I can't backup.  Is there any other way besides upgrading to 
.2 to resolve this?
Thanks,
Randy

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] 6.5.2A media server with 6.5.1 master server

[Clausen, Matt R [EQ]]

According to both Symantec support and Symantec Education Services you can't 
run a media server at a higher patch revision then the master. The order of 
upgrading needs to be (in this order): master server(s) --> media server(s) --> 
client(s).

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Monday, August 18, 2008 3:38 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] 6.5.2A media server with 6.5.1 master server

I think we just ran into this issue:
http://seer.entsupport.symantec.com/docs/301175.htm
on one of my Windows SAN media servers. My master server is at 6.5.1, which 
leads me to ask, has anyone run a 6.5.2A media server with a 6.5.1 master 
server? I'd rather avoid messing with my master server at this point if I can 
avoid it, but need to resolve this issue on the Windows server.

  - Bluejay 
Adametz

In 1914 the first school of cosmetology opened. All the students had to take a 
make-up exam.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Media server installation

[Clausen, Matt R [EQ]]

Sure it does... he just said they were SCSI connected to the 3rd Media Server. 
So that being said, he would need to create a third robot instance which is 
defined as a remote robot and it would have the drives indexed as follows:

TLD(2): Remotely Controlled by Media Server #2:
Library Drive Index 1: Media Server 3 - Drive #1
Library Drive Index 2: Media Server 3 - Drive #2
Library Drive Index 3: Media Server 3 - Drive #3
Library Drive Index 4: Media Server 3 - Drive #4

So when NetBackup executes a job requiring usage of Media Server #3, it knows 
the robot is controlled by media server #2 and that the drives are controlled 
by media server #3. This robot can then be added to Storage Unit groups or 
policies, etc


From: Ed Wilts [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 1:00 PM
To: Clausen, Matt R [EQ]
Cc: [EMAIL PROTECTED]; veritas-BU
Subject: Re: [Veritas-bu] Media server installation

On Mon, Aug 18, 2008 at 11:53 AM, Clausen, Matt R [EQ] <[EMAIL 
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Well, why can't he set something up like this:

Media Server #1: Library Control + 4 Drives
Media Server #2: Library Control + 4 Drives
Media Server #3: 4 Drives with Media Server #2 being the remote host 
controlling the library

You don't need anything special to do this (such as the SSO). Matter of fact, 
the Veritas Class I just got done taking has this exact setup (Quantum M1500 
library with two drives, each drive controlled by a UNIX server with one of the 
servers being the robot control host) and we didn't have anything special 
beyond the base NetBackup installation.

Media Server #3 has no physical access to the DRIVES that Media Server #2 sees. 
 Sure, NetBackup can tell MS # 2 to mount a tape, but MS # 3 has no path to the 
actual tape devices.  This goes beyond the "robot control host" functionality.



From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL 
PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Ed Wilts
Sent: Monday, August 18, 2008 11:25 AM

To: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>
Cc: veritas-BU

Subject: Re: [Veritas-bu] Media server installation

On Mon, Aug 18, 2008 at 10:12 AM, <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> 
wrote:
My Tape drive is directly conected to media server thru scsi cable.

There's not much hope of a different media server being able to write to these 
tape drives.  If you want a system to share tape drives, you need some sort of 
physical connection between the media server and the tape drives.

If you have a SAN but don't have your tape drives SAN connected, you could 
consider a fibre to SCSI bridge and share those tape drives.  If you don't have 
a SAN at all, the costs probably aren't justified.


"Ed Wilts" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>

18/08/2008 16:01


To
[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>
cc

veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>
Subject
Re: [Veritas-bu] Media server installation







On Mon, Aug 18, 2008 at 9:13 AM, <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> 
wrote:

We have master server with Netbackup enterprise 6.0 running on  solaris 8 & two 
media server having two HPESl 9300 series tape library with four drive in each 
Library.

We want to add now four drive in our our existing Library & connect it to third 
media server.

Please let me know is that possible.

Will this 3rd media server have direct access to the tape drives?  In other 
words, are the tape drives SAN-connected or are they SCSI connected to the 
existing media servers?

If the tape drives are SAN-connected, then what you want to do is fairly 
straight-forward.  You need to purchase the Shared Storage Option licenses and 
then you would configure the tape drives to use the right robot control hosts.  
You can dedicate tape drives to media servers - one way to do this is to use 
SAN zoning.


.../Ed

Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Media server installation

[Clausen, Matt R [EQ]]

Well, why can't he set something up like this:

Media Server #1: Library Control + 4 Drives
Media Server #2: Library Control + 4 Drives
Media Server #3: 4 Drives with Media Server #2 being the remote host 
controlling the library

You don't need anything special to do this (such as the SSO). Matter of fact, 
the Veritas Class I just got done taking has this exact setup (Quantum M1500 
library with two drives, each drive controlled by a UNIX server with one of the 
servers being the robot control host) and we didn't have anything special 
beyond the base NetBackup installation.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts
Sent: Monday, August 18, 2008 11:25 AM
To: [EMAIL PROTECTED]
Cc: veritas-BU
Subject: Re: [Veritas-bu] Media server installation

On Mon, Aug 18, 2008 at 10:12 AM, <[EMAIL PROTECTED]> 
wrote:
My Tape drive is directly conected to media server thru scsi cable.

There's not much hope of a different media server being able to write to these 
tape drives.  If you want a system to share tape drives, you need some sort of 
physical connection between the media server and the tape drives.

If you have a SAN but don't have your tape drives SAN connected, you could 
consider a fibre to SCSI bridge and share those tape drives.  If you don't have 
a SAN at all, the costs probably aren't justified.


"Ed Wilts" <[EMAIL PROTECTED]>

18/08/2008 16:01


To
[EMAIL PROTECTED]
cc

veritas-bu@mailman.eng.auburn.edu
Subject
Re: [Veritas-bu] Media server installation







On Mon, Aug 18, 2008 at 9:13 AM, <[EMAIL PROTECTED]> 
wrote:

We have master server with Netbackup enterprise 6.0 running on  solaris 8 & two 
media server having two HPESl 9300 series tape library with four drive in each 
Library.

We want to add now four drive in our our existing Library & connect it to third 
media server.

Please let me know is that possible.

Will this 3rd media server have direct access to the tape drives?  In other 
words, are the tape drives SAN-connected or are they SCSI connected to the 
existing media servers?

If the tape drives are SAN-connected, then what you want to do is fairly 
straight-forward.  You need to purchase the Shared Storage Option licenses and 
then you would configure the tape drives to use the right robot control hosts.  
You can dedicate tape drives to media servers - one way to do this is to use 
SAN zoning.


.../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] NBU 6.5.1 - Queued DSSU Duplications

[Clausen, Matt R [EQ]]

I actually had a call with Symantec on this issue a few weeks ago The 
destaging job would start, get maybe a few sub-jobs in and then just hang (or 
exit with a Status 50). To make a long story short, I had to do some DB stuff 
with Symantec Backline Support on the phone and apply 6.5.2 in order to correct 
the issue (this problem surfaced after we applied 6.5.1).

Your mileage may vary, but applying 6.5.2 (not 6.5.2A) to the master/media 
server fixed the issue for us.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts
Sent: Friday, August 15, 2008 10:51 AM
To: Martin, Jonathan
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] NBU 6.5.1 - Queued DSSU Duplications

On Fri, Aug 15, 2008 at 9:28 AM, Martin, Jonathan <[EMAIL 
PROTECTED]> wrote:

NBU 6.5.1 on Windows 2003 SP2

I've been running 6.5.1 stable at my main site now since it came out and
over the past three weeks I've have several DSSUs that would queue up
duplication jobs but never run them, despite drives being available.

Log a call with Symantec on this one.  We use DSSUs extensively on both Solaris 
and Windows with a Solaris master and have not seen this issue with 
6.5.1.  There was a bug with destages not working in 6.5.2A but 
an EEB is available for that.  I checked our internal changelog and can't find 
us installing an EEB for 6.5.1 for destages.
.../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] MPT driver and SG

[Clausen, Matt R [EQ]]

Is the SL24 the FC or SCSI one? Generally though once the device is available 
to the OS, NetBackup should be able to use it. The MPT Driver problem listed 
here is more of a Solaris 10 issue then a Solaris 8 issue, so you should be 
fine.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Markham
Sent: Tuesday, July 22, 2008 7:44 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] MPT driver and SG

Does anyone know where i can find compatibility with a new Sun SL24 unit and 
Netbackup v5.0MP7 on Solaris 8. I'm having no joy on the sunsolve site. Will 
the normal sg driver be able to see it? It will be using LTO3 drives.


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Strange schedule problem

[Clausen, Matt R [EQ]]

I remember running into a problem when I was still running 6.0 (MP1 or 2 - been 
awhile) where it would just stop doing scheduled jobs out of the blue. This was 
a standalone master/media server, but in order to get it working again I had to 
stop/start all the NetBackup processes. I ended up scheduling via cron a job to 
do that just to keep the backups running until I could upgrade to NBU 6.5 
(which didn't have this problem).

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Markham
Sent: Thursday, July 17, 2008 9:05 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Strange schedule problem

Guys i have Master server (NBU 6.0MP4) and a number of media servers and 
clients.

One media server which is SSO Media server sharing drives is NBU 5.0MP7 and has 
been fine but all of a sudden as stopped automatically running backups. We can 
run manual ones fine but its as though the scheduling system isnt working for 
it or something.  Anyone any pointers as to where to look?

There isn't a bpsched log directory on the master server with NBU6 so i'm a bit 
stuck.

Everything else is working ok.

Cheers

This is all on Solaris, and please no need for replies with "Why not upgrade to 
6 on the media server" i know i know and i'm trying to get it passed by service 
management.


___
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] Unable to write to both drives

[Clausen, Matt R [EQ]]

I just ran into something similar. I had a Storage Unit Group that consisted of 
two libraries with two tape drives each, but only one library would ever get 
used. I ended up having to remove all the Storage Unit Groups that had these 
libraries in them, recreate them and then make sure the policies were set to 
this new group.

After doing this, the problem went away.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Honeybrook, Kate
Sent: Wednesday, July 16, 2008 1:45 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Unable to write to both drives

Hi All,

We are having a problem with our tape drive since the library was replaced and 
Symantec haven't been able to provide much assistance. We are running netbackup 
6.5 on a windows master server and separate windows media server. Basically our 
robot died, so they replaced it but left the same tape drives in the library. 
We have configured netbackup to pick up the new library, and it still sees the 
existing drives. We can see all drives using the tpconfig -d. Our problem 
occurs when we try and run multiple jobs, it wont write to both libraries. The 
jobs wait with:

requesting resource gisvw-granite.cs.adi-limited.com.NBU_CLIENT.MAXJOBS
requesting resource gisvw-granite.cs.adi-limited.com.NBU_POLICY.MAXJOBS
awaiting resource NDMP-Backup-Storage-Group - Maximum job count has been 
reached for the storage unit

We have been on the phone to Symantec for some time trying to get these 
working, but there suggestions have not helped at all. Our storage unit is 
configured to use 2 concurrent drives. However it wont use both drives. We have 
tested and it can write to each drive individually but not both at the same 
time.

If anyone has any suggestions on what we could do they would be greatly 
appreciated.

Kate Honeybrook
Systems Administrator



DISCLAIMER:---
 This e-mail transmission and any documents, files and previous e-mail messages 
attached to it are private and confidential. They may contain proprietary or 
copyright material or information that is subject to legal professional 
privilege. They are for the use of the intended recipient only. Any 
unauthorised viewing, use, disclosure, copying, alteration, storage or 
distribution of, or reliance on, this message is strictly prohibited. No part 
may be reproduced, adapted or transmitted without the written permission of the 
owner. If you have received this transmission in error, or are not an 
authorised recipient, please immediately notify the sender by return email, 
delete this message and all copies from your e-mail system, and destroy any 
printed copies. Receipt by anyone other than the intended recipient should not 
be deemed a waiver of any privilege or protection. Thales Australia does not 
warrant or represent that this e-mail or any documents, files and previous 
e-mail messages attached are error or virus free. 
--
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Master/Media server input

[Clausen, Matt R [EQ]]

I've seen a couple of whitepapers out there on them, but the Sun Enterprise 
T5220 servers seem to scream as a media server. I'm actually redoing my 
NetBackup environment as well and I'm going to a Dedicated Master Server + 3 
Media Servers (each Media server in a different location).

My master server is going to be a reused Sun SunFire v440 to handle all the 
Database operations necessary on the master server. The media servers are going 
to be all T1/T2 based servers because of their superior I/O handling over the 
USIIIi/USIV/USIV+ (not to mention they're cheaper then those class of machines).

One media server is going to have 6 4Gb/s FC HBAs running, one will have 4 
HBAs, and the last one will 4xU320s.

Master Server will be Solaris 10 (SPARC)
Media Servers will be mixed (two will be Sol10 SPARC and one will be a 
Sol10_x64 server)

If you do go with Solaris, I cannot stress this enough... Disable tcp_fusion! 
Disable tcp_fusion! Disable tcp_fusion!

This little vixen was responsible for a big list of headaches with tape 
duplication, catalog backups failing, etc.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Dyck
Sent: Thursday, July 10, 2008 4:11 PM
To: Veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Master/Media server input

Hi all,

Looking to replace some old hardware with shiny and new.  Wondering if anyone 
out there had some commentary on anything idiotic I may be putting down as my 
requirements ;-)

Backup software to be used:  Symantec Enterprise Netbackup 6.5, we'll be 
procuring 1 master server, and 2 media servers to drive a total of 600 MB/s 
aggregate to a Diligent Protectier VTL.

OS Options (any will do):
- Solaris 10 for SPARC for both Master/Media
- Solaris 10 for x86 for both Master/Media
- RedHat Linux Enterprise 4 for x86 for both Master/Media

NIC requirements (per master/media server):
- ~200 MB/s aggregate throughput required (real-world)
- Suggesting 4x1 GigE NICs (single team) with offload engines

HBA requirements (per master/media server):
- ~2x200 MB/s aggregate throughput required (two separate buses, one for read, 
one for write, yes we still duplicate to LTO3 physical tape)
- Either two single port 4GB HBA's or one dual-port 4GB HBA's

Bus requirements:
- 1 independent PCI-E (x2) bus at minimum for each single-ported 4gb HBA
- 1 independent PCI-E (x4) bus at minimum for a dual-ported 4gb HBA
- 1 independent PCI-E (x8) bus at minimum for a quad GigE w/ offload engines

Internal Disk Requirements:
- One raid-set of 500 GB of Raid 1+0 (usable), probably 10k SAS, for Netbackup 
catalogs on master server only
- A raid-set of 100GB of Raid 1+0 (usable), probably 10k SAS, for OS/other 
application data on media and master

Memory Requirements:
- 12GB for the master server
- 4GB for a media server

CPU Requirements:
- Equivalent of four dual-core CPUs for the master server
- Equivalent of two dual-core CPUs for the media servers

Thoughts (Paul Keating stay of it ;-)?

Cheers,
Jon


La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of Canada does not waive any related rights. Any distribution, use, or copying 
of this email or the information it contains by other than the intended 
recipient is unauthorized. If you received this email in error please delete it 
immediately from your system and notify the sender promptly by email that you 
have done so.



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il 
contient par une personne autre que le ou les destinataires désignés est 
interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer 
immédiatement et envoyer sans délai à l'expéditeur un message électronique pour 
l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu.

___
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