Sponsored Content
Operating Systems Solaris Information about taking dump of a unix server on a tape and then restoring Post 302339824 by asalman.qazi on Friday 31st of July 2009 11:42:29 AM
Old 07-31-2009
Information about taking dump of a unix server on a tape and then restoring

Hi all,

Can anyone provide me with a site or book that gives detailed information about taking dump of a unix server on a tape and then restoring the server from the dump

Also i want information about migration from old server to new server (solaris 5.6 to solaris 8)
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Restoring a file from Tape

help please i have "inherited" a Sco Server (the administrator departed in a hurry...yes we are chasing him..) and haven't used Unix for 8 years. i have a file that i need to retrieve from a tape. i have been able to find the file on tape using the cpio -ivt command. however... the problem I... (3 Replies)
Discussion started by: mfischer
3 Replies

2. AIX

Problems restoring from tape in AIX

I am trying to restore some files from a DLT drive in AIX 4.3 but I am having a few problems. Basically when I try to run the restore command I get the following error: Cannot read from the specified input. Please enter the device name when ready I am the following command for the restore ... (0 Replies)
Discussion started by: The Hunter
0 Replies

3. UNIX for Dummies Questions & Answers

Blocksize problem restoring file from tape

I was recently given the responsibility of the unix box at our work. Without much training, I now have to go back and restore a file from tape. I'm having some trouble with it. I'm getting an error with the blocksize. The part of the script that does the tar looks like this: tar cvfX... (11 Replies)
Discussion started by: citrowske
11 Replies

4. UNIX for Dummies Questions & Answers

Restoring tape files...

Hi all, I have kinda inherited this problem, but was wondering if anyone else had any ideas. Currently all our backup rentention periods are set to 2 weeks, so that we can cycle through tapes (save money etc...). Anyhow the guys next door in IT, decided one day long long ago, that it would... (0 Replies)
Discussion started by: B14speedfreak
0 Replies

5. Solaris

Problem restoring files from remote tape drive

Server 1 - Sun Solaris 5.8 sparc SUNW,Sun-Fire-480R with attached DLT tape drive /dev/rmt/0n Server 2 - Old DG-UX box which has restore command on it compatible with the files on the backyup tape - backed up with dump2 Server 3 - Sun solaris 5.9 sparc SUNW,Sun-Fire-V490 with lots of free space... (4 Replies)
Discussion started by: lindab
4 Replies

6. Filesystems, Disks and Memory

Tape drives used for taking backups

Hi, I am a abit new in AIX system administration field. I want to gather knowledge about backup techniques. As per my knowledge we use Tape archives for taking backups. Can anyone pls explain me in detail abt tape archive? Whether these tape archives come along with the systems or we have to... (1 Reply)
Discussion started by: forumsrahul
1 Replies

7. UNIX for Advanced & Expert Users

script fot taking mount information

Hi all, I want to take the details of all mounted directories.Some thing like using bdf we can get the information. My code should get the information about the mounted directories and should write into a file. What we are going to do is we are going to shutdown our HP unix server... (12 Replies)
Discussion started by: arunkumar_mca
12 Replies

8. Solaris

Restoring dump from tape to SCSI disk

