05-09-2018
Depends what you mean by "provision"?
Flash is usually used (1) for disaster recovery and/or (2) to clone a system.
Whether recovery or cloning the new system has the same node name, ip configuration, and other configs as the original. Be aware of that.
Why don't you want to do a fresh install?
9 More Discussions You Might Find Interesting
1. Solaris
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
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
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
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
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
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
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
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
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
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte
at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given.
During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is
long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO
tp(1)
BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.
HT(4)