Emergency Recovery Problems


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Emergency Recovery Problems
# 1  
Old 05-13-2006
Emergency Recovery Problems

Any help here whatsoever will be greatly appreciated!

Running ScoUnix on IBMx235 server.
LTO1 tape drive.
Need to set up DR box.
Disks installed/configured by IBM techie.

On production server:
Ran emergency_disk -d /tmp diskette1 and diskette2 successfully.
Rean emergency_rec -e ctape1 ran successfully.

On DR server:
Boot off diskette 1 sucessfully.
When prompted for diskette2, insert and loads drivers successfully.
Get error message that hard disks are NOT sane
Enter
Proceed to second option to restore hard disks
Insert LTO tape and press Enter when tape is completely loaded.

ERROR IS AS FOLLOWS:
No tape has been detected in the tape drive


Please help!!!
 
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

UNIX emergency

can anyone please tell me that how can i boot unix from a cd? full procedure. it's an emergency. reply asap (1 Reply)
Discussion started by: niket agarwal
1 Replies

2. Solaris

Emergency !!!Help Please--- NFS

Hi Guru's, I am unable to mount NFS share on unix system (DG/UX) which is nfs client. Error: mount: /nfsshare: Invalid argument mount: giving up on: /mountpoint i tried following commands mount -t nfs remotehost:/nfsshare /mountpoint Error: mount: /nfsshare: Invalid... (1 Reply)
Discussion started by: Justin John
1 Replies

3. Shell Programming and Scripting

Emergency !! Need to fix this error!

Pls help me with the below script. Its returning an error No such file or Directory. #!/bin/ksh cd /enip/enipapp/cbp/AOC2511201 for file in `cat filename.txt | head -1 | tr -d '\r'` do for i in `cat '$file' | tr -d '\r'` do echo "-----script start `date`... (9 Replies)
Discussion started by: Naga06
9 Replies

4. Ubuntu

Emergency help with ubuntu

Hi guys i have some question about ubuntu(10.10) 1.what time scheduling & page replacement algorithm have been used in ubuntu 2.how to create a process 3.how to kill a process 4.how to send information to a process 5.how to see a process 6.how to increase priority of a process 7.how to... (1 Reply)
Discussion started by: mortez28
1 Replies

5. Shell Programming and Scripting

Need Emergency help with script!

I'm trying to write a script to push out to all our servers some Veritas add-ons. I want the script to push to all servers and if there server hardware matches the uname -i statement, it will install a additional add-on.. The script keeps giving me a error on line 29. Here is the script.... (3 Replies)
Discussion started by: soupbone38
3 Replies

6. UNIX for Advanced & Expert Users

emergency shutdown best practices.

Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server? I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not... (10 Replies)
Discussion started by: jsw371
10 Replies

7. UNIX for Advanced & Expert Users

Emergency Recovery Problems

Any help here whatsoever will be greatly appreciated! Running ScoUnix on IBMx235 server. LTO1 tape drive. Need to set up DR box. Disks installed/configured by IBM techie. On production server: Ran emergency_disk -d /tmp diskette1 and diskette2 successfully. Rean emergency_rec -e ctape1... (1 Reply)
Discussion started by: kwagga123
1 Replies

8. SCO

Emergency boot

I need to boot an OpenServer 5.0.5 server but I don't have emergency boot disks for it. There are some boot disks of other servers. Can I use these disks, changing defbootstr ?. How ?. The fact is that administrator can't login as root and it seems to be a corrupted auth system issue. Other... (2 Replies)
Discussion started by: dags
2 Replies
Login or Register to Ask a Question
FMS(8)							       AFS Command Reference							    FMS(8)

NAME
fms - Determine a tape's capacity and a tape device's filemark size SYNOPSIS
fms -tape <tape special file> [-help] fms -t <tape special file> [-h] DESCRIPTION
The fms command determines the capacity of the tape currently in the tape device identified by the -tape argument, along with the size of the filemark for the device. The filemark is also referred to as the device's end-of-file (EOF) marker, and can differ for each combination of tape and tape device. As the Tape Coordinator writes a dump, it writes a filemark between the data included from each volume and also tracks the amount of space left before the end of the tape (EOT). For some tape devices, the filemark is large enough (multiple megabytes) that failure to consider it leads the Tape Coordinator significantly to overestimate the available space. The intended use of this command is to determine tape capacity and filemark size values that can be specified in a tape device's entry in the /var/lib/openafs/backup/tapeconfig file. For certain types of tape drives, the Tape Coordinator operates more efficiently when the tapeconfig file lists accurate values. For further discussion, see the OpenAFS Administration Guide chapter on configuring the Backup System. Insert a tape in the drive before issuing this command. CAUTIONS
Do not use this command on compressing tape devices in compression mode or with tape devices that handle tapes of multigigabyte (or multiterabyte) capacity. It does not produce accurate results in those cases. For alternate suggestions on the values to record in the tapeconfig file for compressing drives, see the OpenAFS Administration Guide chapter on configuring the Backup System. Running the command completely overwrites the tape, so use a blank one or one that can be recycled. Because it writes filemarks to the complete length of the tape, the command can take from several hours to more than a day to complete. OPTIONS
-tape <tape special file> Specifies the UNIX device name of the tape device for which to determine filemark size and the capacity of the tape it currently contains. The format varies on different system types, but usually begins with /dev; an example is /dev/sd0a. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
The command generates output both on the standard output stream and in the fms.log file that it creates in the current working directory. The output reports the capacity of the tape in the device and the device's filemark size. The first few lines of output include status information about the execution of the command, including such information as the number of blocks and the number of file marks written to the tape by the command. The last two lines of both screen and file output provide the following information: o "Tape capacity is number bytes": specifies the size, in bytes, of the tape in the device. o "File marks are number bytes": specifies the device's filemark size in bytes. The following message indicates that the fms command interpreter cannot access the tape device. The command halts. Can't open tape drive I<device> The following message indicates that the command interpreter cannot create the fms.log log file. Again, the command halts. Can't open log file EXAMPLES
The following command illustrates the output for the device called /dev/rmt1h: % fms /dev/rmt1h wrote block: 130408 Finished data capacity test - rewinding wrote 1109 blocks, 1109 file marks Finished file mark test Tape capacity is 2136604672 bytes File marks are 1910205 bytes The following appears in the fms.log file: fms test started wrote 9230 blocks Finished file mark test Tape capacity is 151224320 bytes File marks are 2375680 bytes PRIVILEGE REQUIRED
The issuer must be able to insert and write to files in the currently working directory, if the fms.log file does not already exist. If it already exists, the issuer need only be able to write to it. SEE ALSO
fms.log(5), tapeconfig(5) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FMS(8)