10-16-2006
Veritas Backup Agent on SCO problem
Hello All,
We have Veritas Backup Exec on a Windows 2003 OS and trying to setup the Ralus agent on SCO to perform regular backups of our Unixware system; but for some reason after "I believe" installing the agent on SCO; and launching it using the 'agent.be" command I receive a syntax error "getsrvbyname failed!"
There is a service grfs 6101/tcp entered in my services file and pointing to the server host name in the hosts file but still no avail...
Any ideas? Can someone please help?
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Backup Exec Agent won't start....
Question: Has anyone had any previous experience working with Backup exec for Unix? I'm running SCO Openserver 5.0.5 and Backup Exec agent Version 5.01 Revision 5.032 Basically, these are the commands I'm issueing and here is the output.
# cd etc
# cd... (1 Reply)
Discussion started by: PatMcCoy
1 Replies
2. UNIX for Advanced & Expert Users
Does anyone know how to run " ./agent.be & " in the background? I need to keep it running so that Backup Exec can see it. When I log out as root is shuts down the agent. This just started happening after I upgraded my Veritas drivers on my Windows 2000 server. That is my backup server.
Hope... (1 Reply)
Discussion started by: jback
1 Replies
3. Solaris
hi ,
we have a monthly policy for database backups .
the database is a huge one about 200 GB in size and every month , we shut down the database and take a full system backup .
my question is : Is there a way to know that i have taken a valid backup, I need to do something like a test restore... (5 Replies)
Discussion started by: ppass
5 Replies
4. UNIX for Dummies Questions & Answers
Hi guys,
First I have to say that I'm not Unix expert, I just have medium level experince in Unix scripting and some knowledge with a little of hands on experience of unix administration (Solaris only). I have my plans to move ahead in that field but this is a different story.
I have a client... (0 Replies)
Discussion started by: SolarisProToBe
0 Replies
5. UNIX for Advanced & Expert Users
Hello,
When launching a recently installed UNIX agent for my Veritas backup exec server I receive "getservbyname (grfs, tcp) failed!"
I have checked to make sure the service exists under port 6101 and its there. I also removed and recreated the service but still no go. :confused: :confused:... (2 Replies)
Discussion started by: George26
2 Replies
6. SCO
I have 3 SCO 5.0.5 machines. Two are running the /etc/bkupexec/agent.be just fine but the 3rd fails with a NRL initialization error. It can't seem to find the backup server in the /etc/hosts file.
The entry is in the /etc/hosts file.
The perms are set correctly on /etc /etc/bkupexec... (0 Replies)
Discussion started by: cnpaul
0 Replies
7. UNIX for Dummies Questions & Answers
I was facing problems in taking backup of a windows server for quiet a long time.i have again reinstall the client software to get rid of this.
my question : how to check the agent (netbackup) is running on client side or not?? how to check????
bcoz reinstalltion is not a good solution .:( (6 Replies)
Discussion started by: saurabh84g
6 Replies
8. UNIX for Dummies Questions & Answers
anyone ?
i install and it just fail to startup. (0 Replies)
Discussion started by: kakabobo
0 Replies
9. AIX
Hi all. I hope someone could give me a hand on installing Backup Exec agent on AIX machine :(
Agent:
OS: AIX 5.3
Hostname: DB-HN-SRV02
IP: 10.1.4.64
Backup server:
OS: Windows Server 2003
Hostname: backup-srv
IP: 10.1.5.51
I download "Legacy Unix agent.tar", untar, then run file... (0 Replies)
Discussion started by: bsddaemon
0 Replies
10. BSD
Hi
I'd like to backup my freeBSD 7.0 using Backup Exec 12.0
Where to download the Backup Exec Agent for Linux/Unix? (4 Replies)
Discussion started by: ccc
4 Replies
vxiod(1M) vxiod(1M)
NAME
vxiod - start, stop, and report on Veritas Volume Manager I/O threads
SYNOPSIS
vxiod
vxiod [-f ] [set count]
DESCRIPTION
The vxiod utility starts, stops, or reports on Veritas Volume Manager (VxVM) I/O kernel threads. An I/O thread provides a process context
for performing I/O in VxVM.
When the vxio module is loaded, 16 I/O threads are created, plus 2 threads per additional CPU for a system with more than 8 CPUs, up to a
maximum of 64 threads. At least one I/O thread must be running while the vxio module is loaded, and the number of I/O threads cannot be
forced to zero.
When invoked with no arguments, vxiod prints the current number of I/O threads to the standard output.
The number of threads that is required for handling I/O requests depends on the system load and usage. If volume recovery seems to proceed
more slowly at times, it may be possible to improve its performance by increasing the number of I/O threads up to a maximum of 64.
KEYWORDS
set When invoked with the set keyword, vxiod creates the number of I/O threads specified by count. If more volume I/O threads exist
than are specified by count, the excess processes terminate. If more than the maximum number(64) are specified, the requested
number is silently truncated to that maximum.
OPTIONS
-f This option has no effect from release 5.0 onward. The number of I/O threads cannot be reduced to zero.
EXIT CODES
The vxiod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O request occurs within a I/O
thread, the state of that I/O request is not reflected in the exit status for vxiod. Otherwise, vxiod returns a non-zero exit status on
error.
Usage errors result in an exit status of 1 and a usage message. If the requested number of threads cannot be created, the exit status is
2, and the number of threads that were successfully started is reported. If any other error occurs, the exit status is 3.
FILES
/dev/vx/iod The device used to report on and start volume I/O threads.
NOTES
Veritas Volume Manager I/O threads cannot be killed directly through the use of signals.
Depending on the operating system, VxVM I/O threads may not appear in the list of processes that is output by the ps command. The number
of I/O threads that is currently running can be determined by running vxiod.
SEE ALSO
fork(2), ps(1), vxconfigd(1M), vxdctl(1M), vxintro(1M), vxio(7), vxiod(7)
VxVM 5.0.31.1 24 Mar 2008 vxiod(1M)