Quantum| recovery_fs |
The recovery_fs process creates and services the “/recover/images” filesystem. This file system is typically exported via NFS and CIFS to allow access from other hosts for VM image-level recovery (vmx, vmdk, -flat.vmdk and cfg files).
The recovery_fs process reads all of its data from the “/storage” file system. (Prior to 3.0 software, the recovery_fs process read all of its data from the “/scratch” file system)
The “/storage” file system itself is imported by the vmPRO appliance via NFS or CIFS. This import is set up using the vmPRO Recovery Wizard from the GUI which causes /storage to mount on the vmPRO appliance. See the screen shot below:
The “/storage” file system can contain ordinary ascii files, “-flat.vmdk” files, and “–pancbt.vmdk” files. Ordinary ascii files in “/storage” are exported by recovery_fs unchanged, in “/recover/files”. The “-flat.vmdk” files are merged with “-pancbt.vmdk” files (if appropriate), and then exported as one “merged” file. The “-pancbt.vmdk” files are not exported by recovery_fs, and are only used as part of the merging process, and –pancbt files do not appear in the “/recover/images” file system. Only image level access is provided by recovery_fs. File-level access is provided by a separate daemon (recovery_fs_files).
An open operation of a flat vmdk file in “/recover/images” causes recovery_fs to look for a corresponding “-pancbt.vmdk” file, and perform a merge, if required.
The recovery_fs daemon also recognizes SmartMotion “.json” files, which represent soft-links to –flat.vmdk files. The recovery_fs daemon follows the soft-links, and automatically presents the files as part of the current directory.
Process Communication Flow
|
/storage => |
recovery_fs => |
/recover/images |
|
xxx-flat.vmdk xxx-pancbt.vmdk => |
“merge” => |
xxx.flat.vmdk (merged version) |
|
xxx.vmdk => |
“no merge” => | xxx.vmdk |
Troubleshooting:
The recovery_fs daemon writes log entries to “/var/log/recovery_fs”. The daemon writes debug output to this file, when so enabled. Setting the registry key appliance.debug.level to a small positive integer will enable general debug output, which increases in verbosity with a higher value. Note that setting these keys can result in significant log output.
This page was generated by the BrainKeeper Enterprise Wiki, © 2018 |