The above example restores the “Banners” Safe from the backup computer to the Vault. Parestore C:\PrivateArk\Server\Vault.ini Backup/asdf1 /restoresafe banners /targetsafe banners_r This means that if another Safe is restored from the same backup, there is no need to upload or load the metadata files again, and running PARestore /DataOnly is enough The Safes are restored to the Vault from the Restored Safes folder in the Replicator computer.ĭisplays the list of options available with this utility.Īfter PARestore restores a single Safe, the entire metadata is loaded. Note: This parameter and ‘LoadOnly’ are mutually exclusive and cannot be used together. After the upload process has finished, run ‘CAVaultManager RestoreDB’ to complete the restore process. Restores a complete Vault by uploading all the metadata and data files to the Vault’s Restored Safes folder. Note: This parameter and ‘FullVaultRestore’ are mutually exclusive and cannot be used together. If a third-party backup application is used, after files have been restored to the Restored Safes folders in the Vault, this parameter will enable PARestore to use the files already in the Vault. Prevents PARestore from copying files to the Restored Safes folder on the Vault file system. A Safe cannot be restored without its corresponding metadata. For this option to work, the metadata must already have been uploaded to the Vault with a separate PARestore command. Only the Safe’s data files will be uploaded and restored, but not the metadata. Only the Safe’s metadata will be uploaded and restored, but not the external files. Therefore, this name must not correspond with an existing Safe. The restore process does not overwrite an existing Safe – it creates a new one. If the Safe was deleted after backup, create a Safe with the same name, and add the same Safe Owners that were assigned to the backed up Safe. This Safe must exist in the backup files from which the restore is made, as well as in the Vault. The Pool Name must match the pool name specified in the backup process, so that you can distinguish between different backup sets. This is used when there are several backup sets for a Vault, or a number of clients used to backup the server. The pathname of a user credentials file containing an encrypted password that the utility will use to log on instead of a password. If the User issues this command without specifying the password and without specifying the /LogonFromFile parameter, the User is prompted for it before the command is carried out. The password of the User specified above. This User must have the ‘Restore All Safes’ authorization in the Vault. The name of the User issuing the command. By default, this file is called Vault.ini. The file containing all the information about the Vault and the Safes within it. This usage is explained in the following table and examples: Option RestoreSafe safename /TargetSafe newname PARestore provides the following options: For more information, refer to Restore Safes or the Vault. Only Users with the ‘Restore All Safes’ authorization in the Vault can restore a Safe. After the metadata backup files are restored to the PrivateArk\Restored Safes\Metadata folder, a synchronization procedure will take place, after which users will be able to work with the files immediately. The Safe data files are restored to the PrivateArk\Restored Safes folder in the same structure as that in which they were backed up. The PARestore utility enables you to restore Safes that have previously been either replicated or backed up to the Vault.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |