06-02-2009
How to configure netbackup client in Solaris 9 & 10
Hi Experts
Though I am aware that I am asking some thing which I should not ask here, however I am sure that there are many who must be have configure netback client in solaris 9 and 10.
Please help /direct me towards some link as how and what all is required to configure Veritas netback client.
Thanking in anticipation
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Is it possible to configure the Solairs (2.6) mail client to get it's email from an MS Exchange server ? If so can soemone point me in the right direction.
Thanx
:confused: (5 Replies)
Discussion started by: ianf
5 Replies
2. Solaris
can someone please through light on how to configure video and nic.
Dimension 3000 Series, Intel Pentium 4 Processor at 2.8GHz
256MB DDR SDRAM at 400MHz EA 0.00 0.00
17 in (17 in viewable) E173FP Flat Panel Display EA
Integrated Intel Extreme Graphics 2 EA
Intel Pro 100M Integrated... (4 Replies)
Discussion started by: Jimmpy
4 Replies
3. Solaris
I hope someone out there can help. I'm trying to install & configure Openssh to my Solaris, I downloaded & Installed the following pkgs :
openssh-4.4p1-sol8-sparc-local.gz
openssl-0.9.8d-sol8-sparc-local.gz
tcp_wrappers-7.6-sol8-sparc-local.gz
zlib-1.2.1-sol8-sparc-local.gz... (6 Replies)
Discussion started by: Remi
6 Replies
4. Solaris
Hi,
Anyone know netbackup 3.4 on Solaris 8 .
Currently I use root to perform backup / monitoring ...etc .
Can I create a user call "backup" and perform the same task
What permission should I give the "backup" user . (1 Reply)
Discussion started by: civic2005
1 Replies
5. Solaris
Hello - Could you please let me know where do I get the installer for installing netbackup on solaris 10 X86 ? along with the instructions?
Thank you. (1 Reply)
Discussion started by: panchpan
1 Replies
6. Solaris
We have a Solaris 8 machine which is a Netbackup 5.0 clinet.
Backups have been running fine. Today I see in dmesg that "bpcd/tcp: bind: Address already in use" error
bpcd which is backup clinet deamon listens on port 13782 as stated in /etc/services
when I do $ netstat -an|grep -i... (3 Replies)
Discussion started by: Tirmazi
3 Replies
7. Solaris
Hi, I am trying to configure NTP client on my Solaris server, but I am getting error like:
Jan 13 10:53:33 SPOTS ntpdate: no server suitable for synchronization foundMy ntp.conf file:
bash-3.00# pwd
/etc/inet
bash-3.00#
bash-3.00#
bash-3.00# cat ntp.conf
# ident "@(#)ntp.client... (5 Replies)
Discussion started by: nypreH
5 Replies
8. Solaris
Greetings,
I have a bunch of Solaris servers that are running Netbackup as a client. I set them up and my backup admin has confirmed that they are being backed up. But what I want to be able to do is run a command from each Solaris client to see some proof from the client side that the files... (1 Reply)
Discussion started by: BrewDudeBob
1 Replies
9. Solaris
Hello,
I have a solaris 10 U 8 and want it to authenticate any user against a remote RADIUS server and return it's appropriate privileges on the system
First is it possible? and if yes, How I can do it?
please a consider I'm a little "newbie" on Solaris world
Thanks in advance! (0 Replies)
Discussion started by: basim
0 Replies
10. Proxy Server
Hi guys. First, sorry for my english, I´m tried to write the best form but sure I´m not do it.
I´m tried to configure the native ldap client on Solaris 10 but yet dosen't work. May be the problem is in the pam.conf or something like that.
This is the line I was applied to configure the... (7 Replies)
Discussion started by: sultano
7 Replies
XNB(4) BSD Kernel Interfaces Manual XNB(4)
NAME
xnb -- Xen Paravirtualized Backend Ethernet Driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
options XENHVM
device xenpci
DESCRIPTION
The xnb driver provides the back half of a paravirtualized xen(4) network connection. The netback and netfront drivers appear to their
respective operating systems as Ethernet devices linked by a crossover cable. Typically, xnb will run on Domain 0 and the netfront driver
will run on a guest domain. However, it is also possible to run xnb on a guest domain. It may be bridged or routed to provide the net-
front's domain access to other guest domains or to a physical network.
In most respects, the xnb device appears to the OS as an other Ethernet device. It can be configured at runtime entirely with ifconfig(8).
In particular, it supports MAC changing, arbitrary MTU sizes, checksum offload for IP, UDP, and TCP for both receive and transmit, and TSO.
However, see CAVEATS before enabling txcsum, rxcsum, or tso.
SYSCTL VARIABLES
The following read-only variables are available via sysctl(8):
dev.xnb.%d.dump_rings
Displays information about the ring buffers used to pass requests between the netfront and netback. Mostly useful for debugging, but
can also be used to get traffic statistics.
dev.xnb.%d.unit_test_results
Runs a builtin suite of unit tests and displays the results. Does not affect the operation of the driver in any way. Note that the
test suite simulates error conditions; this will result in error messages being printed to the system log.
SEE ALSO
arp(4), netintro(4), ng_ether(4), xen(4), ifconfig(8)
HISTORY
The xnb device driver first appeared in FreeBSD 10.0.
AUTHORS
The xnb driver was written by Alan Somers <alans@spectralogic.com> and John Suykerbuyk <johns@spectralogic.com>.
CAVEATS
Packets sent through Xennet pass over shared memory, so the protocol includes no form of link-layer checksum or CRC. Furthermore, Xennet
drivers always report to their hosts that they support receive and transmit checksum offloading. They "offload" the checksum calculation by
simply skipping it. That works fine for packets that are exchanged between two domains on the same machine. However, when a Xennet inter-
face is bridged to a physical interface, a correct checksum must be attached to any packets bound for that physical interface. Currently,
FreeBSD lacks any mechanism for an Ethernet device to inform the OS that newly received packets are valid even though their checksums are
not. So if the netfront driver is configured to offload checksum calculations, it will pass non-checksumed packets to xnb, which must then
calculate the checksum in software before passing the packet to the OS.
For this reason, it is recommended that if xnb is bridged to a physical interface, then transmit checksum offloading should be disabled on
the netfront. The Xennet protocol does not have any mechanism for the netback to request the netfront to do this; the operator must do it
manually.
BUGS
The xnb driver does not properly checksum UDP datagrams that span more than one Ethernet frame. Nor does it correctly checksum IPv6 packets.
To workaround that bug, disable transmit checksum offloading on the netfront driver.
BSD
June 6, 2014 BSD