[Veritas-bu] Netbackup socket write failed what mean???

2009-06-12 Thread men duffy
We have Netbackup 6.5 on server and client. Every two to three days log file have following messages and backup failed: 5:28:42.502 [27407] 16 flush_archive(): ERR - Cannot write to STDOUT. Errno = 104: Connection reset by peer 05:28:42.520 [27407] 16 bpbkar Exit: ERR - bpbkar FATAL

Re: [Veritas-bu] Netbackup Exam ??

2009-06-12 Thread Ed Wilts
On Fri, Jun 12, 2009 at 12:47 AM, Sabar Martin Hasiholan Panggabean sabar.hasiho...@metrodata.co.id wrote: Does anyone has link/information where to get pdf questions for these exam: Exam 250-365: Data Protection Administration for Windows using NetBackup 6.5 Exam 250-265: Data

Re: [Veritas-bu] Using multiple drives with NDMP.

2009-06-12 Thread Rusty.Major
For the policy you want to multi-stream, is the Allow Multiple Streams box checked in the Policy Attributes? Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693 Keeping People and Information

[Veritas-bu] Backing up cluster after failover

2009-06-12 Thread smwoodcrafts
No, the physical nodes are 1a and 1b, the cluster is vir1. The active node on the cluster was 1a, then it failed over so the active node was 1b. We then started getting the 71 error. We are only backing up the shared resource. If I go to client proterties on the master server, the client name

Re: [Veritas-bu] Backing up cluster after failover

2009-06-12 Thread Len Boyle
Are there more then one cluster group. We found that we would be given a cluster name, but there might be 3 or 4 different groups that could move between the physical nodes. So we might have vir1 and group2 on node 1a and group3 on node 1b. Which would then lead to the 71 errors and netbackup

Re: [Veritas-bu] Backing up cluster after failover

2009-06-12 Thread Ed Wilts
On Fri, Jun 12, 2009 at 9:48 AM, smwoodcrafts netbackup-fo...@backupcentral.com wrote: No, the physical nodes are 1a and 1b, the cluster is vir1. The active node on the cluster was 1a, then it failed over so the active node was 1b. We then started getting the 71 error. We are only backing up

Re: [Veritas-bu] Using multiple drives with NDMP.

2009-06-12 Thread Jeff Cleverley
rusty.ma...@sungard.com wrote: For the policy you want to multi-stream, is the Allow Multiple Streams box checked in the Policy Attributes? Yes. I've stopped and started all processes several times just to make sure all changes are getting loaded also. Jeff *Rusty Major, MCSE, BCFP,

[Veritas-bu] Backing up cluster after failover

2009-06-12 Thread smwoodcrafts
ewilts wrote: On Fri, Jun 12, 2009 at 9:48 AM, smwoodcrafts netbackup-forum at backupcentral.com (netbackup-forum at backupcentral.com) wrote: The client name set on the host is actually irrelevant - it's only used when you want to do a restore. On your Windows cluster, you want

[Veritas-bu] Backing up cluster after failover

2009-06-12 Thread smwoodcrafts
It might be easier, because I'm new to this and probably not explaining it correctly, to just ask what are the correct steps when configuring for backup of the floating drives in a cluster. There has to be something I missed. This would be an all Windows environment and I would need steps on

Re: [Veritas-bu] Backing up cluster after failover

2009-06-12 Thread Ed Wilts
On Fri, Jun 12, 2009 at 10:34 AM, smwoodcrafts netbackup-fo...@backupcentral.com wrote: ewilts wrote: On Fri, Jun 12, 2009 at 9:48 AM, smwoodcrafts netbackup-forum at backupcentral.com (netbackup-forum at backupcentral.com) wrote: The client name set on the host is actually

Re: [Veritas-bu] Backing up cluster after failover

2009-06-12 Thread judy_hinchcliffe
I don't think you are seeing the picture. Go into your windows server and cluster admin. Now look at your resources and find the virtual name of the server that owns that resource. This is NOT a physical server name. Example when you go into cluster Administaff Inc. You see a folder called

Re: [Veritas-bu] Backing up cluster after failover

2009-06-12 Thread Robin Small
I think you mentioned database cluster in an earlier post? here's how I have my sql cluster set up: physical node hostnames: sql1 (192.168.0.1) sql2 (192.168.0.2) cluster node hostname: sqlclus (192.168.0.3) I have two policies for my sql cluster (well, *I* have more than two, but for the

Re: [Veritas-bu] Backing up cluster after failover

2009-06-12 Thread Kendall, Scott
You say they are writing to (and you're trying to backup) a floating drive and that you've defined vir1 in your backups. Your vir1 must not be in the same Cluster Group as the resources you're trying to back up. I'm guessing you're trying to backup the Network Name resource called Cluster

Re: [Veritas-bu] Using multiple drives with NDMP.

2009-06-12 Thread Jeff Cleverley
The clients max job was set to 1. I changed it to 10 for now. The policy with 3 file systems in the includes grabbed 3 drives and started writing. Performance now needs to start getting tuned to see what we can get but at least I can use all the drives. Thanks, Jeff Jon Bousselot wrote:

[Veritas-bu] More tapes than cap space on eject

2009-06-12 Thread scott . george
All, I have a NBU 6.5.3.1 server running AIX. and a STK SL8500 Library with dual 39-slot caps, driven by ACSLS. Our vault jobs are to the point where they are consistently more than 78 tapes, and when the deferred ejects are performed, the remaining x-78 tapes will not eject. We just

Re: [Veritas-bu] More tapes than cap space on eject

2009-06-12 Thread Rusty.Major
We aren't sending that many tapes offsite, but I do have similar issues with the ACS libraries hanging in eject mode until the cap is emptied and then closed in an empty state. I really hate this operation, btw, but we utilize the eject notification to email the operators to inform them they

Re: [Veritas-bu] More tapes than cap space on eject

2009-06-12 Thread scott . george
No, they are right on it, because they initiate the eject with the deferred eject. What happens is the vault runs and does all of its dupes and the finishes without ejecting anything. When they notice the vault is done, they expand out Vault Management down to the job itself and right click

[Veritas-bu] Backing up cluster after failover

2009-06-12 Thread smwoodcrafts
I just checked with the owner. Everything is in the same cluster group. I did find out that F: resides on our SAN. It's not physically in one of the servers. Ownership changes with a failover the the newly active node. Any more ideas? It's clear I'm not understanding this.

Re: [Veritas-bu] Backing up cluster after failover

2009-06-12 Thread judy_hinchcliffe
Cannot send screen shots via this mail group. Send me your email address and I will try to do screen shots to 'show' you what we are talking about. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of

[Veritas-bu] Backing up cluster after failover

2009-06-12 Thread tburrell
I'll take a stab at it: Don't think drives think groups Remember that Windows Cluster drives do not float around on their own- they are part of a Cluster Group. That group also includes IP addresses- you can and should have a dedicated backup IP address for each Cluster Group that resolves

Re: [Veritas-bu] More tapes than cap space on eject

2009-06-12 Thread Conner, Neil
I only have experience with SCSI-controlled TLD and TL8 libraries, but this might be useful... Try ejecting a large batch of tapes manually and see how it behaves when the cap fills: vmchange -multi_eject -w -res -ml $EJECT_LIST -rt $ROBOT_TYPE \ -rn $ROBOT_NUM -rh $ROBOT_HOST You can

[Veritas-bu] Steps to add a new media server

2009-06-12 Thread Mike Kiles
I am looking for brief steps to add a brand new server to existing Netbackup 6.5.3 environment, all windows 2003 servers. Thanks. __ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now