Sponsored Content
Operating Systems SCO Recovering OpenServer 5.0.6 onto different hardware Post 302375358 by jgt on Friday 27th of November 2009 11:30:03 AM
Old 11-27-2009
The easiest solution is the replacement hardware having the same disk controller (driver) as the current system.
Next easiest is to build a target kernel for the proposed disk controller, and having it on the current system.
BackupEdge is a really really good solution.
Make sure that the tape drive and its controller will fit the new system, or that a replacement drive will read your tape.
Make sure that any add in cards that you have will work with the replacement hardware, or that you can find a suitable alternative.
Try to arrange your data so that the root file system contains minimal data.
eg. Move home directories to /u or /home.
Move mail boxes from /usr/spool/mail to /u/spool/mail (edit /usr/mmdf/mmdftailor).
Make a copy of /usr/spool/lp/admins/lp/interfaces, /etc/hosts, /etc/resolv.conf, /etc/rc2.d, and anything else you know about.
Use the ap command to make a copy of all user accounts and passwords.
This way, if you have to rebuild from scratch you will have the most amount of configuration and data on file systems that are easy to restore.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Recovering lost files

I noticed this in a search for more security tools... It IS possible to "undelete" a file; I suppose recover would be a better term for it. I suppose we've all made the boo-boo (that we all hopefully learned from) of deleting a file, and finding that you do not have a backup. I wouldn't... (1 Reply)
Discussion started by: LivinFree
1 Replies

2. News, Links, Events and Announcements

Filesystems: Hiding and recovering data

Here is a very interesting article on not only hiding data on filesystems (the article deals mainly with the ext2 filesystem, which should also work with etx3), but also recovering, including from slack space on raw blocks, and even deleted data! ... (0 Replies)
Discussion started by: LivinFree
0 Replies

3. SCO

HELP! Recovering system from New Orleans!!

I am helping a company recover a system that is SCO OS 5.0.5 - they have their backup media, cd copies of SCO, but they do not have their license keys to install and SCO is being difficult in validating their license. Does anyone have an install license key for 5.0.5 that they would be willing... (1 Reply)
Discussion started by: ggraham
1 Replies

4. UNIX for Dummies Questions & Answers

recovering files removed with rm

Hello, I was reading the manual on rm and it states that when you use 'rm' the files are usual recoverable, how is this done? Does it assume that a backup system is in place? Cheers Jack (4 Replies)
Discussion started by: jack1981
4 Replies

5. UNIX for Dummies Questions & Answers

Help recovering a backed up file

Hello, By accident I erased a file at work and I need to restore it from a backup tape. My manager says I will have to use the mt command with the fsf option to look through the tape but I am confuzed. I did a restore -t to get a listing of the tape. This is taking a long time. If I sound... (1 Reply)
Discussion started by: mojoman
1 Replies

6. SCO

Recovering 5.0.7 from Bootable CD

I've been working with SCO Unix for several years now but have never had to restore a system from a bare drive. I have a bootable CD that contains what appears to be the correct files necessary to recover the boot and root filesystems. I've got the BIOS setup such that the CD is the first... (12 Replies)
Discussion started by: teamhog
12 Replies

7. High Performance Computing

MPI, recovering node

Hi all, I'm writing an MPI application, in which I handle failures and recover them. In order to do that, in case of one node failure, I would like to remove that node from the MPI_COMM_WORLD group and continue with the remaining nodes. Does anybody know how I can do that? I'm using... (5 Replies)
Discussion started by: SaTYR
5 Replies

8. AIX

Recovering a failed system

Hi,My system is not booting and at the startup it is getting struck.In HMC error code is coming as 0000, I know the reason of failing.I have few queries on recovery, please answer:1. I have mksysb of the system from which I can restore the system but problem is my few application mount point was a... (5 Replies)
Discussion started by: aixpank
5 Replies

9. Shell Programming and Scripting

recovering cron job

I deleted one of the job from the cron tab. I want to get it back. How can i do this. pplease suggest me.. thanks (1 Reply)
Discussion started by: pranabrana
1 Replies

10. UNIX for Advanced & Expert Users

recovering a deleted directory

I accidentally deleted a very important directory today with this rm -r. What would be the recommended way to recover my directory? After a lot of googleing I have seen these choices. Could I get some recommendations please? Testdisk Photorec- Doesn't recover file name like I would like. ... (10 Replies)
Discussion started by: cokedude
10 Replies
UUCP(1) 						      General Commands Manual							   UUCP(1)

NAME
uucp - unix to unix copy SYNOPSIS
uucp [ -acCdfmr ] [ -nuser ] [ -ggrade ] [ -sspool ] [ -xdebug ] source-file.... destination-file DESCRIPTION
Uucp copies files named by the source-file arguments to the destination-file argument. A file name may be a pathname on your machine, or may have the form system-name!pathname where `system-name' is taken from a list of system names that uucp knows about. Shell metacharacters ?*[] appearing in the pathname part will be expanded on the appropriate system. Pathnames may be one of:(1) a full pathname; (2) a pathname preceded by ~user; where user is a userid on the specified system and is replaced by that user's login directory; (3) a pathname prefixed by ~, where ~ is expanded into the system's public directory (usually /usr/spool/uucppublic); (4) a partial pathname, which is prefixed by the current directory. If the result is an erroneous pathname for the remote system, the copy will fail. If the destination-file is a directory, the last part of the source-file name is used. Uucp preserves execute permissions across the transmission and gives 0666 read and write permissions (see chmod(2)). The following options are interpreted by uucp. -a Avoid doing a getwd to find the current directory. (This is sometimes used for efficiency.) -c Use the source file when copying out rather than copying the file to the spool directory. (This is the default.) -C Copy the source file to the spool directory and transmit the copy. -d Make all necessary directories for the file copy. (This is the default.) -f Do not make intermediate directories for the file copy. -ggrade Grade is a single letter/number; lower ASCII sequence characters will cause a job to be transmitted earlier during a particular con- versation. Default is `n'. By way of comparison, uux(1C) defaults to `A'; mail is usually sent at `C'. -m Send mail to the requester when the copy is complete. -nuser Notify user on remote system (i.e., send user mail) that a file was sent. -r Do not start the transfer, just queue the job. -sspool Use spool as the spool directory instead of the default. -xdebug Turn on the debugging at level debug. FILES
/usr/spool/uucp - spool directory /etc/uucp/* - data and configuration files SEE ALSO
uux(1C), mail(1) D. A. Nowitz and M. E. Lesk, A Dial-Up Network of UNIX Systems. D. A. Nowitz, Uucp Implementation Description. WARNING
The domain of remotely accessible files can (and for obvious security reasons, usually should) be severely restricted. You will very likely not be able to fetch files by pathname; ask a responsible person on the remote system to send them to you. For the same reasons you will probably not be able to send files to arbitrary pathnames. BUGS
All files received by uucp will be owned by the uucp administrator (usually UID 5). The -m option will only work sending files or receiving a single file. (Receiving multiple files specified by special shell characters ?*[] will not activate the -m option.) At present uucp cannot copy to a system several "hops" away, that is, a command of the form uucp myfile system1!system2!system3!yourfile is not permitted. Use uusend(1C) instead. When invoking uucp from csh(1), the `!' character must be prefixed by the `' escape to inhibit csh's history mechanism. (Quotes are not sufficient.) Uucp refuses to copy a file that does not give read access to ``other''; that is, the file must have at least 0444 modes. 7th Edition April 24, 1986 UUCP(1)
All times are GMT -4. The time now is 08:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy