- Newest
- Most votes
- Most comments
There is no way to trigger a manual backup of the WorkSpaces data drive. Additionally, WorkSpaces only backup the user drive (D drive) for a WorkSpace. The OS Drive (C: drive) is not backed up during a backup job so any programs installed will not be restored during a WorkSpaces rebuild.
Please see Mayank_J's response below for documentation regarding the restore / rebuild process
There needs to be better control of backups. A 12 hour snapshot is great for recovering from a major disaster, but how do we support users migrating between Workspaces (for example if they need to change to a GPU accelerated instance) or when a newer operating system is available?
It would be helpful if there was a way to backup the home drive to an external service/S3 so that such a migration could occur. It would also make it easier to perform restore of individual files rather than the entire system.
Relevant content
- asked 7 months ago
- asked 3 months ago
- Accepted Answerasked 3 years ago
- asked a year ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 10 months ago
The Workspaces service does backup both root (C:) and user (D:) volumes in form of snapshot every 12 hours. But depending on whether you rebuild a Workspace[1] or restore a workspace[2] it would differ how those snapshots are used.
[1] https://docs.aws.amazon.com/workspaces/latest/adminguide/rebuild-workspace.html [2] https://docs.aws.amazon.com/workspaces/latest/adminguide/restore-workspace.html
This is absurd. I need the ability to manually backup Workspaces builds in progress; Workspaces from which our images are created, and need backup before and after major updates/installs. If said install breaks the workspace I am building for image-creation, then I get to start completely from scratch because AWS is blocking user's access to manually use a built-in function of AWS, workspace-backup.
Not allowing the manual backup of individual workspaces is utterly inexcusable, in my sincere opinion. There is no excuse for such penny-pinching restrictions being placed on paying customers.
You can take manual backup of the data using any 3rd party tools but you can't rebuild or restore Workspaces using that backup. You can only restore the data from that backup. Workspaces restore and rebuild functionality will always use the snapshots taken by the service.