Ufsrestore on Solaris 7

When restoring multiple files on Solaris 7 using ufsrestore (ex. ufsrestore xf /dev/rmt/0 ./file-1 ./file-2), can anyone tell me if the ufsrestore command sorts the files by inode (the way they are written to tape by ufsdump) before attempting the restore? I have a script that I am working on that I am planning on sorting the files by inode before feeding the ufsrestore command. This step would be totally unnecessary if ufsrestore does the sorting. If they aren't sorted, then it becomes necessary to prevent the tape from rewinding between files and thrashing the tape drive and media.

Quoting from Solaris 8 System Administrator's Reference:
(I assume this command behaves consistently for both Solaris 7 and 8)
You must do a level 0 dump after a full restore. Because ufsrestore runs in user mode, <b>it has no control over inode allocation</b>. ufsrestore repositions the files, although it does not change their contents. Thus, you must do a full dump to get a new set of directories reflecting the new file positions so that later incremental dumps are correct.

Similar Messages

Backup issues (ufsdump/ufsrestore) under solaris 10

Hello all,
We are in the process of migrating to Solaris 10 from Solaris 8.
On our Solaris 8 systems with 2 HDDs we have a script that does a full backup of one disk (slice by slice) on to another using ufsdump/ufsrestore + boot record. The idea is that if one disk becomes corrupt logically/physically we can boot off the backup disk and continue using the system.
This worked fine under Solaris 8. We tried to do the same under Solaris 10 and noticed some unexpected behaviour when we tried to boot off the backup disk. Solaris 10 started "reconfiguring services" just like it does it when you install the OS fresh with the message:
Loading smf(5) service descriptions: xx/117
Somehow Solaris 10 "knew" that it was booted from a different device than last time.
My question would be: how does Solaris 10 know this and could we "fool" it into thinking that it was always installed on a backup disk, so it doesn't reconfigure itself every time new backup is made (and used).

"... The real question is "how can I be sure that except smf there is nothing else in the OS affected by HDD change" and that is what I meant..."
The fact that you use ufsdump on mounted (I am guessing that you are doing so :-) file systems is risky!. Alternatively, you can create snapshots (fssnap(1M)) for the file systems that you are going to ufsdump on.
If your main aim is to replicate and reduce down time in case of root disk failure, a better solution is make use of mirriong via Solaris Volume Manager (aka SDS or md(7D)). Mirror does not guard against human errors though, such as accidentally deletion of crucial files :-) (which a backup strategy can guard against).
Hope this helps.
Regards,
S.T.Chang

Solaris 8 ufsrestore issues

Hello all,
this is my first post here.
I am experiencing a strange issue when attempting to do a ufsrestore of an entire backed up OS (Sol 8) The restore goes fine but some time after the new server is up and running I start getting these errors;
# Jun 13 01:20:00 usmlsu52new.arrow.com cron[23056]: open_module: stat(/usr/lib/security/pam_projects.so.1) failed: No such file or directory
Jun 13 01:20:00 usmlsu52new.arrow.com cron[23056]: load_modules: can not open module /usr/lib/security/pam_projects.so.1
# ls | more
ls: Cannot find /usr/lib/ld.so.1
more: Cannot find /usr/lib/ld.so.1
Killed
# Jun 13 01:20:00 usmlsu51new.arrow.com cron[2638]: open_module: stat(/usr/lib/security/pam_projects.so.1) failed: No such file or directory
Jun 13 01:20:00 usmlsu51new.arrow.com cron[2638]: load_modules: can not open module /usr/lib/security/pam_projects.so.1
I now can't do anything on the server? I am at the root prompt but when I try to run a ls, df -k, cp it just gives me the same error complaining about the ld.so.1 file missing??
Can anyone help me with this
Thanks
Paul.

