09-26-2001
Hmmm....
Well-
you tried my favorite already, "dd" is great, but how about a "dd" once a month, for a "Full image" mirror, and then using a *fsdump command to dump over the slices of the fs for the rest of the month? this is faster, but not as strenuous or inclusive as "dd". Is this a heavily used server 24/7? If not, the "dd" on a nightly or weekly basis should be fine. If the data is pretty static, like some static web pages with a separate database for info storage, then I'd say that a weekly "dd", and another whenever any major revisions are made would be good, but it really comes down to the state of your data. Since you are only looking at the mirror to maintain uptime, I am assuming this is some sort of webserver. If not, I'd look at getting something off to tape as well asap, you can never have too many backups to a removable media source. I'll also go with the hardline approach on this one, buy a good tape drive if you are using one, a good way to determine the value of your data is to see how much you put into your backup system. If you backup to a $10 DDS1 DAT drive, that must be all your data is worth to you.
My old place of work used to backup our webserver like this:
-weekly "dd" to an IDENTICAL drive as that in the server itself
-nightly ufsdump of the critical filesystems over to the mirror drive
-daily tape backup to a DLT, incremental and a monthly full image
This worked on a Solaris box, it was a Sparc, they flip IDs 0 and 1 (if I remember right) on boot, so we just set the mirror at ID2. This was a great setup, and it worked quite well until one of the drives died and someone (not me, I swear) tried to "dd" to the replacement from the production drive. They crossed-up the "if" and "of" args, so we copied a nice, formatted disk with a spanking new drive label on it over to our produciton webserver drive, that was a bad day. Luckily, the tape was there, and so I say again, get your data on a removable media, keep at least two copies and one HAS to be off-site. I may sound paranoid, but these are reasonable measures for a business that places value on it's data. If your computer makes you any sort of income (tangible or not), the data on that computer is worth, at minimum, what you make off of it, sometimes much more....
Later,
loadc
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-delete-replication
FEDFS-DELETE-REPLICATION(8) System Manager's Manual FEDFS-DELETE-REPLICATION(8)
NAME
fedfs-delete-replication - send a FEDFS_DELETE_REPLICATION ADMIN protocol request
SYNOPSIS
fedfs-delete-replication [-?d] [-n nettype] [-h hostname] [-s security] path
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-delete-replication(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_DELETE_REPLICATION request to a remote FedFS ADMIN protocol service.
The FEDFS_DELETE_REPLICATION request deletes a replication marker in a local file system on a remote file server. The fedfs-delete-repli-
cation(8) command taks a single positional parameter which is the pathname on the remote server of the replication marker to be deleted.
This pathname is relative to the root of the local file system on the remote server.
OPTIONS
-d, --debug
Enables debugging messages during operation.
-?, --help
Displays fedfs-delete-replication(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. To delete an existing FedFS replication on the remote server
fs.example.net, use:
$ fedfs-delete-replication -h fs.example.net /export/replication1
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-DELETE-REPLICATION(8)