09-19-2001
Well, I figured out the imaging part. The dd command does work, it just takes such a long time I didn't think it was working. I let it run overnight and it finished. Must have taken several hours though. So it looks like using dd for imaging hard drives is possible, just not very practicle.
Having tried a emulating a raid setup with IDE yet. I'll get to that as soon as I have the time and resources. If anyone else has tried it let me know!
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know of any good imaging tools that can be used to create an image of a Sco-Unix box? (2 Replies)
Discussion started by: gmrfh1
2 Replies
2. UNIX for Advanced & Expert Users
Dears,
I have server has two port's(Enet0,Enet1) what I want as follows:
Make the two port's has same IP address
where, if the port Enet0 became down automaticly Enet1 become up :confused: .
Amen (4 Replies)
Discussion started by: amen00
4 Replies
3. UNIX for Advanced & Expert Users
Here we want to implement the network redundancy on UNIX with the software.
The two network interface cards are configured on the UNIX node,once one card is down or unnormal,the other can take over. Those aplications that used the tcp ,udp,multicast protocol can also been switched at the same... (2 Replies)
Discussion started by: Frank2004
2 Replies
4. UNIX for Dummies Questions & Answers
We have had some email outages in the last few months and my boss is asking is it worth going with one of those email redundancy/filtering sites. The thing is, we have a backup server on a remote location, so I am pretty sure we can set something up with what we have already.
At the moment... (1 Reply)
Discussion started by: edzillion
1 Replies
5. Red Hat
Can anyone recommend an imaging solution for RedHat Linux that would allow base imaging with the ability to do incremental updates and encryption? I know Acronis has a version available, but it is rather pricey.
Thanks. (0 Replies)
Discussion started by: here2learn
0 Replies
6. Solaris
Hello,
Yes, it's me again. Running around getting this done! My current problem is I'm trying to image one drive 0 (/dev/dsk/c1t0d0s0) to drive 1 (/dev/dsk/c1t1d0s0). I know that drive1 came out of a Sun Server and it is a Sun drive. Solaris 10 recognized drive1 after the devfsadm command. The... (8 Replies)
Discussion started by: adelsin
8 Replies
7. AIX
Hi Guys,
I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards...
... (2 Replies)
Discussion started by: kkeng808
2 Replies
8. AIX
Have been learning a lot off late and am a little unclear about the VIOS setup particularly with regards to redundancy. Would appreciate your help.
My question is very basic. Lets say I have setup a VIOS and 3 LPARs on only one hdd (non scsi). On what do I setup the second VIOS? Could I for... (7 Replies)
Discussion started by: theaixeman
7 Replies
9. AIX
I have one p5 server, no lpar, 2 physical network adapter, bundle as one EtherChannel. The two 2 physical network adapter connect to 2 network switches.
How to make this as a redundancy config?
Current is if one physical network adapter down, the seond one will go through the network. but if... (2 Replies)
Discussion started by: rainbow_bean
2 Replies
LEARN ABOUT CENTOS
fedfs-null
FEDFS-NULL(8) System Manager's Manual FEDFS-NULL(8)
NAME
fedfs-null - send a FEDFS_NULL ADMIN protocol request
SYNOPSIS
fedfs-null [-?d] [-n nettype] [-h hostname] [-s security]
INTRODUCTION
RFC 5716 introduces the Federated File System (FedFS, for short). FedFS is an extensible standardized mechanism by which system adminis-
trators construct a coherent namespace across multiple file servers using file system referrals. For further details, see fedfs(7).
FedFS-enabled file servers allow remote administrative access via an authenticated RPC protocol known as the FedFS ADMIN protocol. Using
this protocol, FedFS administrators manage FedFS junctions and NSDB connection parameter information on remote FedFS-enabled file servers.
DESCRIPTION
The fedfs-null(8) command is part of a collection of low-level single-use programs that is intended for testing the FedFS ADMIN protocol or
for use in scripts. It sends a single FEDFS_NULL request to a remote FedFS ADMIN protocol service.
The FEDFS_NULL request performs a simple ping operation that determines if there is an operational FedFS ADMIN service on the remote
server.
OPTIONS
-d, --debug
Enables debugging messages during operation.
-?, --help
Displays fedfs-null(8) version information and a usage message on stderr.
-h, --hostname=hostname
Specifies the hostname of a remote FedFS ADMIN service. If this option is not specified, the default value is localhost.
-n, --nettype=nettype
Specifies the transport to use when contacting the remote FedFS ADMIN service. Typically the nettype is one of tcp or udp. If this
option is not specified, the default value is netpath. See rpc(3t) for details.
-s, --security=flavor
Specifies the security flavor to use when contacting the remote FedFS ADMIN service. Valid flavors are sys, unix, krb5, krb5i, and
krb5p. If this option is not specified, the unix flavor is used. See the SECURITY section of this man page for details.
EXAMPLES
Suppose you are the FedFS administrator of the example.net FedFS domain and that you want to know if the FedFS ADMIN service on the file
server fs.example.net is operational. Use:
$ fedfs-null -h fs.example.net
Call completed successfully
SECURITY
By default, or if the sys and unix flavors are specified with the --security=flavor option, the fedfs-create-junction(8) command uses
AUTH_SYS security for the Remote Procedure Call. AUTH_SYS has known weaknesses and should be avoided on untrusted networks.
The RPC client uses the Kerberos v5 GSS mechanism if a Kerberos security flavor is specified. When specifying a Kerberos security flavor,
the user must first obtain a valid Kerberos ticket using kinit(1) before running fedfs-create-junction(8).
The AUTH_NONE security flavor is no longer supported by this implementation.
SEE ALSO
fedfs(7), rpc.fedfsd(8), kinit(1), rpc(3t)
RFC 5716 for FedFS requirements and overview
COLOPHON
This page is part of the fedfs-utils package. A description of the project and information about reporting bugs can be found at
http://wiki.linux-nfs.org/wiki/index.php/FedFsUtilsProject.
AUTHOR
Chuck Lever <chuck.lever@oracle.com>
3 February 2014 FEDFS-NULL(8)