• Keine Ergebnisse gefunden

Back Up Files

Im Dokument Software Installing Domain (Seite 42-45)

This procedure is broken down into seven major steps:

Step 2. Back Up Files

If you are installing Domain/OS on a new workstation or DSp, skip this sec-tion and proceed to Step 3.

Initializing a disk destroys all data on it. Therefore, before you initialize the disk you should back up any files and directories you want to save. Typically, you back up user directories and any site- or node-specific configuration and database files. You can then restore the archived objects to the node after you install Domain/OS.

You can back up objects to removable media (cartridge tape, magnetic tape, or floppy disk) using the wbak command. Or you can simply copy the objects to another node in the network using the Aegis cpt and cpr commands, or the UNIX cp command. Copying files to another node is faster, but the node's disk must have sufficient space. Also, if you copy files, be sure to preserve any desired attributes of the files - such as ACLs and date and time stamps- by using the appropriate command-line options.

Do not back up and restore any system directories like /sys or /com - you want to use the new versions of these that get installed with Domain/OS.

The following list identifies objects that are commonly backed up and pro-vides sample wbak command lines for doing so. The list is not comprehensive - the objects you back up on any given node ultimately depends on the node, the node's user, and the site. Also, the wbak command lines are suggestive only. For more information about wbak and its command-line options, see the Aegis, SysY, or BSD Command Reference or the online manual pages for wbak.

In all of the wbak command lines, the variable device is ctO for cartridge tape,

ro

for floppy disk, or mO for magnetic tape. Also, use the command-line op-tion -f 1 instead of -f end if the backup volume is blank. wbak resides in the /com and /usr/apollo/bin directories. You may have to be logged in as root, depending on the ACLs (Access Control Lists) of the objects to be backed up.

• Back up all user directories and files, using this command line:

wbak -dey device -I -nhi -f end -tid user_trees pathnamel ... pathnameN where

pathnamel ... pathnameN are the pathnames of user directories and files.

We recommend that you use full, not relative, path names and designate the node entry directory with a single slash, rather than with two slashes and the node name (/my_dir rather than //node_name/my_dir or my_dir, for exam-pIe). If you use two slashes, the restore (rbak) commands we provide later in this chapter won't work properly if the node is cataloged under a different name. If you use relative pathnames, the rbak commands we provide restore the objects to the current directory, which can complicate the process.

• If the node is an ns_helper database site, back up the ns_helper database

Instead of backing up the ns_helper files, you can reinitialize the files with edns after you install Domain/OS. Reinitializing the files is not that difficult because edns can reconstruct the databases with little intervention on your part.

If you choose to back up the ns_helper files, first stop ns_helper using the sigp (Aegis) or the kill (UNIX) command. Then back up the files, using this command line:

wbak -dey device -I -nhi -f end -tid ns_helper /sys/ns/helper_data/'ns_helper.?*'

/sys/node_data/system_logs/ns_helper.err_log

• If the node is the master registry site, back up the registry database and the /etc/passwd, /etc/group, and /etc/org files:

wbak -dey device -I -nhi -f end -tid registry /sys/registry /etc/passwd /etc/group /etc/org

Before you back up the registry, make sure you stop or put the registry serv-ers in maintenance mode using the rgy _admin tool. Otherwise, some files will be busy and will not be backed up properly.

Installing Domain/OS from Media

.. Also consider backing up the following types of files:

• User-modified startup files in the directories /sys/node_data and /sys/dm.

If other nodes use the node for booting diskless, there may be additional startup files in /sys/node_dataJlode_ID directories, where node_ID is the node ID of a node that boots diskless from the node. When you install Do-main/OS, you get a new set of startup files with appropriate defaults.

However, the information from the old startup files may help you get the node up and running the way you like it more quickly.

.. Printer configuration files in the directory /sys/print, if the node is at-tached to a printer.

.. Customized font files, if any, in the directory /sys/dm/fonts .

• Local extensions, if any, to the standard UNIX commands in the directo-ries /usr/local, /bin, or /com .

.. UNIX system configuration files, such as /etc/rc, /usr/lib/crontab, and uucp configuration files, if the node is a uucp administrative site. When you install Domain/OS, you get a new set of these files with appropriate defaults .

.. TCP/IP administrative files, if the node is running TCP/IP: /etc/hosts, /ete/

hosts.equiv, /etc/networks, /etc/gateways.

To back up these files, you can use the following wbak command line:

wbak -dey device -I -nhi -f end -fid file _id pathnamel ... pathnameN where

file _id is a character string of your choice that labels the physical file on the backup media in which the groups of objects are archived. You can use this label with rbak to easily restore the same group of objects.

pathnamel ... pathnameN are the pathnames of the files or directories you want to back up.

Step 3. Initialize the Disk and Boot From

Im Dokument Software Installing Domain (Seite 42-45)