You can restore the database to the state it was in when the backup was created. Furthermore, you can revive a backup database to the current state by using log files generated after the backup was made. Those log files include information about the data inserted or updated since the latest backup.
Preparing netbackup files for recovery
You might need to take the following two preliminary steps before a database can be recovered from remote backup files.
1 If the backup.ini file was not used, the original naming and sizing of the database files must be restored from the solid.db file.
2 All the backup files must be copied to the server where the restore takes place.
Besides these steps, restoring a netbackup is similar to restoring local backup.
Returning to the state of the last backup
1 Shut down solidDB, if it is running.
2 Delete all log files from the log file directory. The default log file names are sol00001.log, sol00002.log, and so on.
3 Copy the database files from the backup directory to the database file directory.
4 Start solidDB. Recovery is not performed because no log files exist.
Refreshing database from the backup to the current state
1 Shut down solidDB, if it is running.
2 Copy the database files from the backup directory to the database directory.
3 Copy the log files from the backup directory to the log directory. If the same log files exist in both directories, do not overwrite the newer log files with the older backup log files.
4 Start solidDB. solidDB uses the log files automatically to perform a roll-forward recovery.
Recovering from an abnormal shutdown
If the server was closed abnormally, that is, if it was not shut down using the procedures described earlier, solidDB automatically uses the log files to perform a roll-forward recovery during the next startup. No administrative procedures are required to start the recovery.