Search results for query: *

This seems to be a harmless error http://seer.support.veritas.com/docs/283084.htm exerpt below: Etrack Incident = ET528354 Description: After applying NetBackup 5.1 MP4 the problems report showed "SO_REUSEADDR failed, errno = 0, No error". Additional Notes: This error is...

What was the slight mistake, I would finfd this script useful if you have it working thanks

Imagine you are doing a restore of a mission critical database. The restore takes 10 hours to complete. At hour 9.5 the restore fails and you discover that there is a bad block on the tape. Now you have just lost 9.5 hours on the restore, and you have to go back to an older instance of the...

Maybe the default in Solaris is to use the 1st NIC address it finds to send data out to a subnet unless you tell it to use a different NIC In windows you can force traffic to go out a particular NIC based on IP addresses by creating a persistant route on the server: Example: Define a route on...

I found this to be very useful: http://support.veritas.com/docs/270101

The Vnetd option enables backup through a fire wall. You do have to open a port to come in on it is all explained in the TID. http://support.veritas.com/docs/251630 Thsi is also covered in the Admin Guide.

Have you thought about teaming the NICS and the ports they attach to on the switch? Compaq refers to this as Switch Assisted Load Balancing. Heres a white paper: ftp://ftp.compaq.com/pub/products/servers/networking/TeamingWP.pdf Page 21 is similar to my set up. This is actually how my...

did you flush the dns cache on the servers after you made the change?

I had this issue too. We mistakenly had a _B appended to the Master/Media server name for the IP on the backup network. The clients refused the connection every time. They knew about MasterServer and MediaServer. They did not know about MasterServer_B or MediaServer_B, and NBU did not know...

Are you running Veritas Backup Exec Compression? If so shut that off and let the tape drive handle the compression, that could be whats slowing you down.

I am running all w2k master and media servers. I have Netware clients that are multihomed and use the backup network. I will double check all my name resolution related configs in case I have missed something really obvious. Maybe it is not a name resolution issue. In your case the client is...

Before buying new hardware you should validate that you do not have a bottleneck somewhere that is preventing the tape drive from running at full speed. You can expect 11-15MBps on LTO1 and faster w/ compression depending on the type of data and file characteristics. There are many factors...

yes it would be overwritten..if you have "allow media overwrite"set up to allow it to overwrite TAR

You should not have to format tapes in order for NBU to use them. There is a paramater under host properties on the master and media servers, "allow media overwite" where you specify what tape formats NBU can overwrite, otherise NBU will not overwrite these tapes. How to configure this is...

Below is a similar configuration to the one that I use. The Master server is also a media server. The backup network is non routable. master1 10.10.1.1 pub 10.10.2.1 backup 10.10.2.2 backup 10.10.2.3 backup hostfile: client1B 10.10.2.5 client2B 10.10.2.6 client3B...

Did you select "eject media after job completes", that would cause BE to eject the tape when the job is done if that is whats hapening, or you could have a tape that belongs to a media set other then the one the job is using, or the tape could be full, or the job could be set to overwrite and...

We have the same setup. Clients w/ large amounts of data are connected to the backup network, clients with small amounts of data are only on the public network, the media servers are connected to both networks. There is a setting "Required Network Interface" It might help. Look into trying...

When was the tape drive last cleaned? Cleaning often makes this error go away.

I have a private backup network and each media server is connected to it and the Public network as well. To force the clients to use the backup network and not the public network I edited the host file on the clients and associated the master/media server with IP of the NIC connected to the...

Check your media overwrte protection settings, sounds like you have it set to "Full", setting to "Partial" should resolve the issue for you. from the help menue search for "media overwrite" and it is all explained w/ instructions on how to configure.