You can send a backup database over the network to any host running a solidDB® server. A server playing the role of the backup receiver is called a NetBackup Server. By default, any solidDB® server instance can acts as the NetBackup Server.
By default, the netbackup operation copies the database to one flat file in the NetBackupDirectory, even if the logical database consists of multiple files. Instead of flattening the structure to one file, you can define multiple files to which the source database files are mapped to during the netbackup operation. You map the source and target files in a backup.ini file that must be stored on the target server in the directory defined with the General.NetBackupDirectory parameter.
Making netbackup
Start a network backup (netbackup) with the following command:
The call returns either when the netbackup is completed or if there is an error.
-I
Executes a full database integrity check.
-i
Executes a database index integrity check.
▪DELETE_LOGS | KEEP_LOGS defines whether backup logs are deleted or kept in the source server. Default is DELETE_LOGS.
DELETE_LOGS is referred to as Full backup
KEEP_LOGS is referred to as Copy backup. Using KEEP_LOGS corresponds to setting the General.NetbackupDeleteLog parameter to “no”.
▪connectconnect strspecifies the connection to the NetBackup Server. If connect str is omitted, it must be specified in the solid.ini configuration file. For the full connect string syntax, see Configuring solidDB®.
▪dirbackup dirdefines the backup directory in the NetBackup Server. The path can be either absolute or relative to the netbackup root directory.
If two databases are copied to the same directory, the earlier database copy is overwritten by the latter. The backup dirdirectory cannot point, for instance, to the root directory of the Netbackup Server.
Notes
▪The command ADMIN COMMAND 'netbackup' is not supported within the Srv.At configuration parameter.
▪The command ADMIN COMMAND 'status netbackup' is synonymous to ADMIN COMMAND 'status backup'; it reports on both local and network backups.
▪The command ADMIN COMMAND 'netbackuplist' is synonymous to ADMIN COMMAND 'backuplist'; it reports on both local and network backups.
Flat and deep NetBackup directory structures
The NetBackup Server sees all the database files sent to it as one logical database even though the source database can consist of multiple files stored in different directories and on different permanent storage devices. By default, netbackup copies all the files of the source database to a single directory, that is, the user‑specified netbackup directory.
It is, however, possible to explicitly specify the directories, names, and sizes of the backup files stored into the file system of the NetBackup Server. The directories, names, and file sizes are specified in a backup.ini netbackup configuration file in the netbackup directory. The backup.ini file follows the syntax of [IndexFile] section in solid.ini configuration file. Therefore, in addition to the section name, the backup.ini file can include multiple specifications for file names and sizes. Formally the syntax is as follows:
[IndexFile] FileSpec_[1...N]=[path/]file name [maximum file size]
A NetBackup Server with a backup.ini file receives the incoming database as a whole, splits it into N separate parts, and stores the parts as files as specified in the backup.ini file.
To retain the directory structure of the source server, copy and rename the source server’s solid.ini to backup.ini and move it to the backup directory at the NetBackup Server. The NetBackup Server reads only the IndexFile.FileSpec_[1...N] specifications, creates similar directory structure, and stores backup files with their original properties to the NetBackup Server.