180 likes | 305 Views
Module 7 : Backups. Agenda. Unidesk Backup Concepts Backing up the MA, MCP and shared Layers Personalization layer backup process Restoring a personalization layer. Typical Unidesk Components. Management Appliance Contains Config Database Entire VM gets backed up.
E N D
Agenda • Unidesk Backup Concepts • Backing up the MA, MCP and shared Layers • Personalization layer backup process • Restoring a personalization layer
Typical Unidesk Components Management Appliance Contains Config Database Entire VM gets backed up Backup Storage Volume(s) Desktop CachePoint Has required layers to support desktops and personalization layers Master CachePoint Maintains copy of all layers, acts are replication hub MA MCP CP App OS App OS Pers OS App App Pers App App Pers App Pers App Pers
Typical Unidesk Components Backup Storage Volume(s) MA MCP OS App OS App App App MA MCP CP App Pers Pers App OS App OS Pers OS App App Pers Pers Pers App App Pers App Pers App Pers
Backing Up the MA and MCP • MA can be backed up like any other VM (using VM backup tools) • MCP has independent disks which traditional tools do not backup. Therefor: • Volume level replication/copies (using SAN tools if available). • Unidesk MA and MCP Backup Utility • Run Manually or • Scheduled
Unidesk MA and MCP Backup Tool • MA and MCP should be on the same datastore • MA and MCP should be on the same host (if running one command) • Must have root password for the ESXi server • Win7 or Win Srvr 2008 R2 to run the backup utility • VMware PowerCLI 5 (5.1 most current) required • Mail Relay for e-mail notifications
Backup Process for MCP/MA • MCP Appliance and shared layers are backed up • Utility does NOT backup personalization layers on the MCP • Backup does not backup MA/MCP snapshots • The VM is shutdown prior to its backup (copy) layers are copied using powershell since VMW backups do not backup independent disks
Lab Configuring and running MCP backups
Personalization Layer Backups • Backs up ONLY the personalization layer • Leverages snapshots to minimize backup space • Automated backup time set at the desktop level (via template or manually) • Retention Policy set globally • Personalization layer automated backups are NOT required but recommended and can be done manually also
Personalization Layer Backup Chain Backup Storage Volume(s) Personalization Layer Personalization Layer Snapshot Snapshot Snapshot Snapshot Snapshot
Setting the Backup Time • Can be set at the desktop • Also can inherit from the template
Repairing/Restoring Pers Layer • Same CachePoint or different CachePoint • Clear/Wipe the pers layer • Restore Apps/Settings or data, or Both
Lab Configuring and running backups
Splitting up the backups • Split load up by CachePoint or Time • If running all backups simultaneously split up the “archive” tier for each CP to its own data store or • Set the desktops on specific datastores (CPs) to backup at specific times of the day
Splitting backups by time CP1 Single Storage Volume(s) 6 PM Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers CP2 7 PM Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers CP3 Pers Pers Pers 8 PM Pers Pers Pers Pers Pers Pers Pers Pers Pers
Splitting backups by datastore CP1 6 PM Backup Volume 1 Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers CP2 Backup Volume 2 6 PM Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers CP3 Backup Volume 3 6 PM Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers Pers
Questions you may see again • Automated personalization layer backup times are set where? • Is the backup retention policy global or can it be set per desktop? • The archive tier for personalization layers is set per desktop, per CP, or per MA? • Can you use a standard VM backup tool to backup the MCP and MA?