Sponsored Content
Full Discussion: FLAR Tape Backup/Restore
Operating Systems Solaris FLAR Tape Backup/Restore Post 302341723 by StarSol on Thursday 6th of August 2009 12:38:09 PM
Old 08-06-2009
Thanks for the response! Yes, the JumpStart server was still active at the time. When Attempted to do the restore while the JumpStart server was inactive, we did not get the "Solaris Interactive Installation" menu so "F4_Flash" can be chosen; instead, another menu (for frash install from disk) started; asking for langauge, locales, etc.

How do we restore from tape (FLAR) without the JumpStart server (and its influence)?
 

10 More Discussions You Might Find Interesting

1. HP-UX

Backup Tape Restore?

I am trying to do a restore on a backup tape (DDS2) and am having a little trouble. For one, I dont know how the tape was made, whether is was tar, cpio, dump..etc. Anyone know how to restore a tape without knowing the format of the backup? (5 Replies)
Discussion started by: bake255
5 Replies

2. AIX

Restore a tape

Hello everyone I have a tape with some information that I got to restore, the tape was made with the fbackup command in a hp box. My question is that I have to restore in a Ibm box, how can I do this ? Thanks in advance (1 Reply)
Discussion started by: lo-lp-kl
1 Replies

3. UNIX for Dummies Questions & Answers

Mounting DLT tape and to backup file to tape

Hi there: I'm new here Can anyone help me: I have DS15 Alpha server : Unix 5.1B Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit. What is the exact comman to mount the DLTape IV?? How do i make backuo @ copy file to the tape? Thanx to all (0 Replies)
Discussion started by: ayzeayem
0 Replies

4. UNIX for Dummies Questions & Answers

Check backup file size on backup tape

Hi, I performed backup on tape and I want to append more files to my previous backup on the same backup tape. But before I do that I need to know the backup file size of the first backup I performed so that I know the available size on the backup tape. Can someone help me what command I will use... (0 Replies)
Discussion started by: ayhanne
0 Replies

5. SCO

Backup to SCSI Tape Backup aborts

I am trying to make a full backup of my system using the cpio command. The Tape Unit is a SCSI DDS. The process started fine but after about 30 minutes, it just stopped and showed the following message: 1755 Signal 31 - Core dumped Any idea of what is causing this and how to fix it? ... (4 Replies)
Discussion started by: zionpc
4 Replies

6. UNIX for Dummies Questions & Answers

I cannot restore my backup from my exabyte tape drive

Hi All, I have an old Unix system used by a client as a backup server.I installed an Exabyte tape drive and on restarting the server and during POSTs, the system recognizes the tape drive with its scsi id. On running the command devstat -IAF, the system sees the tape drive quite well. When... (1 Reply)
Discussion started by: ezleone
1 Replies

7. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

8. AIX

Tape backup/restore Date/time

good morning everyone how can i find the tape backup/restore Date/time? (2 Replies)
Discussion started by: Portabello
2 Replies

9. Solaris

Solaris 8 Flar Creation/Restore

I'm new to utilizing Solaris... especially the old 8 version, but I'm trying to find out if there is a way to create a Flash Archive of a disk that can be restored on a smaller size disk or disk of varying size? (2 Replies)
Discussion started by: scifi_vixen
2 Replies

10. Solaris

Solaris 10 Restore from flar image

Hi! I want to migrate Sun Fire v240 server (sun4u) with Solaris 10 update 6 to LDOM virtual host (sun4v). I was mount NFS directory from another server in /mnt and did this steps on v240 1) I add to the /var/sadm/system/admin/.platform PLATFORM_GROUP=sun4v # cat... (1 Reply)
Discussion started by: pbubentsov
1 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 01:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy