Quantum| Troubleshooting vmPRO Restore Errors |
When vmPRO full restores fail, an alert is posted in the GUI, but not much other troubleshooting information is displayed. Using the logs, you can gain information that will help you determine the cause of the restore failure.
This is the first of a set of three articles on vmPRO restores. Together, the articles cover the following main topics:
vmPRO has two separate types of restore, which are covered in detail in the next two articles, and briefly in this article:
Both types of restore are managed by the recovery_fs.
In vmPRO 3.0.1, you can perform image-level restores from the web GUI or vCenter console plugin via the recovery wizard or from the /recover/images mount as presented by Samba.
If a VM backup was done using SmartMotion, file-level restores are done by browsing to /vmpro_<ip_address>/recover/files. If the backup was done by a third-party agent such as NetBackup, the VM image must first be recovered using the same agent. Then, file-level access is available by browsing to the file.
Previous vmPRO versions included file-level restore in the web GUI, but there is no file-level restore wizard in the current release.
The following simplified snippet of the smb.conf file shows that the vmPRO appliance makes image-level and file-level restores available from a UNC path.
Note: In the listing below, comments about the listing appear in bold green text.
……………………
[global] (Global vmdk setting to illustrate domain and security access)
workgroup = WORKGROUP
server string = "Quantum vmPRO"
security = user
printing = bsd
load printers = no
disable spoolss = yes
force user = root
unix password sync = yes
#log level = 6
log file = /var/log/samba/samba.log.%m
max log size = 500
debug timestamp = yes
passdb backend = smbpasswd
oplocks = no
……………………
[recover]
path = /recover
comment = "Quantum Recover"
browseable = yes
writeable = no
printable = no
vfs objects = ntfs3g
This page was generated by the BrainKeeper Enterprise Wiki, © 2018 |