Sponsored Content
Full Discussion: Using flar
Operating Systems Solaris Using flar Post 303017033 by fretagi on Tuesday 8th of May 2018 09:22:56 AM
Old 05-08-2018
Using flar

Hi

I have systems running UFS and ZFS file system type, and I need to create images of them ( in HP-UX ) we call it ignite, but in my case I dont have tape drives attached to the servers. I have read about flar archives, but the do I have to create those images in single user mode or using the current run level?
 

9 More Discussions You Might Find Interesting

1. Solaris

Flar Images

I once found a document on the web describing how to build partition flar images instead of having just the one large one. I have managed this but am having problems extracting the subsequent flar archives. I ahve built the system from a jumpstart server and now need to add the program images etc... (0 Replies)
Discussion started by: 58fairlane
0 Replies

2. Solaris

unable to create flar

Hello friend, Now i'm doing JDS3.1 in v440 servers.while checking the lustatus command getiing out like this lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- --------... (0 Replies)
Discussion started by: rjay.com
0 Replies

3. Solaris

Jumpstart / Flar problems Solaris 10 8/07

Hi, Im trying to make a jumpstart dvd using an flar archive. I have done this before on earlier releases of Solaris 10 (Sparc). Im now trying to do the same with the 8/07 release.. Problem : After the server is installed (during first boot ) the Select keyboard layout dialog appears. I... (5 Replies)
Discussion started by: s93366
5 Replies

4. Solaris

Jumpstart with flars: looking for /tmp/flar

I'm a little stumped here. If anyone has seen this, please point me in the right direction Little background first: I maintain a Solaris corporate build, currently based on Solaris 10u4 (08/07). This build is deployed using flars through jumpstart, wanboot, and jumpstart DVD. In the lab, I have... (1 Reply)
Discussion started by: System Shock
1 Replies

5. Solaris

FLAR Tape Backup/Restore

I have a T2000 server that is JumpStarted with Solaris 10 from the JumpStart server. Host name and IP address is changed after that. Then we backup the server using FLAR to tape: root.damas# date; flarcreate -c -t -n "Sol10_cairo_image" -a "engineering@starsolutions.com" -R / /dev/rmt/0n ;... (2 Replies)
Discussion started by: StarSol
2 Replies

6. Solaris

flar on linux???

Hi admins, As we can create flash archieve on solaris with flarcreate command utility, so is there any utility like this on Linux to create flah archieves ?? (10 Replies)
Discussion started by: snchaudhari2
10 Replies

7. Solaris

"flar create" produces a tiny flar image of rpool

Hi, can someone help with the following? I got 1x146GB disk which is span by just one zfs rpool. When issue for example: as you can see in above output the flar is very small, just around 10KB rpool with all data sets has several GB so this can't be good image. This is on the Solaris 10... (3 Replies)
Discussion started by: TomSu
3 Replies

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

9. 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
device_allocate(4)						   File Formats 						device_allocate(4)

NAME
device_allocate - device_allocate file SYNOPSIS
/etc/security/device_allocate DESCRIPTION
The device_allocate file is an ASCII file that resides in the /etc/security directory. It contains mandatory access control information about each physical device. Each device is represented by a one- line entry of the form: device-name;device-type;reserved1;reserved2;auths;device-exec where: device-name Represents an arbitrary ASCII string naming the physical device. This field contains no embedded white space or non-printable charac- ters. device-type Represents an arbitrary ASCII string naming the generic device type. This field identifies and groups together devices of like type. This field contains no embedded white space or non-printable characters. The following types of devices are currently managed by the system: audio, sr (represents CDROM drives), fd (represents floppy drives), st (represents tape drives), rmdisk (removable media devices). reserved1 On systems configured with Trusted Extensions, this field stores a colon-separated (:) list of key-value pairs that describe device allocation attributes used in Trusted Extensions. Zero or more keys can be specified. The following keys are currently interpreted by Trusted Extensions systems: minlabel Specifies the minimum label at which device can be allocated. Default value is admin_low. maxlabel Specifies the maximum label at which device can be allocated. Default value is admin_high. zone Specifies the name of the zone in which device is currently allocated. class Specifies a logical grouping of devices. For example, all Sun Ray devices of all device types. There is no default class. xdpy Specifies the X display name. This is used to identify devices associated with that X session. There is no default xdpy value. reserved2 Represents a field reserved for future use. auths Represents a field that contains a comma-separated list of authorizations required to allocate the device, an asterisk (*) to indicate that the device is not allocatable, or an '@' symbol to indicate that no explicit authorization is needed to allocate the device. The default authorization is solaris.device.allocate. See auths(1). device-exec The physical device's data clean program to be run any time the device is acted on by allocate(1). This ensures that unmanaged data does not remain in the physical device between uses. This field contains the filename of a program in /etc/security/lib or the full pathname of a cleanup script provided by the system administrator. Notes on device_allocate The device_allocate file is an ASCII file that resides in the /etc/security directory. Lines in device_allocate can end with a `' to continue an entry on the next line. Comments can also be included. A `#' makes a comment of all further text until the next NEWLINE not immediately preceded by a `'. White space is allowed in any field. The device_allocate file must be created by the system administrator before device allocation is enabled. The device_allocate file is owned by root, with a group of sys, and a mode of 0644. EXAMPLES
Example 1 Declaring an Allocatable Device Declare that physical device st0 is a type st. st is allocatable, and the script used to clean the device after running deallocate(1) is named /etc/security/lib/st_clean. # scsi tape st0; st; reserved; reserved; solaris.device.allocate; /etc/security/lib/st_clean Example 2 Declaring an Allocatable Device with Authorizations Declare that physical device fd0 is of type fd. fd is allocatable by users with the solaris.device.allocate authorization, and the script used to clean the device after running deallocate(1) is named /etc/security/lib/fd_clean. # floppy drive fd0; fd; reserved; reserved; solaris.device.allocate; /etc/security/lib/fd_clean Making a device allocatable means that you need to allocate and deallocate it to use it (with allocate(1) and deallocate(1)). If a device is not allocatable, there is an asterisk (*) in the auths field, and no one can use the device. FILES
/etc/security/device_allocate Contains list of allocatable devices ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
auths(1), allocate(1), bsmconv(1M), deallocate(1), list_devices(1), auth_attr(4), attributes(5) NOTES
The functionality described in this man page is available only if Solaris Auditing has been enabled. See bsmconv(1M) for more information. On systems configured with Trusted Extensions, the functionality is enabled by default. On such systems, the device_allocate file is updated automatically by the system. SunOS 5.11 12 May 2008 device_allocate(4)
All times are GMT -4. The time now is 10:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy