The VME supports Advanced Pick and most R83 compatible tape formats with some restrictions on the devices (see VME Tapes).
An easy way to load a D3 database is to use a pseudo tape created for example, on a D3 UNIX implementation, and share this file across the network using a PC-NFS package.
Restore data in the new file system, using this syntax:
|
account-restore fsi:name {(o} from: name on tape |
-or-
|
account-restore name {(o} from: name on tape |
where
|
name |
Name of the destination account in the new D3 File System. Note that name on tape is required if it is different from the name of the new account. |
The (o option must be used to overload the account if it exists. Note this overloading is not the same as overwriting the account. If an item exists both in an existing file and on tape, it is overwritten by the item on tape. If an item exists in an existing file but not on tape, it is left in the file.
By default, the files coming from the tape are restored on the server where the account was created. To force the restore to load important files on specific servers, first create the files on the servers using the D3 File Manager (see Creating a Table).
If a restored file does not exist, it is created with a modulo equal to the original modulo and a frame size equal to 4 KB. To resize the file, either set the resize attribute before saving, or pre-create the account and file using the D3 File Manager to the desired modulo.
|
NOTE |
A full restore, using the /restore option in D3Vme.exe, also restores data to the FSI space. The /fileload option deletes the FSI space and recreates a blank file system before the full restore. |
See Also