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
LEARN ABOUT OPENSOLARIS
ssh-agent
ssh-agent(1) User Commands ssh-agent(1)
NAME
ssh-agent - authentication agent
SYNOPSIS
ssh-agent [-a bind_address] [-c | -s ] [-d]
[command [args]...]
ssh-agent [-c | -s] -k
DESCRIPTION
ssh-agent is a program to hold private keys used for public key authentication (RSA, DSA). ssh-agent is often started at the beginning of a
login session. All other windows or programs are started as clients to the ssh-agent program. Through use of environment variables, the
agent can be located and automatically used for authentication when logging in to other machines using ssh(1). See the System Administra-
tion Guide: Security Services.
If a command line is given, this is executed as a subprocess of the agent. When the command dies, so does the agent.
The agent initially does not have any private keys. Keys are added using ssh-add(1), which sends the identity to the agent. Several identi-
ties can be stored in the agent; the agent can automatically use any of these identities. Use the -l option in ssh-add(1) to display the
identities currently held by the agent.
The agent is run in the user's local host. Authentication data need not be stored on any other machine, and authentication passphrases
never go over the network. However, if the connection to the agent is forwarded over SSH remote logins, the user can use the privileges
given by the identities anywhere in the network in a secure way.
There are two main ways to get an agent setup. Either you let the agent start a new subcommand into which some environment variables are
exported, or you let the agent print the needed shell commands (either sh(1) or csh(1) syntax can be generated) which can be evalled in the
calling shell. Later, use ssh(1) to look at these variables and use them to establish a connection to the agent.
A unix-domain socket is created (/tmp/ssh-XXXXXXXX/agent.pid) and the name of this socket is stored in the SSH_AUTH_SOCK environment vari-
able. The socket is made accessible only to the current user. This method is easily abused by root or another instance of the same user.
The SSH_AGENT_PID environment variable holds the agent's PID.
The agent exits automatically when the command given on the command line terminates.
OPTIONS
The following options are supported:
-a bind_address Binds the agent to the unix-domain socket bind_address. The default is /tmp/ssh-XXXXXXXX/agent.pid.
-c Generates C-shell commands on stdout. This is the default if SHELL indicates that it is a csh style of shell.
-d Debug mode. When this option is specified, ssh-agent will not fork.
-k Kills the current agent (given by the SSH_AGENT_PID environment variable).
-s Generates Bourne shell commands on stdout. This is the default if SHELL does not indicate that it is a csh style of
shell.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
FILES
/tmp/ssh-XXXXXXXX/agent.pid
Unix-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner. The
sockets are removed when the agent exits.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsshu |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
SEE ALSO
ssh(1), ssh-add(1), ssh-keygen(1), sshd(1M), attributes(5)
System Administration Guide: Security Services
SunOS 5.11 17 Nov 2008 ssh-agent(1)