Sponsored Content
Operating Systems Solaris Flash Archive Jumpstart with multiple ZFS Pools Post 303013506 by NoelzeN on Thursday 22nd of February 2018 08:34:55 AM
Old 02-22-2018
Flash Archive Jumpstart with multiple ZFS Pools

Hi,
I'm trying to get a Flash Archive Jumpstart Running with ZFS Filesystem. For Testing I set up a VirtualBox VM with 2 Disks attached. On the first disk I have the ZFS root pool, on the second Disk I have some more ZFS Pools which I use for 2 additional Zones I've set up. Restoring works fine if I just restore the Root pool since in the config File I can just mention the root pool, otherwise I get an error when booting saying something like multiple root pools are not allowed. Config looks like this:
Code:
install_type flash_install
archive_location nfs 192.168.0.220:/opt/jumpstart/FlashArchives/Client.archive
partitioning explicit
pool rpool 78g 4g 1g c0d0s0

When I add the line
Code:
 pool zones 55g auto auto c0d1s0

I get the following error when restoring:
Error: Field 1 - Multiple root pool keywords not allowed
Solaris Installation Program exited

Is there any way to do the Flash Archive Jumpstart with attitional Zones?

Last edited by MadeInGermany; 02-22-2018 at 02:20 PM.. Reason: added code tags
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Jumpstart and Flash Archives

Ladies and Gentlemen: I am short on time and need to get up to speed fast on the use of flash archives. I am very familiar with Jumpstart and have used it successfully for the past 5 years. The current project I am working on requires optimization of time and speed when deploying systems which is... (0 Replies)
Discussion started by: rambo15
0 Replies

2. Solaris

Flash installation with Jumpstart

I get following error while doing a flash installation. I 'm trying to deploy a flash archive created by our engineering team. I 'm trying to install it with ZFS root and the profile which i using is as following #more flash_profile_test install_type flash_install archive_location nfs... (3 Replies)
Discussion started by: fugitive
3 Replies

3. Solaris

ZFS root + Flash archive in update7

Has ZFS root is being supported in flash archive in the recently released update 7 .. i read a specific patch has been released for this , can anyone let me know that , and have anybody tested it if its working fine or not ? (1 Reply)
Discussion started by: fugitive
1 Replies

4. Solaris

difference between flash archive and jumpstart

Hi, Can anyone explains me the difference between solaris flash archive and jumpstart installation. Both are used to install many systems frm a centralized location , correct me if am wrong,. Clear view on this is really appreciable. Thanks in advance (3 Replies)
Discussion started by: rogerben
3 Replies

5. Solaris

zfs root flash archive issue

I have created a flash archive from a Ldom on T5220 with zfs root solaris 10_u8. But after creation of flar the info shows the content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s but not sun4v due to which i 'm unable to install this flash archive on another Ldom on the same host. Is... (0 Replies)
Discussion started by: fugitive
0 Replies

6. Solaris

Installing Sun Cluster on ZFS root pools

Hi All! I have been tasked with creating a clustered file system for two systems running Sol 10 u8. These systems have 3 zones each and the global zone has ZFS on the boot disk. We currently have one system sharing an NFS mount to both of these systems. The root zfs pool status (on the... (2 Replies)
Discussion started by: bluescreen
2 Replies

7. Solaris

Jumpstart client flash archive error....

Hi , I am facing this issue while restoring flash archive from jumpstart server.The image was aroung 9 gb (5.9 release) and we have restored the other images successfully bigger than this size to other machines we have never faced this issue .Please advice me on this issue . Extracted 100 %... (0 Replies)
Discussion started by: knl.sundeep
0 Replies

8. Solaris

ZFS and jumpstart

I am building a new server on sol10_X86. I am new to ZFS, this will be one of the first systems to use it. I would like to have /opt /usr and a /u01 as separate file systems from the main ZFS pool. I know that this goes against the basic idea of ZFS, but this is so I can restrict the size/usage... (1 Reply)
Discussion started by: robsonde
1 Replies
AMZFS-SENDRECV(8)					  System Administration Commands					 AMZFS-SENDRECV(8)

NAME
amzfs-sendrecv - Amanda script to create zfs sendrecv DESCRIPTION
amzfs-sendrecv is an Amanda application implementing the Application API. It should not be run by users directly. It create a zfs snapshot of the filesystem and backup the snapshot with 'zfs send'. Snapshot are kept after the backup is done, this increase the disk space use on the client but it is neccesary to be able do to incremental backup. If you want only full backup, you can disable this feature by setting the KEEP-SNAPSHOT property to 'NO'. Only the restoration of the complete backup is allowed, it is impossible to restore a single file. The application is run as the amanda user, it must have many zfs priviledge: zfs allow -ldu AMANDA_USER mount,create,rename,snapshot,destroy,send,receive FILESYSTEM Some system doesn't have "zfs allow", but you can give the Amanda backup user the rights to manipulate ZFS filesystems by using the following command: usermod -P "ZFS File System Management,ZFS Storage Management" AMANDA_USER This will require that your run zfs under pfexec, set the PFEXEC property to YES. The format of the diskdevice in the disklist (DLE) must be one of: Desciption Example ---------- ------- Mountpoint /data ZFS pool name datapool ZFS filesystem datapool/database ZFS logical volume datapool/dbvol The filesystem doesn't need to be mounted. PROPERTIES
This section lists the properties that control amzfs-sendrecv's functionality. See amanda-applications(7) for information on the Application API, application configuration. DF-PATH Path to the 'df' binary, search in $PATH by default. KEEP-SNAPSHOT If "YES" (the default), snapshot are kept after the backup, if set to "NO" then snapshot are no kept and incremental backup will fail. ZFS-PATH Path to the 'zfs' binary, search in $PATH by default. PFEXEC-PATH Path to the 'pfexec' binary, search in $PATH by default. PFEXEC If "NO" (the default), pfexec is not used, if set to "YES" then pfexec is used. EXAMPLE
In this example, a dumptype is defined to use amzfs-sendrecv application to backup a zfs filesystem. define application-tool amzfs_sendrecv { comment "amzfs-sendrecv" plugin "amzfs-sendrecv" #property "DF-PATH" "/usr/sbin/df" #property "KEEP-SNAPSHOT" "YES" #property "ZFS-PATH" "/usr/sbin/zfs" #property "PFEXEC-PATH" "/usr/sbin/pfexec" #property "PFEXEC" "NO" } define dumptype user-zfs-sendrecv { program "APPLICATION" application "amzfs_sendrecv" } SEE ALSO
amanda(8), amanda.conf(5), amanda-client.conf(5), amanda-applications(7) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHOR
Jean-Louis Martineau <martineau@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.3 01/10/2013 AMZFS-SENDRECV(8)
All times are GMT -4. The time now is 02:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy