Re: [Veritas-bu] Special Tapes to policies

2010-02-20 Thread Ed Wilts
One way to solve this problem is to use encryption.  Use a key-per-tape
procedure and when the tape images expire, destroy the key.  There will be
no way to ever get that data back and the tape can sit in your scratch pool
for years.

   .../Ed

On Fri, Feb 19, 2010 at 4:01 PM, bruceephx 
netbackup-fo...@backupcentral.com wrote:


 I'll give a reason for using specific tapes, litigation discovery.  Our
 email backups need to go to specific tapes so that the tapes are reused
 within 24 hours of the image(s) expiring.  If you used scratch tapes, when
 the image expires the data is still on the tape, it can be re-imported and
 recovered.  We have many dozen scratch tapes, so the email backups could
 exist for weeks after the images expire.

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


[Veritas-bu] Any gotchas with 10 GB Ethernet?

2010-02-20 Thread Larry

Oh yeah, and if you haven't bought the servers yet, Sun has some with dedicated 
busses for 10Gb NICs.  Haven't played with them yet, but it's definitely worth 
considering.  I want to say the 5240 has them while the 5220 doesn't.

+--
|This was sent by la...@hawkeyes.org 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] Incremental Backups.

2010-02-20 Thread Larry

If you mean your incremental backups and full backups in the same policy are 
going to different targets, then check the schedules and one or more will be 
set to override the storage unit set for the policy.

+--
|This was sent by la...@hawkeyes.org 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] Any gotchas with 10 GB Ethernet?

2010-02-20 Thread Larry

I don't know if this has changed since 5.1, but at 5.1 and earlier you would 
need to use /usr/openv/netbackup/NET_BUFFER_SZ (yes, SZ) and put a value 
greater than 64KB in there.  It really doesn't matter what you use, unless 
you're going over a LFN, 1048576 will work in most cases.  It's not like making 
it too big is going to hurt anything.  And, contrary to an old rumor, it is not 
nor has it ever been necessary to set this value to the same thing on client 
and server.

Most people won't see any affect at all by doing this (unless you're running 
really old NBU and doing duplication) until they get to about 4x trunked Gb or 
higher.

+--
|This was sent by la...@hawkeyes.org 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


Re: [Veritas-bu] Any gotchas with 10 GB Ethernet?

2010-02-20 Thread Shekel Tal
I haven't followed the whole thread so excuse me if my message isn't
relevant but I read in a performance tuning guide you should set your
NET_BUFFER_SZ to 4 times the size of your SIZE_DATA_BUFFERS

Also - not mandatory but recommended to match the client and media
server network buffers

The feature is very useful for high latency lan/wan links where you will
definitely see a difference. I have also used and tested it with jumbo
frames which yielded significantly improved results (although jumbo
frames on their own will make a big difference)

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Larry
Sent: 20 February 2010 02:10
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Any gotchas with 10 GB Ethernet?


I don't know if this has changed since 5.1, but at 5.1 and earlier you
would need to use /usr/openv/netbackup/NET_BUFFER_SZ (yes, SZ) and put a
value greater than 64KB in there.  It really doesn't matter what you
use, unless you're going over a LFN, 1048576 will work in most cases.
It's not like making it too big is going to hurt anything.  And,
contrary to an old rumor, it is not nor has it ever been necessary to
set this value to the same thing on client and server.

Most people won't see any affect at all by doing this (unless you're
running really old NBU and doing duplication) until they get to about 4x
trunked Gb or higher.

+--
|This was sent by la...@hawkeyes.org 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] Can't upgrade past windows netbackup client 6.0

2010-02-20 Thread David Stanaway
I just had a problem with this same error on a windows 2000 client. This
was on a new 6.5 install.

At the very end of the install, the installer connected to the windows
event logs through WMI I think but this failed due to WMI repository
being corrupted somehow. The install rolls back at this point.

The problem was with the WMI Registry which needed to be rebuilt. I can
send you instructions if you need. It was relatively painless but needed
a reboot of the client.

On 2/19/2010 5:57 PM, zimmy00 wrote:
 I have over 300 clients out there and out of those I can't seem to get a 
 handful of them upgraded past 6. Now I know that unlike 6 and before, 6.5 
 requires communication with the server, however there are no firewalls in the 
 way. And the servers backup with no problem with the older clients installed. 
 The only error I see in the logs is Failed to connect to server. Error: 
 0x800401F0 and of course during the install the app says Installation was 
 interupted. 

 I know it's not the master servers since they have no problem getting to 
 other clients. DNS is not an issue because the master is a unix server and I 
 use the hosts table. And as stated there are no firewalls in between. Anyone 
 have any idea's because I can't think of anything else.

 This is happening on both 2000 and 2003 clients, I have ran it locally and 
 tried to push it from another client.  I have ran it as administrator (run 
 as) and as an adminstrator account.  There is no UPS software on these 
 servers (only article I could find on it).

 +--
 |This was sent by steve.s...@compucom.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