The raw encryption functions are provided to solve this problem. Backup applications are a primary intended user for these functions. Therefore, the caller of the raw encryption functions does not need access to the cryptographic keys that decrypt the file. The following raw encryption APIs are available for use with backup and restore applications:. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
View all results across Veeam. Back to document search. I want to report a typo. Submit report. To add a database to the list choose option 1. This example also uses option 3 to show that the database is added to the current list. To remove a database to the list choose option 2. This example also uses option 3 to show that the database is removed from the current list. To display a list of all databases in this instance choose option 4 :. To display information about the last full backup choose option 5 :.
If no backup is running when you choose this option, you receive the following message:. You can start the monitor in a separate Terminal window before starting the backup or restore job. A restore job cannot be monitored if switch 10 was set when starting the restore.
In most cases, answer Yes. Asks for the name of the file that holds the backup you wish to restore. If your backup is on more than one volume, that information is in the volume header. After restoring the first volume, the utility prompts you for the next. Displays the header of the volume. The header contains the following information determined during the backup: the date of the backup on this volume, the date of the previous backup, and the date of the last full backup.
Allows you to specify another input device that contains the next backup to restore. When you select one of these restore options, the utility asks you to enter the name of the device holding the first backup to restore. The default the first time you enter a restore option is the device to which the last full backup was sent, if there was one. When you are restoring an incremental or cumulative backup, the target database must be in exactly the same state as when you restored it from the last full backup.
You must prevent all updates to the restored databases until you restore all subsequent incremental backups. Failure to heed this warning can result in the incremental or cumulative restore producing a degraded database.
Restoring Databases Using the Backup History. Mirrored Database Considerations. You can also perform these functions non-interactively in a script. If you are restoring mirrored databases, review Mirrored Database Considerations in this section before you perform this procedure. The following procedure is an outline of an example that restores all directories. It shows the beginning prompts of the restore process. As it continues, the utility asks you very specific questions while stepping through the restore process.
Select to restore all directories from the utility menu. This option restores all directories that are on the backup medium. Next you are asked to enter the top path you want all the databases to be restored to.
The system prefixed it to the original path of the database to be restored. So all the databases are restored under this directory with their original directory as a subdirectory to this directory. Press Enter to ignore it and restore the databases to their original path. InterSystems recommends suspending processes. Specify the first file from which to restore.
You can press Enter to accept the default file, which is the last full backup. Check that the description of the backup is correct and verify that this is the file you want to restore.
The utility tells you which directories it will restore, and the restore proceeds. Specify the input file for the next incremental backup to restore, or enter stop if there are no more input files to restore.
Indicate whether you want to restore other backups. When you answer Yes , the procedure repeats. When you respond No , the system mounts the databases you have restored. Specify which journal entries you want to apply to the restored databases and the name of the journal file you are restoring. Normally, you select option 1 and apply only those changes that affect the directories you have just restored. Restore from the journal files begins after confirming several pieces of information:.
This option lets you select which directories to restore from the backup medium. It also allows you to restore a database to a different directory name or to a different device. As the utility prompts you with directory names, specify which databases you want to restore, and in which directories you want to restore them:.
Answer Yes if you want to edit your choices, or press Enter to confirm them. The process then continues the same as the procedure for restoring all directories, as specified in the previous section. You can use this procedure to restore a backup performed on different system from the one on which you are restoring it. The restore utility prompts you for the backups to restore according to their type and order in the backup history.
After restoring the last full backup, the utility uses the information in the backup history to suggest the next logical backup for you to restore and continues through the history. It prompts you to restore subsequent backups in the following order:. All incremental backups since the last cumulative backup or if none exists, since the last full backup. It does so in order from the first to the most recent. You can override the suggested backups in the restore process.
Remember, however, that an incremental or cumulative backup does not represent a complete copy of the databases. You can restore an incremental backup only after restoring a full backup. On InterSystems IRIS platforms that support access to a database from cluster, you should always back up a given database directory from the same node so that its complete backup history is available if you need to restore the directory.
If you are restoring mirrored databases, review Mirrored Database Considerations in this section before you perform an unattended restore. You can write a script to implement unattended restores by calling one of these two entry points:. If the target directory exists but the IRIS. DAT file. Both entry points are functions, which return the status of the call. All arguments are input only. The following table describes the input arguments used for both functions except where indicated.
For example, assuming you have created a text file RestoreList. The last record could also be completely omitted if you do not want to restore the journal for that directory. When a mirrored database is the target of an InterSystems IRIS backup restore, the source database must match the target that is, it must be the same mirrored database.
Mirrored database backups created on a failover mirror member can be restored to any member of that mirror that is, another failover member or an async member. If you are restoring from a backup created on an async mirror member, see Restoring from Async Mirror Members in this section.
It does not include databases that were once mirrored, or that were included in a mirror to which the host system no longer belongs. InterSystems IRIS backup restore in a mirror behaves differently depending on whether it is being restored on the mirror member where the backup was created or on a different system:.
The database is restored as a mirrored database, however since it was backed up as one , and the functionality described in the following sections applies, including automatic restore of the journal files required to activate the database in the mirror. Backup Failover Member — On the backup failover member, restoring a mirrored database that is active, or newer than the copy in the backup, results in a warning message:.
For a selective restore, you are given a chance to overwrite the target if that is what you really want to do. A full backup restore on the system that created the backup works as it does for nonmirrored systems, except that local mirrored databases that are newer than the copies in the backup — which, by definition, includes databases that are currently active — are skipped; all databases are restored to their original locations. A full backup restore on a mirror member other than the system that created the backup restores only mirrored databases that already exist on the system.
However, mirrored databases on the target system that are newer than those in the backup are skipped. A full backup restore that specifies a new top-level directory restores all the databases in the backup after generating the new path for the databases.
If the user ends up with two copies of any of the mirrored databases after the restore, they are warned that the copy being restored cannot be activated because it is already active on the system. Link the mirrored databases into the active mirror if the mirror exists and a copy of the database does not already exist. The following differences apply to selective backup restores of mirrored databases:. When a backup is being restored, you are asked whether to limit the restore to only mirrored databases; depending on your response:.
During the database selection phase of a selective restore, you are presented with a list of the databases in the backup and asked to specify a path where each should be restored. When restoring a backup on a mirror member other than the system that created the backup, the result of pressing Enter for a mirrored database directory varies depending on whether an active mirrored database with the same mirror database name exists on that system.
If the database does not exist, the database is restored to the directory path it has on the source machine. If that path does not exist, you must confirm the creation of the needed directories. If a database already exists at that location, no action is taken. If a selective backup restore detects that the restore is going to overwrite a mirrored databases in the following situations, you are warned that continuing will destroy the target database and asked if you want to continue:.
The database from the backup is not a copy of the current database for example, it could be a nonmirrored database or a database of the same mirror database name from a different mirror.
If you continue, the target database is removed from the mirror and overwritten as requested. For a mirrored database, if the target is left blank it means restore to the corresponding mirror database on the local machine.
If the target is not blank, then the database must be one of the following:. If the target is a mirror database name or blank and that mirrored database does not exist on the local system or is dismounted , the target is created only if the backup is being restored on the system that created it.
If the backup is being restored on another mirror member the database is skipped. As with full backup restores, following a selective backup restore, the system attempts to:. The following considerations apply when restoring from mirrored databases created on async mirror members:.
Mirrored databases backups created on a async mirror member can be restored to any async member of the same mirror. Mirrored databases backups created on a async mirror member can only be used to create new copies of the mirrored database that is, they cannot be restored over an existing mirrored database on a failover member.
Release Information. Release Notes. Supported Platforms. InterSystems Kubernetes Operator. Using the InterSystems Kubernetes Operator. Installation Kit. Installation Basics Installation Guide. Automating Configuration Configuration Parameters. Data Migration. System Administration. Monitoring Guide. Error Reference. Specialized System Tools and Utilities. Mirroring and High Availability. First Looks. Scalability Guide. Resiliency and Data Integrity.
First Look Data Integrity Guide. Security Tutorial. Check Recap. Securing Applications. Security for Developers. SOAP Security. Authentication and Authorization. Authentication Guide. Authorization Guide. LDAP Guide. OAuth 2. Overview of OAuth 2. Database Encryption Public Key Infrastructure. Encryption Guide. TLS Guide. Embedded Language Development. Data Model Orientation Guide. Using Terminal. Using ObjectScript. Class Definitions. Class Definition Reference.
ObjectScript Reference. ObjectScript Tutorial. The Basics. The Good Stuff. Using Globals. First Look. Using SQL. Optimizing SQL. Document Database. XML Tools. XML Projections. Web Services. Web Gateway Configuration Guide. Using JSON. Internet Utilities. Advanced Concepts. Unit Testing Overview. What is a Unit Test? Why Unit Test? API Index. Tools Index. Complete Glossary of Terms. External Language Development. Using Java with InterSystems Software.
Native API for. NET Managed Provider. Using the Native SDK for. NET Quick Reference. Interoperability Productions. First Look Introducing Interoperability Productions. Preparing to Create Productions. Best Practices. Developing Productions. Developing Productions Using ObjectScript. Developing Productions Using Java and.
Developing DTL Transformations. Using a Production as an ESB. Configuring, Managing, and Monitoring Productions. Configuring Productions. Managing Productions. Monitoring Productions. Push Notifications. Defining Workflows. Testing Productions.
Testing Productions Tutorial Testing Productions. Connecting Systems. Supported Formats Email Adapters. File Adapters. FTP Adapters. HTTP Adapters. MQTT Adapters. SAP Java Connector. SQL Adapters. TCP Adapters. Managed File Transfer. Using Virtual Documents in Productions. Developing Business Rules. Analytics and Data Science. BI Introduction. BI Modeling.
BI Advanced Modeling. Using Dashboards and the User Portal. BI Dashboards. BI Analyzer. Using MDX. MDX Reference. BI Clients. Introduction DeepSee. BI Tutorial. Apache Spark. Using the InterSystems Spark Connector. Machine Learning. Using IntegratedML. Text Analytics Natural Language Processing.
SQL Search. Unstructured Information Management Architecture. InterSystems Reports. Class Reference. Thanks for your feedback! Need to tell us more? Click here or use the Feedback button. Is this page helpful? Allows zero downtime backups for most systems. With old-format databases, there is minimal user interruption.
Backs up only databases; it does not back up external files, requiring a separate simultaneous system backup. Provides a backup strategy with little or no interruption for sites that are not able to use one of the other recommended approaches.
0コメント