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
ccr(8) System Manager's Manual ccr(8)
Name
ccr - remote console carrier requester
Syntax
ccr [ options ] node
Description
The command establishes a logical connection between your ULTRIX system and the console carrier server on a remote system. enables your
terminal to act as the console for a remote unattended system. For example, your terminal can act as the console for a Digital Ethernet
Communications Server (DECSA) and its resident software. The node is the name or address of the target node. A node name consists of from
one to six alphanumeric characters. A node address consist of two decimal integers (n.n), where the first indicates the network number
(1-63), and the second indicates the node address (1-1023).
You can use to force a crash if a server node becomes unresponsive. To determine how to force a crash, see the documentation for the
respective server product.
The requirements for using are as follows:
o The host node (that is, your local ULTRIX node) and the remote node must be on the same Ethernet.
o If your server product is a DECSA, the console carrier server image (plutocc.sys) and its loader file (plutowl.sys) must be located in
on your ULTRIX node. The pluocc.sys and plutowl.sys files are not need, nor is any loading done for other servers. For more details,
see the installation guide for the particular server product.
<CTRL/D> exits from console carrier mode and terminates
Options
-c Uses the specified circuit to connect to the target node.
-h Uses the specified address (next argument) as the Ethernet address of the target node.
-n Uses the next argument as the target node ID.
-p Uses the specified service password (next arguments) in accessing the target node.
Examples
# /etc/ccr -c qna-0 -n dallas <RET>
ccr: Remote console reserved
.
.
.
<CTRL/D>
ccr: Remote console released
#
Restrictions
You must have superuser privileges to run
Diagnostics
The command can return the following diagnostic messages:
ccr: Remote console reserved
The command has successfully connected to the remote console server and your terminal is now capable of acting as a console for the remote
node.
ccr: Remote console released
Your connection with the remote console server has been terminated and you are no longer in console carrier mode.
ccr: Remote console already in use
The remote console server that you are attempting to connect to is already reserved by another user.
ccr: Permission denied
You do not have the necessary privileges to run (You must be a superuser.)
ccr: Hardware address required
The command is unable to locate the hardware address of the remote node to which you are attempting to connect. A remote node's hardware
address must be defined either in the command line, or in its nodes database entry. (Nodes database entries are defined with the command.)
ccr: No node entry in database
The command does not recognize the remote node to which you are attempting to connect, since the node-id that you specified is not defined
in the nodes database. (Nodes database entries are defined with the command.)
Files
Console carrier server image
Console carrier server loader
See Also
addnode(8), getnode(8), load(8), remnode(8), trigger(8)
Guide to Local Transport Servers
ccr(8)