Could be the library file is missing or corrupted. Need to copy the good version of the library file.
Since, the system is up, the recovery steps are as follows:
1) /usr/sbin/static/mv /usr/lib/ld.so.1 /usr/lib/ld.so.1.buggy
2) /usr/sbin/static/cp /etc/lib/ld.so.1 /usr/lib
It worked for me on Solaris 9 and Solaris 10.
In case, the server doesn't boot, need to boot of media, mount the root file system and /usr, if /usr is a separate filesystem and perform the above commands.
-Siddi

Solaris 10 boot error after ufsrestore

Hi,
We have restored a V490 using ufsrestore and are having a few issues.
The root partitions of the original V490 were mirrored by SVM so I basically restored /, /var, /opt and /usr and changed vfstab (among other things) and also commented out the MD lines in system. (for info we have done numerous of these restores on T2000's albeit they were hardware mirrored).
The new boot disk partitions are c1t1d0xx and I can mount /ust on c1t1d0s6 from the boot disk, ive cut/pasted vfstab at the end of this thread...
After checking everything I rebootedfrom the other disk but unfortunately I receive this error when booting:
Rebooting with command: boot disk1 -s
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@1,0 File and args: -s
SunOS Release 5.10 Version Generic_147440-10 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
sorry, variable 'xmit_hiwat' is not defined in the 'udp' module
sorry, variable 'udp_recv_hiwat' is not defined in the 'udp' module
Booting to milestone "milestone/single-user:default".
Hostname: SERVER
ERROR: svc:/system/filesystem/root:default failed to mount /usr (see 'svcs -x' for details)
Requesting System Maintenance Mode
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
Mar 14 16:00:56 su: 'su root' succeeded for root on /dev/console
-sh: /bin/i386: not found
-sh: /usr/sbin/quota: not found
-sh: /bin/cat: not found
-sh: /bin/mail: not found
Ive gone back and checked, double (triple) checked vfstab, put a space at the end but im at my wits end...
I am unable to enter any commands at the prompt and when I reboot to the original disk there is nothing in svc logs to indicate what the issue is.
Any assistance would be appreciated.
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c1t1d0s1 - - swap - no -
/dev/dsk/c1t1d0s0 /dev/rdsk/c1t1d0s0 / ufs 1 no -
/dev/dsk/c1t1d0s6 /dev/rdsk/c1t1d0s6 /usr ufs 1 no -
/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /var ufs` 1 no -
/dev/dsk/c1t1d0s5 /dev/rdsk/c1t1d0s5 /opt ufs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
#/dev/zvol/dsk/tankroot/swap - - swap - no -
sharefs - /etc/dfs/sharetab sharefs - no -
Thanks.

Hi, thanks for the reply...
Ive created the /usr usiong the same criteria as the V490 we took the ufsdump from
/dev/dsk/c1t1d0s6 /dev/rdsk/c1t1d0s6 /usr ufs 1 no -
Ive checked the disk hasnt changed to something else and used the standard ufsrestore -rf command to restore the data.
The original V490 OS was mirrored using SVM but ive removed all traces of SVM from vfstab and system and am now going to try restoring /usr back into / itself and see what happens, ive a feeling I will receive the same error message though but worth a try.
One google hit suggested a blank line at the end of vfstab but ive tried that as well to no avail.

How to mount USB & CDROM drives from single user mode - Solaris boot disk?

Hi All,
I need to carry out ufsrestore on a single newly replaced system disk (no redundancy / mirroring) from either USB or CDROM drives from the following steps:
( i ) GRUB => e, e, cdrom –s, Enter, b (boot from Solaris 10 x86 media).
( ii ) Choose menu 1 for Install Solaris Interactive Mode to reach single user mode.Below are the commands that I have tried in single user mode without success:
mount –r –F pcfs /dev/dsk/c1t0d0p0 /cdrom (after unmount Solaris CD)
mount: /dev/dsk/c1t0d0p0 is not a DOS filesystem.
svcadm –v enable smserver
svcadm: Pattern ‘smserver’ doesn’t match any instances
svcadm enable autofs
svcadm: Pattern ‘autofs’ doesn’t match any instances
devfsadm
devfsadm: mkdir failed for /dev 0s1ed: Read-only file system
mkdir /mnt
mkdir: Failed to make directory “/mnt”; Read-only file systemPart of the problem is due to the current READ ONLY filesystems which does not allow the creation of mount point such as /mnt.
I have been able to create both / root (/dev/dsk/c1t0d0s0) and /export/home (/dev/dsk/c1t0d0s0) filesystems with newfs that are awaiting for restore using ufsrestore.
The only option I am left with is to attach a secondary disk to install Solaris 10 on either of them before bring the system to multi-user mode so that service such as volmgt, autofs, volfs are available to access USB & CDROM drives.
Any suggestion on how to resolve this issue?
Many thanks,
Jack

Hi JKGN,
Is the directory a located under the root filesystem. ie /a? Are there any other mount point for say USB drive as well? I am not in a position to try it out right now but will get back
to you soon on whether /a exist or not.
Btw, the last thing I managed to do on this system at the time was added a secondary 1TB internal disk with the intention to restore both / and /export/home data onto this disk while
making use of all the disk device management services such as the following services only available in a fully installed Solaris system (both single & multi-user modes) installed on the
primary disk:
# svcs smserver
STATE          STIME    FMRI
online         Jun_08   svc:/network/rpc/smserver:default
# svcs autofs
STATE          STIME    FMRI
online         Jun_08   svc:/system/filesystem/autofs:default
# devfsadm
# iostat -En
c1t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: SAMSUNG HD321KJ Revision: 0-11 Serial No:
Size: 320.07GB <320072932864 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 41 Predictive Failure Analysis: 0
c0t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
Vendor: PHILIPS Product: DVD+-RW DVD8801 Revision: AD21 Serial
Size: 17.54GB <17538875392 bytes>
Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
Illegal Request: 10 Predictive Failure Analysis: 0
c2t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: JetFlash Product: Transcend 16GB   Revision: 1100 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 7 Predictive Failure Analysis: 0
# rmformat
Looking for devices...
     1. Volmgt Node: /vol/dev/aliases/cdrom0
        Logical Node: /dev/rdsk/c0t0d0s2
        Physical Node: /pci@0,0/pci-ide@1f,1/ide@0/sd@0,0
        Connected Device: PHILIPS DVD+-RW DVD8801 AD21
        Device Type: DVD Reader/WriterHowever, I was disappointed that "iostat -En" has not found the secondary disk (1 TB) even though it was available earlier, for Solaris installation as the only disk on the same system.
As a result, I am left with no option but the need to rebuild this system with only a single primary disk while in single user mode. However, the single user mode that I am in is the
one from Solaris installation disk with restrictive (_cannot create folder for mount point or running disk management utilities_) capability such as those services just covered, compared to one from a completed Solaris installation system with full access to all filesystems and utilities / commands in general.
I would very much value your assistance on how to mount both CD & USB in this restrictive limited Read Only OS (assume that it is running from memory) in order to get complete access to
the blank primary disk so that full restore with ufsrestore could take place.
Thanks in advance,
Jack
Edited by: 797805 on 9/06/2012 04:15

How to restore / on Solaris 8 X86

Hi,
I new the procedure:
newfs /dev/rdsk/c0t0d0s0
mount /dev/dsk/c0t0d0s0 /a
/usr/lib/fs/ufs/ufsrestore
chdir /usr/platform/`uname -i`/lib/fs/ufs
/usr/platform/i86pc/lib/fs/ufs
/usr/sbin/installboot pboot bootblk /dev/rdsk/c0t0d0s0
But on Solaris 8, you also have the following filesystem to restore:
/dev/dsk/c0t0d0p0:boot
10579 1668 8911 16% /boot
What should I do to backup/restore /dev/dsk/c0t0d0p0:boot? And will restoring these 2 filsesystems be enough to also restore the boot loader?
Thanks.

Technically... you should restore to Snow Leopard (or whatever OS you had before Lion). "You" purchased a license to install Lion on each of your machines under your Apple ID. The Apple ID of the purchaser is also required to use recovery (which the purchaser will not have). Of course if you want to purchase the USB flash drive with Lion on it and include that with your old machine, that would be fine.

Local mods - upgrading to Solaris 8

Hi
I will be upgrading from Solaris 2.6 to Solaris 8.
How much will I have to re-do in the way of the configuration of things like cron jobs, rtel printers, lpadmin printers, serial port (aurora) configuration and ?any other local modifications?
Will I have to reinstall the aurora serial port drivers?
Are the /etc/rcn.d directory contents and /etc/inittab preserved?
Thanks
D

"Most" user configurable files will "survive" an upgrade but it is up to you to find out if such things as aurora serial port drivers are supported, or will even work ,in Solaris 8 or if an upgrade is required. Your primary network interface may be the only interface to survive the upgrade. Cron jobs should be OK.
The only way to protect yourself is to have a level 0 ufsdump of all your OS slices to a local tape drive. Preferably this will be done from a cdrom boot. Don't really want to dump "live" files. You can then interactivly ufsrestore missing files.
If your upgrade turns sour, or your filesystems are too small for Solaris 8 then a ufsrestore may be your only recourse.
Please try to find InfoDoc 16141 - Solaris Upgrade Tips & Checklist.
Please ensure your system boots before any upgrade begins.

Upgrading to Solaris 8 - local modifications

I will be upgrading from Solaris 2.6 to Solaris 8. (SUN Enterprise 450)
How much will I have to re-do in the way of the configuration of things like cron jobs, rtel printers, lpadmin printers, serial port (aurora) configuration and ?any other local modifications?
Will I have to reinstall the aurora serial port drivers?
Are the /etc/rcn.d directory contents and /etc/inittab preserved?
Thanks
D

"Most" user configurable files will "survive" an upgrade but it is up to you to find out if such things as aurora serial port drivers are supported, or will even work ,in Solaris 8 or if an upgrade is required. Your primary network interface may be the only interface to survive the upgrade. Cron jobs should be OK.
The only way to protect yourself is to have a level 0 ufsdump of all your OS slices to a local tape drive. Preferably this will be done from a cdrom boot. Don't really want to dump "live" files. You can then interactivly ufsrestore missing files.
If your upgrade turns sour, or your filesystems are too small for Solaris 8 then a ufsrestore may be your only recourse.
Please try to find InfoDoc 16141 - Solaris Upgrade Tips & Checklist.
Please ensure your system boots before any upgrade begins.

Migrate Solaris 10 update 4 Native SunFire V245 to zone on T5-2 update 11

I create the flar on this solaris 10.
more /etc/release
                       Solaris 10 8/07 s10s_u4wos_12b SPARC
           Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
                        Use is subject to license terms.
                            Assembled 16 August 2007
When i try to install on the server T5-2 this messages send me on the installation.
root@sgc00 # zoneadm -z desarrolloB install -u -a /var/tmp/des.flar
      Archivo de registro: /var/tmp/desarrolloB.install_log.dma4n1
    Realizando instalaci▒n: Este proceso puede tardar varios minutos...
Postprocessing: This may take a while...
   Postprocesamiento: Updating the zone software to match the global zone...
   Postprocesamiento: ERROR: Updating the Zone software failed
        Resultado: Postprocesamiento fallido.
        Resultado: *** La instalaci▒n ha fallado ***
      Archivo de registro: /var/tmp/desarrolloB.install_log.dma4n1
root@sgc00 # more /var/tmp/desarrolloB.install_log.dma4n1
[viernes 6 de febrero de 2015 10:49:24 PM CST]       Archivo de registro: /var/tmp/desarrolloB.install_log.dma4n1
[viernes 6 de febrero de 2015 10:49:24 PM CST] Starting pre-installation tasks.
[viernes 6 de febrero de 2015 10:49:24 PM CST] Installation started for zone "desarrolloB"
[viernes 6 de febrero de 2015 10:49:24 PM CST] flash archive
[viernes 6 de febrero de 2015 10:49:24 PM CST]     Realizando instalaci▒n: Este proceso puede tardar varios minutos...
[viernes 6 de febrero de 2015 10:49:24 PM CST] cd /zonas/desarrolloB/root && cat /var/tmp/des.flar | install_flar
[viernes 6 de febrero de 2015 10:53:57 PM CST]   Sanity Check: Passed. Looks like a native system.
[viernes 6 de febrero de 2015 10:53:57 PM CST] Postprocessing: This may take a while...
[viernes 6 de febrero de 2015 10:53:57 PM CST] running: p2v -u desarrolloB /zonas/desarrolloB
[viernes 6 de febrero de 2015 10:53:57 PM CST]    Postprocesamiento: Creando puntos de montaje
[viernes 6 de febrero de 2015 10:54:05 PM CST]    Postprocesamiento: Updating the zone software to match the global zone...
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWjato 2.1.5,REV=2005.04.06.08.07 para versi▒n 2.1.2,REV=2005.01.09.23.05
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWjhrt 2.0,REV=2007.06.15 para versi▒n 2.0,REV=2006.10.31
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWmcon 3.1,REV=2010.05.26.22.06 para versi▒n 3.0.2,REV=2006.12.08.20.48
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWmconr 3.1,REV=2010.05.26.22.36 para versi▒n 3.0.2,REV=2006.12.08.20.48
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWmcos 3.1,REV=2010.05.26.22.36 para versi▒n 3.0.2,REV=2006.12.08.20.48
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWmcosx 3.1,REV=2010.05.26.22.36 para versi▒n 3.0.2,REV=2006.12.08.20.48
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWmctag 3.1,REV=2010.05.26.22.06 para versi▒n 3.0.2,REV=2006.12.08.20.48
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWservicetagr 1.1.5,REV=2009.09.23.10.58 para versi▒n 1.0,REV=2007.05.21.20.36
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWservicetagu 1.1.5,REV=2009.09.23.10.58 para versi▒n 1.0,REV=2007.05.21.20.36
zoneadm: zone 'desarrolloB': ERROR: intento de descargar paquete SUNWstosreg 1.1.5,REV=2009.09.23.10.58 para versi▒n 1.0,REV=2007.05.21.20.36
[viernes 6 de febrero de 2015 10:54:11 PM CST] ERROR: Updating the Zone software failed
[viernes 6 de febrero de 2015 10:54:11 PM CST]         Resultado: Postprocesamiento fallido.
[viernes 6 de febrero de 2015 10:54:11 PM CST]
[viernes 6 de febrero de 2015 10:54:11 PM CST]         Resultado: *** La instalaci▒n ha fallado ***
[viernes 6 de febrero de 2015 10:54:11 PM CST]       Archivo de registro: /var/tmp/desarrolloB.install_log.dma4n1
and i can't install the zone.

Hi , try with this
In the new server:
zonecfg -z zona1
create -b
set zonepath=/export/zona1
set autoboot=true ( or false )
exit
zoneadm list -cv ( check if the zone was created)
root@GlobalZone # zoneadm list -cv
ID NAME             STATUS     PATH
0 global           running    /
- ZONA1          configured /export/zona1
root@GlobalZone # chmod 700 /export/zona1
In the old server :
ufsdump -0f - / |ssh -l root 10.xx.xx.33 "(cd /export/zona1;ufsrestore -rf -)"
where 10.xx.xx.33 is the ip address of the new server
In the new server
# zoneadm -z zona1 attach -U ( this command uptodate all packages from Global Zone to NonGlobalZone )
# zoneadm -z zona1 ready
After this
You have to copy the files /etc/inet/hosts and sudoers for example, from the old server
in the old server
# scp /etc/inet/hosts [email protected]:/export/zona1/root/etc/inet/hosts
# scp /usr/local/etc/sudoers [email protected]:/export/zona1/root/usr/local/etc/sudoers
In the new server
# zoneadm -z zona1 halt
# zoneadm -z zona1 boot
If you have any trouble, or need explanation in Spanish , let me know
regards
Diego

Difficulty with SAN boot of solaris 10 (on V245) from HP EVA 4000 -

Hi
This is my first post. I'm trying to get my head around what's preventing me booting a V245 solaris 10 from a LUN presented from an HP EVA 4000.
The machine boots up ok from a local disk. So, i've done the LUN masking (presentation) on the EVA and the Brocade zoning - solaris can see the disk.
I've formated it close to the current internal root disk, and had used ufsdump/ufsrestore and installboot to copy the contents of / onto the new LUN , which i had mounted as /mnt.
My problem is i just can't seem to get at the new disk at the ok prompt - i'm never quite sure that i'm booting from the correct disk.
I believe all the compatibility with o/s qlc card drivers and the EVA are in order.
The qlc HBA is as follows:
Sun SG-XPCI2FC-QF2/x6768A 1077 2312 1077 10A and have suitable patch 119139-33
Here's some output:
root@bwdnbtsl02# uname -a
SunOS bwdnbtsl02 5.10 Generic_137111-01 sun4u sparc SUNW,Sun-Fire-V245
root@bwdnbtsl02#
root@bwdnbtsl02# luxadm probe
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node WWN:50001fe15009df00 Device Type:Disk device
Logical Path:/dev/rdsk/c4t600508B4001066A60000C00002B50000d0s2
root@bwdnbtsl02#
Now down at ok prompt, probe-scsi-all can see the EVA (HSV) LUNS
(Here's a sample of the output)
ok probe-scsi-all
/pci@1f,700000/pci@0/SUNW,qlc@2,1
************************* Fabric Attached Devices ************************
Adapter portId - 640100
Device PortId 640000 DeviceId 1 WWPN 210000e08b8a3e4f
Device PortId dc0000 DeviceId 2 WWPN 50001fe15009df09
Lun 0 HP HSV200 6220
Lun 1 DISK HP HSV200 6220
Device PortId d20000 DeviceId 3 WWPN 50001fe150092f19
Lun 0 HP HSV200 6220
/pci@1f,700000/pci@0/SUNW,qlc@2
************************* Fabric Attached Devices ************************
Adapter portId - 630100
Device PortId 630000 DeviceId 1 WWPN 210100e08baa3e4f
Device PortId 780000 DeviceId 2 WWPN 50001fe15009df08
Lun 0 HP HSV200 6220
Lun 1 DISK HP HSV200 6220
Device PortId 6e0000 DeviceId 3 WWPN 50001fe150092f18
Lun 0 HP HSV200 6220
So, i attempt to boot with the following:
ok boot /pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0/disk@w50001fe15009df08,0:a
Boot device: /pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0/disk@w50001fe15009df08,0:a File and args:
Can't read disk label.
Can't open disk label package
Can't open boot device
{1} ok
If anyone can put me straight here i'd be most grateful.
thanks john

hi,guys:
i am interesting in your question. i have never try it like your experience.
maybe the cause is drive . either the OS is running . the drive can load. or relation with the style of server .
i think you can try it like the following again.
when you install OS , you chocie EVA disk .
remeber . if the test is complete. you must tell me .
the following is my contact: [email protected]
best regards

Cloning Solaris 10 with zones

What is the best method to use when cloning a Solaris machine with zones, to ensure all software is included and can be easily installed
on new hardware?
Thank you!

If you use UFS, then ufsdump/ufsrestore
If you use ZFS, then zfs send/zfs receive
But, if you are using hardware or software RAID, you can also try to move one disk to an another machine.
You can see with these simple examples, that you have several methods and it depends how you configured your machine, Solaris and the zones. And finally, it depends too what is the source machine and what is the target machine, and how they are configured.

Boot from san in solaris 11

Hi,
Thanks in advance.
I have a solaris 11 set up with SPARC(sunfire v-250). I wanted to set up a boot from san environment in Solaris 11.
1) In solaris 10 I used to do set up using ufsdump command and the further steps. Now in solaris 11 the command ufsdump cannot be used since the native file system has changed to zfs.
2) When I tried to create a boot environment using beadm utility, I am able to create and activate BE in the san(SCSI) disk. But when I activated the new BE, status of new BE is changed to "R" and that of the current BE is still "NR" (which should be N, as per the behaviour of beadm). When I reboot the system it is again getting booted in the same old BE. I tried by setting the boot-device in OBP as the new san disk, which is giving error as "Does not appear to be an executable".
In solaris 10 i used lucreate for creating zfs BE, but lucreate command is not present solaris 11.
Can anybody help me creating a SAN boot environment either with ufs or zfs filse system?
Thanks and Regards
Maneesh

Glad to hear that you have other supportable systems that you can try this with.
881312 wrote:
1) In solaris 10 I used to do set up using ufsdump command and the further steps. Now in solaris 11 the command ufsdump cannot be used since the native file system has changed to zfs. With zfs, the analogs to ufsdump and ufsrestore are 'zfs send' and 'zfs receive'. The process for creating an archive of a root pool and restoring it is documented in the ZFS admin guide at http://docs.oracle.com/cd/E23824_01/html/821-1448/recover-1.html#scrolltoc. Note that instead of sending it to a file and receiving it from the file, you can use a command like "zfs send -R pool1@snap | zfs recv pool2@snap". Read the doc chapters that I mention for actual zfs send and recv options that may be important, as well as other things you need to do to make the other pool bootable.
2) When I tried to create a boot environment using beadm utility, I am able to create and activate BE in the san(SCSI) disk. But when I activated the new BE, status of new BE is changed to "R" and that of the current BE is still "NR" (which should be N, as per the behaviour of beadm). When I reboot the system it is again getting booted in the same old BE. I tried by setting the boot-device in OBP as the new san disk, which is giving error as "Does not appear to be an executable".I would have expected this to work better than that - but needing to set boot-device in the OBP doesn't surprise me. By any chance, was the pool on the SAN created using the whole disk (e.g. c3t0d0) instead of a slice (ct30d0s0)? Root pools need to be created on a slice.
Note that beadm only copies the boot environment. Datasets like <rootpool>/export (mounted at /export) and its descendants are not copied. Also, dump and swap are not created in the new pool. Thus, you may have built dependencies into the system that cross the original and new root pools. You may be better off using a variant of the procedure in the ZFS admin guide I mentioned above to be sure that everything is copied across. On the first boot you will likely have other cleanup tasks, such as:
- 'zpool export' the old pool so that you don't have multiple datasets (e.g. <oldpool>/export and <newpool>/export) both trying to mount datasets on the same mountpoint.
- Modify vfstab to point to the new swap device
- Use dumpadm to point to the new dump device
In solaris 10 i used lucreate for creating zfs BE, but lucreate command is not present solaris 11.I think that once you get past this initial hurdle, you will find that beadm is a great improvement. Note that beadm is not really intended to migrate the contents of one root pool to another - it has a more limited scope.
Can anybody help me creating a SAN boot environment either with ufs or zfs filse system?Is there any reason to not just install directly to the SAN device? You shouldn't really need to do the extra step of installing to a non-SAN disk first, thus avoiding the troubles you are seeing.
Good luck and please let us know how it goes.
Mike

Migrate Solaris 10 from Sun-Fire-V240 to T5140

Hi everyone.
Is it possible to migrate Solaris 10 running Oracle 10g RAC on a Sun-Fire-V240 to a T5140 without having to reinstall OS + Oracle-DB-software from scratch?
Because both servers are based on a SPARC-processor, I am guessing that it should be possible to patch/configure the OS to run on a T5140 instead of a V240.
Well, I have tried the following:
1) Booting the T5140 using "disk1" (c1t0d0).
2) Formatting "disk2" (c1t1d0) in the same number of slices I have on the V240.
3) newfs on every slice, mounting and copying from V240 to T5140 using "ufsdump/ufsrestore" over ssh.
4) Editing the /etc/vfstab.
5) installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t1d0s0
...Because I haven't got the correct platform for T5140 on the V240-install (even though it is patched recently), I used the one on the T5140.
6) Removed the /etc/path_to_inst and tried to "boot -ar" (after switching disk2 to "disk1-controller-position").
When 1-6 did not work, I tried a few other things:
a) Replace the /platform and /usr/platform with the ones on the T5140 (Generic_137111-06 sun4v sparc SUNW,T5140).
b) Replace the /kernel with the one from the T5140 (Generic_137111-06 sun4v sparc SUNW,T5140).
c) Replace the /etc/path_to_inst with the one from the T5140.
No luck so far.
So I am left with my initial question - is it possible to patch or configure the V240-Solaris10-installation, so it will run on a T5140?
Thanks,
Niels

In theory you can, but the question is if you want the issues. Migrating between architectures is only recommended for sparse zones, but not for any other. In this case it's you go from sun4u to sun4v which will give you enough of issues beside te changing hardware paths and configuration items.

Using ufsrestore i to restore files

Okay, I'm confused.
I have a tape created by ufsdump, and a request to restore a directory from it. I'm runing on a Sun e450 with Solaris 8. The tape was actually created on another Sun box in a different location.
Using "ufsrestore ivfs /dev/rmt/0 11" I can invoke ufsrestore, read the tape, and get to the section that contains the files I want to restore. I can cd to the requisite directory, and use ls to confirm the files exist. I can use "add *" to mark all files in that directory for restoration.
Unless I'm missing something obvious (likely!), I should be able to use "extract" to extract the requested files to the empty directory I am in when I invoke ufsrestore. When I do that, I get a message from ufsretore telling me I haven't read any volumes yet, and that I should mount a volume and specify the device. Er, I'm in the volume, looking at the files I want. Why am I being asked this?
No response I give to the questions seems to make a difference. Looking in the directory I'm in, I see ufsrestore has created the directory and sub-directory for the files I want. but has not extracted the files I need.
I've pored over the man page, and I'm still lost. How do I actually extract the files? And is there a ufsrestore command that will display what volumes are on the tape I'm using? I didn't see one mentioned.
I normally use tar or cpio for this stuff, and am not familiar with ufsdump/ufsrestore. Words of wisdom for a confused newbie to this package would be appreciated.
Thanks in advance!
Dennis

ufsrestore> what shows who/what made the current tape file
ufsrestore> add * takes all files from current tape file and puts them in directory you are currently in.
ufsrestore> extract does the restore after the add.
set owner mode for `.' ? [yn] n
ufsrestore> quit exit interactive mode

Consoles in solaris 9

I just installed Solaris 9 and can't use the ctrl-alt-f1, ctrl-alt-f2, etc as you can in Linux and BSDs. I installed Solaris 8 a while back and remembered using a purely text based console. Does Solaris 9 not support virtual consoles like a lot of other UNIXs do? I'm stuck in Gnome and am too used to using a console. Thanks.

There is a lot to be taken into consideration before desiding on your backup strategy, but if you're a little confused with different options (ufs snaps, jumpstart, good old ufsdump, etc.), the choice is still simple -- ufsdump/ufsrestore are the tools you would use to perform regular backups. UFS snapshots can not be considered a reliable backup, since it depends on the reliability of the filesystem -- you loose the filesystem, you loose the snapshot and therefore to be a true backup it still needs to be backed up to an external source. I would not call flash archives and jumpstart a real backup either, since the real purpose of either is to have easy deployable system images to maintain a large number of systems. I'm sure it is possible to concoct a backup system relying on flash archives or jumpstart, but it would be quite combersome compared to true backup solutions. If you're looking for a free backup solution on Solaris, a way to go would be either ufsdump/ufsrestore or possibly open-source Amanda backup suite if you have a more complicated setup with tape loaders.

Ufsrestore on Solaris 7

Similar Messages

Maybe you are looking for