cc_staff
147
edits
Recovering data from a compromised VM: Difference between revisions
Recovering data from a compromised VM (view source)
Revision as of 16:57, 18 April 2023
, 1 year agono edit summary
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<languages/> | <languages/> | ||
<translate> | <translate> | ||
| Line 17: | Line 15: | ||
* you will be notified when a ticket is created via OTRS | * you will be notified when a ticket is created via OTRS | ||
==Why do I need to rebuild?== <!--T: | ==Why do I need to rebuild?== <!--T:4--> | ||
* you cannot start an administratively locked VM | * you cannot start an administratively locked VM | ||
* unfortunately a compromised VM is no longer trustworthy | * unfortunately a compromised VM is no longer trustworthy | ||
| Line 23: | Line 21: | ||
* you will need to recover your software, settings, and data | * you will need to recover your software, settings, and data | ||
==What steps should I take to recover?== <!--T: | ==What steps should I take to recover?== <!--T:5--> | ||
* contact the support team and outline your recovery plan | * contact the support team and outline your recovery plan | ||
* if access to the filesystem is required the Cloud support team will unlock the volume | * if access to the filesystem is required the Cloud support team will unlock the volume | ||