Re: [Veritas-bu] Media Server Issue

Dave Well I had a similar issue to this, and my only resolution was to stop all Netbackup Services, power down the robot, then from Windows Device Manager ensure the drives are robot were removed from each media server. Then power the robot back online, then from each media server, run the

Re: [Veritas-bu] Media Server Issue

On Wed, 18 Jul 2007, Clooney, David wrote: Hi All We have a unusual situation going which maybe some of you have come across? Environment - all 5.1 MP5 Mater - Solaris 8 Media Servers - winodws2000/2003 On Friday we started to experience numerous Status 52: timed out waiting

Re: [Veritas-bu] Media Server Issue

Thanks Simon What was the issue you where experiencing? , what I find bizarre is that this is even occurring whilst netbackup is down on this media server ? Dave From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: 18 July 2007 11:31 To:

Re: [Veritas-bu] Media Server Issue

Dave Status 52, status 11, Status 13 - happened on backups or Catalog backups. Narrowed down to one drive, but even so, to correct the SCSI issue on the Media Server, had no choice to go via the route I did! drastic and annoying, but hey it sorted it all out ! Regards Simon Weaver 3rd

[Veritas-bu] Media Server Issue

Hi All We have a unusual situation going which maybe some of you have come across? Environment - all 5.1 MP5 Mater - Solaris 8 Media Servers - winodws2000/2003 On Friday we started to experience numerous Status 52: timed out waiting for media manager to mount volume. After a

Re: [Veritas-bu] Max # of Drives on a Master Server?

In my environment the master server does all the vaulting. Which means I need access to all robots/drives in my environment. Every Media server is just a SAN Media server and also a production server. I am nervous about what might happen with IO on the SAN Media servers, if I allow them to

Re: [Veritas-bu] ALL_LOCAL_DRIVES not working?

I've had this issue where there's a problem with connectivity (e.g. firewall) between the master and the client, but the (different) media server and the client can talk to each other correctly. It's like the master can't query the client to find out what filesystems need backing up, but the

[Veritas-bu] Library changed

Hello, Our current libraries (a Sun L25 and a Sun L700), are configured so that they do NOT show the Media Type suffix when NetBackup 5.1MP6 does an inventory. So a tape with a physical label of AB0123L2 shows as AB0123 and no NetBackup media ID generation rules are required. In a DR situation,

Re: [Veritas-bu] HP LTO3 media on IBM 800GB LTO3 Tape drive?

good morning. just last week i was running a dr scenario in which i was told that the lto 3 drives where hp's but netbackup showed that they were ibm's gen 3. i did not encounter any problems reading data off the tape with ibm's lto gen3 drive, which were written by hp's lto gen3 at home.

[Veritas-bu] NBU 5.1MP6 x86 Client Issues

Folks, I'm working on getting our Exchange Servers to do file/system backups now and have to use the 5.1MP6 x86 client. I've gotten them installed and set up in a policy. However, I've noticed several oddities: 1. Most jobs are returning 41s. I've kicked up logging and respawned jobs,

[Veritas-bu] NBWin - 5.1MP5 Veritas logo spins forever [C1]

Solaris master and 4 media servers plus 1 W2K serverdedicated for restores of Windows, Lotus Notes servers and NAS directories off the NetApp. NDMP agent on one of the media servers to NetApp. NBWin ( Backup, Archive and Restore Windows GUI ) is hanging forever, showing the spinning Veritas

Re: [Veritas-bu] Media Server Issue

I think I had a similar issue at one time and found that one of the media servers didn't have the correct entry in 'Maximum multiplexing per drive'. We had 8 drives and it was set for 4. This media server was becoming the SCAN_HOST (vmdareq -a) on some drives from time to time and caused some

Re: [Veritas-bu] Library changed

[EMAIL PROTECTED] # /usr/openv/volmgr/bin/vmupdate -rt tld -rn 0 Generating list of recommended changes ... Proposed Change(s) to Update the Volume Configuration = Logically add new media AB0123 (barcode AB0123L2) to robot slot 1.

Re: [Veritas-bu] ALL_LOCAL_DRIVES not working?

Connectivity is fine between the server and client (actually on the same subnet at this point). I'm just seeing really strange results related to the policy database. If I create a new policy using the ALL_LOCAL_DRIVES, it just backs up the root partition. If I manually list the individual

[Veritas-bu] End of Life dates for 5.0 and 5.1

This documented was published July 16, 2007 and addressed to Symantec Customers http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Ser ver/290017.pdf End of life Start Date: October 5, 2005. New Date for End of Standard Support and Start of Partial Support: March

Re: [Veritas-bu] ALL_LOCAL_DRIVES not working?

John, Have you done some configuration in the include/exclude that is causing this overriding feature? Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman -Original Message- From: [EMAIL