Backup Files Failed

Thread Tools Search this Thread
Operating Systems HP-UX Backup Files Failed
# 1  
Old 09-29-2009
Backup Files Failed

I am having difficulty in doing ontape -s -L 0. At first it was giving a message Archive failed - function to write to tape failed code -l errno 5.

After about 24 hours it says "could not write archive tape. What do I do?

Can anyone please advise on what the problem is and what I can do?

Thanks in advance.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

How to backup a directory (sub-directories/files) files from one server on to other ?

Hello, Server A: /directory1/ Server B: /Backups/ i wanted to backup contents of /directory1 from "server A" on to "Server B" every 1 hour. If there is any change in (only new/differences) contents on serverA (directory1/) supposed to be backeup on next run. I did used rsync command to... (5 Replies)
Discussion started by: System Admin 77
5 Replies

2. AIX

Backup: The lseek call failed

Hi, We are facing issues while backing up our 1205 GB filesystem on LTO5 Tape. During backup the "backup: The lseek call failed." messages were generated, I want to know why these messages were generating AIX version is: 6100-08-00-0000 backup: The date of this level 0 backup is Mon Mar 11... (4 Replies)
Discussion started by: m_raheelahmed
4 Replies

3. Shell Programming and Scripting

Backup Files

Hi, Using the shell script, how can I backup the files. /etc/password, /etc/group , /etc/shadow and more and needs a backup like /etc/password.12Mar12.... (4 Replies)
Discussion started by: gsiva
4 Replies

4. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

Hi Everyone, we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment? Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies

5. UNIX for Advanced & Expert Users

FTP failed to copy mulitple files from multiple directory

I am using below scripts to copy all the files from multiple folders. By executing individually command i am able to copy all the files but using scripts only getting first file. System is ignoring the second CD and mget command. USER=loginid PASSWD="abc" echo "open $HOST... (6 Replies)
Discussion started by: meetvipin
6 Replies

6. AIX

backup script failed with error '0403-005 Cannot create the specified file'

In AIX 5.1, a daily run script that backing up oracle data failed yesterday with following errors: The Tivoli backup of DBPROD failed. What could be the issue, OS, backup or Oracle? (3 Replies)
Discussion started by: jalite19
3 Replies

7. Shell Programming and Scripting

Backup files

Greetings. I've got a little bit of problem with writing a script. I'd like to write a script that creates backup files (of your computer) once a week, and on the other days of the week it just updates it. Thanks in advance i hope you can help: buddhist p.s.: this would help a lot, because... (1 Reply)
Discussion started by: buddhist
1 Replies

8. UNIX for Advanced & Expert Users

rm & mv command failed due to too many files.

In our directory there are too many files, & if I try to execute mv *.gz or rm *.l command it fails, providing error string as - 'arg list too long'. This doesnt happen always, is there any way we know, limit on the rm & mv command so we can take care of this failure in future executions ? (9 Replies)
Discussion started by: videsh77
9 Replies

9. UNIX for Dummies Questions & Answers

Backup failed

I'm getting following message at my EOD backup script:sh: line1: /dev/rct0: cannot create What could be the possible causes for this error and how could I resolve it? (10 Replies)
Discussion started by: nervous
10 Replies

10. UNIX for Dummies Questions & Answers

EOD backup failed

EOD backup failed with following error: 05/08/07 01:10:02 write /home/compdir to DATTAPE 2712860 blocks UX: cpio: HALT: Cannot read from device 1 error Failed on shell-script: cpio -ictB 2>>/home2/Rev83/misc/logs/bk.End-of-day 1>/dev/null </dev/rct0 05/08/07 2:29:14 What above output... (0 Replies)
Discussion started by: nervous
0 Replies
Login or Register to Ask a Question
FMS(8)							       AFS Command Reference							    FMS(8)

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. <> 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)