![HP Data Protector A.06.11 Скачать руководство пользователя страница 339](http://html.mh-extra.com/html/hp/data-protector-a-06-11/data-protector-a-06-11_integration-manual_164979339.webp)
1.
Data Protector first restores the metadata, which was collected during the backup.
Then it examines the metadata to identify the backup components and determine
the restore method. It also checks if restore to specific volumes is possible.
2.
Data Protector connects to the coordinator (VSS service) to notify that the restore
is about to start, which in turn communicates with the writer. Data Protector
restores the data from the backup media to the locations specified in the backup
metadata. During the restore, Data Protector follows the writers' instructions
regarding any additional checking or processing specified in the WMD.
3.
After the data are successfully restored from the backup media, Data Protector
informs the coordinator that the restore is completed and the writers can now
access the newly-restored data and start the internal processing, for example
recovery.
Restoring files
For a successful restore of a VSS component, all files comprising this component must
be restored. If a restore of a single file fails, the restore of the a whole component
fails. Data Protector offers an additional restore mode for restoring single files that
does not use the Microsoft Volume Shadow Copy Service, thus solving this problem.
This mode can also be used for restoring to systems that do not support VSS or do
not have a VSS writer installed.
When restoring files or a group of files, DMA is started and the files are restored
using the standard Data Protector filesystem restore procedure.
IMPORTANT:
As the file restore mode does not utilize VSS services, additional tasks that are performed
after a component restore – such as database recovery – are not performed and your
application data may be left in an inconsistent state, requiring additional manual
procedures before the application is recovered.
VSS database
The VSS database (VSSDB) is an extension to the Data Protector internal database
(IDB) on the Cell Manager. It holds the VSS integration-specific information about
the VSS backup sessions and their replicas. The stored information can be used for
the following purposes:
•
Instant recovery
•
Data mining (you can save backup components and writer metadata documents)
Zero downtime backup integration guide
339
Содержание Data Protector A.06.11
Страница 18: ...Publication history 18 ...
Страница 83: ...Figure 21 EVA backup options Click Next Zero downtime backup integration guide 83 ...
Страница 85: ...Figure 22 Specifying an Oracle Server system Windows Zero downtime backup integration guide 85 ...
Страница 197: ...Figure 49 XP backup options Zero downtime backup integration guide 197 ...
Страница 198: ...Figure 50 VA backup options Data Protector SAP R 3 ZDB integration 198 ...
Страница 199: ...Figure 51 EVA backup options Click Next Zero downtime backup integration guide 199 ...
Страница 242: ...Data Protector SAP R 3 ZDB integration 242 ...
Страница 256: ...Figure 68 Selecting a snapshot backup Click OK Data Protector Microsoft SQL Server ZDB integration 256 ...
Страница 315: ...1 In the Context List select Restore Zero downtime backup integration guide 315 ...
Страница 328: ...Data Protector Microsoft Exchange Server ZDB integration 328 ...
Страница 363: ...3 Right click MS Volume Shadow Copy Writers and click Add Backup Zero downtime backup integration guide 363 ...
Страница 428: ...Figure 122 Oracle proxy copy ZDB and restore concepts when the ZDB_ORA_INCLUDE_CF_OLF variable is set to 1 Appendix 428 ...
Страница 432: ...Appendix 432 ...
Страница 490: ...Glossary 490 ...