Hello,
This is an interesting way of going about a bare metal recovery. I have
several suggestions that may help you.
1. After everything is restored and you kernel is reinstalled,
do:
sync; sync; sync
which will cause the kernel disk cache to be flushed.
2. Before rebooting, umount all disks or if they cannot be unmounted,
remount them read-only.
Hopefully those two items will ensure that all changed information is written
to the disk before rebooting. Concerning the _door files, I have no idea
what they are. Hopefully a Solaris expert can answer the question.
Regards,
Kern
On Friday 15 December 2006 15:57, Mair Wolfgang-awm013 wrote:
> Hello,
>
> I've encountered some problems with my bare metal recovery on solaris 9
> with bacula 1.38.11.
>
> Here is a brief description of the recovery procedure I did (this might
> also be a good description of how to do a bare metal recovery, if this
> issue gets solved):
>
> Boot the client from network in singleuser mode.
> Mount a shared directory containing bacula to the client.
> # mount 192.168.230.10:/export/local /usr/local
>
> Partition the target hard drive.
> # format
>
> Created a new file system on the target partition.
> # newfs /dev/dsk/c0t0d0s0
>
> Mount the new target partition to /a
> # mount /dev/dsk/c0t0d0s0 /a
>
> Create the necessary entries for the director and the storage server
> into the hosts file
> # echo "192.168.230.35 volvo" >> /etc/hosts
> # echo "192.168.230.30 prinz" >> /etc/hosts
> # echo "192.168.230.10 automatix3" >> /etc/hosts
>
> Set the LD_LIBRARY_PATH var to where the bacula libs are:
> # LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/local/lib
> # export LD_LIBRARY_PATH
>
> Start the bacula file daemon
> # /usr/local/etc/bacula start
> Starting the Bacula File daemon
> #
>
> Now go to the bconsole and start the restore procedure and select all
> files to restore:
> *restore
>
> First you select one or more JobIds that contain files to be restored.
> You will be presented several methods of specifying the JobIds. Then you
> will be allowed to select which files from those JobIds are to be
> restored.
>
> To select the JobIds, you have the following choices:
> 1: List last 20 Jobs run
> 2: List Jobs where a given File is saved
> 3: Enter list of comma separated JobIds to select
> 4: Enter SQL list command
> 5: Select the most recent backup for a client
> 6: Select backup for a client before a specified time
> 7: Enter a list of files to restore
> 8: Enter a list of files to restore before a specified time
> 9: Find the JobIds of the most recent backup for a client
> 10: Find the JobIds for a backup for a client before a specified
> time
> 11: Enter a list of directories to restore for found JobIds
> 12: Cancel
> Select item: (1-12): 5
> Defined Clients:
> 1: passat-fd
> ............
> 47: mondeo-fd
> Select the Client (1-47): 47
> Automatically selected FileSet: FullSolaris
> +-------+-------+----------+---------------+---------------------+------
> +-------+-------+----------+---------------+---------------------+------
> +-------+-------+----------+---------------+---------------------+--
> ------+-----------+
> | JobId | Level | JobFiles | JobBytes | StartTime |
> VolumeName
> | StartFile |
> +-------+-------+----------+---------------+---------------------+------
> +-------+-------+----------+---------------+---------------------+------
> +-------+-------+----------+---------------+---------------------+--
> ------+-----------+
> | 547 | F | 86,228 | 1,965,081,652 | 2006-12-15 13:22:45 |
> full-15-12-2006.90 | 0 |
> +-------+-------+----------+---------------+---------------------+------
> +-------+-------+----------+---------------+---------------------+------
> +-------+-------+----------+---------------+---------------------+--
> ------+-----------+
> You have selected the following JobId: 547
>
> Building directory tree for JobId 547 ...
> ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 Job, 83,160 files inserted into the tree.
>
> You are now entering file selection mode where you add (mark) and remove
> (unmark) files to be restored. No files are initially added, unless you
> used the "all" keyword on the command line.
> Enter "done" to leave this mode.
>
> cwd is: /
> $ mark *
> 86,227 files marked.
> $ done
> Bootstrap records written to /var/bacula/working/volvo-dir.8.restore.bsr
>
> The job will require the following Volumes:
>
> full-15-12-2006.90
>
>
> 86227 files selected to be restored.
>
> Run Restore job
> JobName: RestoreFiles
> Bootstrap: /var/bacula/working/volvo-dir.8.restore.bsr
> Where: /
> Replace: always
> FileSet: FullSolaris
> Client: mondeo-fd
> Storage: File
> When: 2006-12-15 15:26:35
> Catalog: MyCatalog
> Priority: 10
> OK to run? (yes/mod/no): m
> Parameters to modify:
> 1: Level
> 2: Storage
> 3: Job
> 4: FileSet
> 5: Client
> 6: When
> 7: Priority
> 8: Bootstrap
> 9: Where
> 10: Replace
> 11: JobId
> Select parameter to modify (1-11): 9
> Please enter path prefix for restore (/ for none): /a
> Run Restore job
> JobName: RestoreFiles
> Bootstrap: /var/bacula/working/volvo-dir.8.restore.bsr
> Where: /a
> Replace: always
> FileSet: FullSolaris
> Client: mondeo-fd
> Storage: File
> When: 2006-12-15 15:26:35
> Catalog: MyCatalog
> Priority: 10
> OK to run? (yes/mod/no): y
> Job started. JobId=554
> *
> *
>
> Then go back to the client and:
> # installboot /a/usr/platform/`uname -i`/lib/fs/ufs/bootblk
> /dev/rdsk/c0t0d0s0
>
>
> Until here everything looks fine. But when I try to boot from the newly
> created disk I see the following inode messages:
>
>
> Rebooting with command: boot
> Boot device: disk:a File and args:
> SunOS Release 5.9 Version Generic_118558-11 64-bit Copyright 1983-2003
> Sun Microsystems, Inc. All rights reserved.
> Use is subject to license terms.
> configuring IPv4 interfaces: eri0.
> Hostname: mondeo
> NOTICE: /: unexpected free inode 140873, run fsck(1M) -o f
> NOTICE: /: unexpected free inode 140873, run fsck(1M) -o f
> NOTICE: /: unexpected free inode 140876, run fsck(1M) -o f
> NOTICE: /: unexpected free inode 140876, run fsck(1M) -o f
> NOTICE: /: unexpected free inode 140877, run fsck(1M) -o f
> mount: /var/run is already mounted, swap is busy,
> or the allowable number of mount points has been exceeded The
> system is coming up. Please wait.
> NOTICE: /: unexpected free inode 140878, run fsck(1M) -o f
> NOTICE: /: unexpected free inode 140878, run fsck(1M) -o f checking ufs
> filesystems
> /dev/rdsk/c0t0d0s7: is clean.
> LDAP domain name is ea.mot.com
> starting rpc services: rpcbind keyserv done.
> Setting netmask of eri0 to 255.255.255.0 Setting default IPv4 interface
> for multicast: add net 224.0/4: gateway mondeo syslog service starting.
> Starting the Bacula File daemon
> The system is ready.
>
> mondeo console login:
>
>
> When I do a fsck I get the following messages. The first one in Phase 1
> doesn't seem very harmfull to me. But the second one with the missing
> door files which get removed doesn't make me feel very confident
> although the system boots up without error messages after the fsck is
> finished.
>
>
> # fsck /dev/dsk/c0t0d0s0
> ** /dev/rdsk/c0t0d0s0
> ** Currently Mounted on /
> ** Phase 1 - Check Blocks and Sizes
> PARTIALLY ALLOCATED INODE I=137137
> CLEAR? y
>
> PARTIALLY ALLOCATED INODE I=138752
> CLEAR? y
>
> PARTIALLY ALLOCATED INODE I=138753
> CLEAR? y
>
> PARTIALLY ALLOCATED INODE I=138755
> CLEAR? y
>
> PARTIALLY ALLOCATED INODE I=138756
> CLEAR? y
>
> PARTIALLY ALLOCATED INODE I=138757
> CLEAR? y
>
> ** Phase 2 - Check Pathnames
> UNALLOCATED I=138755 OWNER=root MODE=0 SIZE=0 MTIME=Jan 1 01:00 1970
> NAME=/etc/sysevent/syseventconfd_event_channel/reg_door
>
> REMOVE? y
>
> UNALLOCATED I=137137 OWNER=root MODE=0 SIZE=0 MTIME=Jan 1 01:00 1970
> NAME=/dev/.devfsadm_synch_door
>
> REMOVE? y
>
> UNALLOCATED I=138756 OWNER=root MODE=0 SIZE=0 MTIME=Jan 1 01:00 1970
> NAME=/etc/sysevent/sysevent_door
>
> REMOVE? y
>
> UNALLOCATED I=138757 OWNER=root MODE=0 SIZE=0 MTIME=Jan 1 01:00 1970
> NAME=/etc/sysevent/piclevent_door
>
> REMOVE? y
>
> UNALLOCATED I=138752 OWNER=root MODE=0 SIZE=0 MTIME=Jan 1 01:00 1970
> NAME=/etc/sysevent/devfsadm_event_channel/reg_door
>
> REMOVE? y
>
> UNALLOCATED I=138753 OWNER=root MODE=0 SIZE=0 MTIME=Jan 1 01:00 1970
> NAME=/etc/sysevent/devfsadm_event_channel/1
>
> REMOVE? y
>
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> FREE BLK COUNT(S) WRONG IN SUPERBLK
> SALVAGE? y
>
> 83047 files, 1997574 used, 3038648 free (95392 frags, 367907 blocks,
> 1.9%
> fragmentation)
>
> ***** FILE SYSTEM WAS MODIFIED *****
> #
>
>
> So question is why are these doors not created correctly by the restore?
> And will these doors get created automatically by the system if they
> don't exist?
> What are these partially allocated inodes?
> I've tried it several times and it shows the same behaviour each time.
>
> Regards
> Wolfgang
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