Hi Gurus, I need help. Mine is an Ultra 10 machine running on solaris 7. Problem with solaris 7 is, it can no longer recognize IDE disks greater that 10GB. My workaround is ro use an external SCSI disk since it is recognizable with solaris 7. I backup my filesystems (residing on the IDE... (2 Replies)
Discussion started by: domesat
2 Replies

9. Shell Programming and Scripting

Restoring problem on tape!

hi all , a messages appeared to me when i was checking my /var/adm/messages and the below code was in it Oct 6 13:15:21 medprod scsi: /pci@3,700000/SUNW,emlxs@0/fp@0,0/st@w21000024ff305234,7 (st1): Oct 6 13:15:21 medprod Restoring tape position at fileno=320,... (5 Replies)
Discussion started by: semaan
5 Replies

10. Red Hat

Issues restoring a large dump file

Post deleted. (0 Replies)
Discussion started by: Nobody_knows_me
0 Replies
dump(1M)																  dump(1M)

NAME
dump, rdump - incremental file system dump, local or across network SYNOPSIS
[option [argument ...] filesystem] [option [argument ...] filesystem] DESCRIPTION
The and commands copy to magnetic tape all files in the filesystem that have been changed after a certain date. This information is derived from the files and option specifies the date and other options about the dump. option consists of characters from the set The and commands work only on file systems of type If the given file system is not of type and will abort after printing an error message. Options This number is the "dump level". All files modified since the last date stored in file for the same file system at lesser levels will be dumped. If no date is determined by the level, the beginning of time is assumed. Thus, the option causes the entire file system to be dumped. The blocking factor is taken from the next argument (default is 10 if not specified). Block size is defined as the logical record size times the blocking factor. writes logical records of 1024 bytes. When dumping to tapes with densities of 6250 BPI or greater without using the option, the default blocking factor is 32. The density of the tape (expressed in BPIs) is taken from the next argument. This is used in calculating the amount of tape used per reel. The default value of 1600 assumes a reel tape. Place the dump on the next argument file instead of the tape. If the name of the file is writes to the standard output. When using this option should be specified, and the next argument supplied should be of the form Whenever and require operator attention, notify all users in group by means similar to that described by wall(1). The size of the dump tape is specified in feet. The number of feet is taken from the next argument. When the specified size is reached, and wait for reels to be changed. The default tape size value of 2300 feet assumes a reel tape. If the dump completes successfully, write on file the date when the dump started. This file records a separate date for each file system and each dump level. The format of is user-readable and consists of one free-format record per line: file system name, increment level, and dump date in ctime(3C) format. The file can be edited to change any of the fields if necessary. For each file system in print the most recent dump date and level, indicating which file systems should be dumped. If the option is set, all other options are ignored and exits immediately. Operates like but prints only file systems that need to be dumped. If no arguments are given, option is assumed to be and a default file system is dumped to the default tape. Sizes are based on 1600-BPI blocked tape; the raw magnetic tape device must be used to approach these densities. Up to 32 read errors on the file system are ignored. Each reel requires a new process; thus parent processes for reels already written remain until the entire tape is written. The command creates a server, or on the remote machine to access the tape device. and require operator intervention for any of the following conditions: o end of tape, o end of dump, o tape-write error, o tape-open error, or o disk-read error (if errors exceed threshold of 32). In addition to alerting all operators implied by the option, and interact with the control terminal operator by posing questions requiring or answers when it can no longer proceed or if something is grossly wrong. Since making a full dump involves considerable time and effort, and each establish a checkpoint at the start of each tape volume. If, for any reason, writing that volume fails, and will, with operator permission, restart from the checkpoint after the old tape has been rewound and removed and a new tape has been mounted. and periodically report information to the operator, including typically low estimates of the number of blocks to write, the number of tapes it will require, the time needed for completion, and the time remaining until tape change. The output is verbose to inform other users that the terminal controlling and is busy and will be for some time. Access Control Lists (ACLs) The optional entries of a file's access control list (ACL) are not backed up with and Instead, the file's permission bits are backed up and any information contained in its optional ACL entries is lost (see acl(5)). EXAMPLES
In the following example, assume that the file system is to be attached to the file tree at the root directory, This example causes the entire file system to be dumped on and specifies that the density of the tape is 6250 BPI. WARNINGS
will not backup a file system containing large files. Tapes created from file systems containing files with UID/GIDs greater than 60,000 will have a new magic number in the header to prevent older versions of restore(1M) from incorrectly restoring ownerships for these files. AUTHOR
and were developed by the University of California, Berkeley. FILES
Default file system to dump from. Default tape unit to dump to. New format-dump-date record. Dump table: file systems and frequency. Used to find group SEE ALSO
restore(1M), rmt(1M), fstab(4), acl(5). dump(1M)
All times are GMT -4. The time now is 03:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy