|
|
| Managing the AMASS File System |
|
|
|
|
| Step | Command | Description |
|
|
|
|
| 5 | Create the following two directories and one file, all with | |
|
| owner as amass: |
|
|
| • /usr/filesydb |
|
|
| • /home/filesysdb/journal | |
|
| • /home/filesysdb/journal/dbv4jrnl (This file must be | |
|
| a minimum of 8 bytes in size.) | |
|
|
|
|
| 6 | amassrestore | Restore the AMASS File System |
|
| For example: | Database from the Backup |
|
| Volume. | |
|
| amassrestore | |
|
| Restores database with verbose | |
|
| /dev/rst12 | |
|
|
| messages |
|
|
| drive (/dev/rst12). The Backup |
|
|
| Volume’s barcode is 12N6J. |
|
|
|
|
| 7 | Transition the system to | |
|
| system. |
|
|
|
|
|
To recover data on a Backup Volume containing a backup from an earlier version of AMASS, make sure the current MAXIOSIZE parameter on AMASS is configured to the same value as when the Backup Volume was made.
For example, your current Backup Volume was made when the MAXIOSZ value on AMASS was 256 KB. (This value should be physically noted on the volume.)
Upgrade AMASS and change the MAXIOSZ value to 1024 KB.
Before attempting to read the Backup Volume, return the MAXIOSZ parameter on AMASS to 256 KB.
Operational Tasks |