Back up databases
Back up both read-only and writable databases.
Pay special attention to the type and the data that is residing in the SQL server. This information will be useful in the event you need to restore one or more databases.
Back up read-only databases
Read-only databases are databases supplied by Verisk which cannot be updated by the client. A one-time backup is required of these databases, and the backup should be readily available in case a database needs to be restored. Examples of read-only databases include:
| AIRAddressServer | AIRLossCost |
| AIRDBAdmin | AIRMap |
| AIRDQIndustry | AIRMapBoundary |
| AIREventInfo | AIRPropertyExposure *if licensed |
| AIREvx | AIRReference |
| AIRGeography | AIRSpatial |
| AIRIndustry |
Back up writable databases
Databases that are not Verisk-supplied read-only databases contain client data and should be backed up regularly. Examples of working databases include:
| AIRCompanyLoss | AIRPropertyExposureHelper *if licensed |
| AIRDowngradeHelper | AIRReinsurance |
| AIREvents | AIRResult |
| AIREvents_50k |
AIRResultRe |
|
AIREvents_HIST |
AIRSecurity |
|
AIRExposure |
AIRSpatialWork *if licensed |
|
AIRExposureRe |
AIRUserMap *if licensed |
| AIRExposureSummary | AIRUserSetting |
| AIRGlobalSetting | AIRUserSpatial*if licensed |
| AIRMapBoundary | AIRUserSpatialWork *if licensed |
| AIRProject | AIRWork |
Verisk recommends:
-
Results databases be in a simple recovery state at all times.
-
Avoid running periodical transactional or differential backups on a Results database.
-
Perform a full back up of Results databases at the end of the analysis to save the results for the future.