- 论坛徽章:
- 0
|
TRU64 恢复自启动光盘
我用btcreate做备份只做过几次,在4.0F上做过,并成功恢复.
今晚在5.1A上也做了,但还未做恢复.我的系统只装了OS.
现把过程给出,作参考.
#df
Filesystem 512-blocks Used Available Capacity Mounted on
root_domain#root 677376 177750 431888 30% /
/proc 0 0 0 100% /proc
usr_domain#usr 6514192 1149542 4713230 20% /usr
usr_domain#var 385072 19022 327542 6% /var
#
#
#
# /usr/sys/bin/btcreate
BOOTABLE TAPE CREATION
The btcreate utility creates a bootable Standalone System (SAS)
kernel on tape. The SAS kernel has a built-in memory file
system (mfs), which contains the commands, files, and directories
needed to restore the system image.
The btcreate utility prompts you for information. Default answers,
if applicable, are enclosed in square brackets ([]). To select
a default answer, press the Return Key at the prompt. Type q at
any prompt to exit the utility; any information you supplied up to
that point is ignored.
The btcreate utility prompts you for the following:
- name of the a kernel configuration file
- disk partition to contain the SAS kernel
- tape device to use for back up operations
- list of file systems to back up
- list of files and directories to back up
Do you want to continue (y/n) [y]:
SELECTING A KERNEL CONFIGURATION FILE
The kernel configuration file, located in the /usr/sys/conf directory,
defines the run-time behavior of the kernel. The btcreate utility
uses this file to build the SAS kernel. You must specify which kernel
configuration file to use.
Enter the name of the kernel configuration file [GEN]:
SELECTING MFS FILE SYSTEM OPTION
You can build the miniroot file system on a memory file system(mfs)
to save space on disk. A mfs file system is a UFS file system in
virtual memory.
Answer yes if you want to create the miniroot file system in memory.
Answer no if you want to create the miniroot file system on disk.
Do you want to use a MFS file system? (y/n) [y]:
SELECTING LOCATION FOR TEMPORARY FILES
The btcreate utility requires 70120 (512 blocks) of disk in the
/usr filesystem for the temporary files that are created during
the process of bootable tape creation.
If you have space constraints in the /usr file system then you
can use disk space in filesystems other than the one /usr/sys is
located on.
When this flag is used all necessary temporary space needed by
btcreate will be used in the specified directory.
Answer yes if you want btcreate to use the space available in /usr/sys.
Answer no if you want btcreate to use some other area for temp files.
Do you want temporary files to be created in /usr/sys ? (y/n) [y]:
SELECTING A TAPE DEVICE
The SAS kernel and file systems are backed up to a no rewind tape
device. You must specify which tape device is to contain the kernel
and file systems.
Enter the name of the tape device [tape0_d1]: tape1_d1
Verifying tape... Done.
SELECTING FILE SYSTEMS
You must specify which file systems you want to include on the tape
device. Each entry consists of the device name, mount point, and
file system type separated by a space or tab as follows.
device_name mount_point fs_type
To help with your selections, information about your local file
systems follows.
root_domain#root / advfs
usr_domain#usr /usr advfs
usr_domain#var /var advfs
Press the Return Key after each entry or at the prompt to end input.
Enter your selection: root_domain#root / advfs
root_domain#root / advfs selected for back up.
Enter your selection: usr_domain#usr /usr advfs
usr_domain#usr /usr advfs selected for back up.
Enter your selection: usr_domain$ #var /var advfs
usr_domain#var /var advfs selected for back up.
Enter your selection:
Have you completed your selections (y/n) [y]:
CUSTOMIZING THE MINIROOT FILE SYSTEM
You have the option of adding files and directories to the miniroot
file system. Each entry consists of two fields separated by a space
or tab as follows.
file destination
The first field specifies the absolute pathname of the file or directory
on the currently running system. The second column specifies absolute
pathname on the miniroot file system.
Press the Return Key after each entry or at the prompt to end input.
Enter your selection:
You did not select a file or directory to back up.
Is this correct (y/n) [y]:
No files will be added to the miniroot file system.
VERIFYING USER INPUT
This section summarizes your selections. You have the option
of accepting or modifying any selection. If you want to exit
the utility discarding all information gathered, type a q at
the prompt.
Kernel Configuration File specified : /usr/sys/conf/GEN
Disk Partition : mfs
Tape Drive : tape1_d1
File systems included : yes
Miniroot customizations : no
The following file systems were specified for back up:
Device_Name Mount_Point File_Type Size
root_domain#root / advfs 176792
usr_domain#usr /usr advfs 1152472
usr_domain#var /var advfs 23104
Are the answers correct? (y/n) [y]:
Proceeding to create Bootable tape...
Creating a new kernel...
Moving the new kernel to /usr/sys/bin/vmunix.
smoothsync_age: reconfigured
Creating device files on mfs...
procprod: using MfsBase 0x14003c000
procprod: pid 2271, MfsBase 14003c000, 43008 sectors, output ==>; "/var/tmp/procprod/mfsImage"
procprod: wrote 22020096 bytes
Getting copy of kernel...
Merging file system into kernel...
Merging sboot into kernel...
pmerge sboot into kernel...
performing dd...
1+0 records in
1+0 records out
performing cat...
deleting /usr/sys/bin/vmunix.boot.2251...
Moving /usr/sys/bin/vmunix.tmp.2251 to /usr/sys/bin/vmunix.boot.2251...
Making tape bootable kernel...
Writing vmunix...
57714+0 records in
57714+0 records out
smoothsync_age: reconfigured
Dumping the file system root_domain#root of type advfs
path : /
dev/fset : root_domain#root
type : advfs
advfs id : 0x3f2bb23b.000a9150.1
vdump: Date of last level 0 dump: the start of the epoch
vdump: Dumping directories
vdump: Dumping 91624455 bytes, 120 directories, 1972 files
vdump: Dumping regular files
vdump: Status at Sat Aug 2 23:07:18 2003
vdump: Dumped 91754659 of 91624455 bytes; 100.1% completed
vdump: Dumped 120 of 120 directories; 100.0% completed
vdump: Dumped 1972 of 1972 files; 100.0% completed
vdump: Dump completed at Sat Aug 2 23:07:18 2003
Dump finished.
Dumping the file system usr_domain#usr of type advfs
path : /usr
dev/fset : usr_domain#usr
type : advfs
advfs id : 0x3f2bb24d.00002620.1
vdump: Date of last level 0 dump: the start of the epoch
vdump: Dumping directories
vdump: Dumping 592985313 bytes, 1069 directories, 28690 files
vdump: Dumping regular files
vdump: Status at Sat Aug 2 23:13:17 2003
vdump: Dumped 224058721 of 592985313 bytes; 37.8% completed
vdump: Dumped 44 of 1069 directories; 4.1% completed
vdump: Dumped 2287 of 28690 files; 8.0% completed
vdump: Status at Sat Aug 2 23:18:17 2003
vdump: Dumped 401394306 of 592985313 bytes; 67.7% completed
vdump: Dumped 524 of 1069 directories; 49.0% completed
vdump: Dumped 13480 of 28690 files; 47.0% completed
vdump: Status at Sat Aug 2 23:23:16 2003
vdump: Dumped 595150344 of 592985313 bytes; 100.4% completed
vdump: Dumped 1069 of 1069 directories; 100.0% completed
vdump: Dumped 28690 of 28690 files; 100.0% completed
vdump: Dump completed at Sat Aug 2 23:23:16 2003
Dump finished.
Dumping the file system usr_domain#var of type advfs
path : /var
dev/fset : usr_domain#var
type : advfs
advfs id : 0x3f2bb24d.00002620.2
vdump: Date of last level 0 dump: the start of the epoch
vdump: Dumping directories
vdump: Dumping 9154824 bytes, 266 directories, 961 files
vdump: Dumping regular files
vdump: Status at Sat Aug 2 23:24:05 2003
vdump: Dumped 9159640 of 9154824 bytes; 100.1% completed
vdump: Dumped 266 of 266 directories; 100.0% completed
vdump: Dumped 964 of 961 files; 100.3% completed
vdump: Dump completed at Sat Aug 2 23:24:05 2003
Dump finished.
Rewinding the tape.
btcreate.log file has been created on /var/adm directory.
End of system image creation on tape.
# |
|
免费注册
发表于 2003-01-23 22:31