Bulk Restore

ZPAT provides capabilities to trigger bulk restore for a set of live connected client devices. Restore is a dispatch operation, hence, the actual completion status of the restore can only be viewed in the Job Logs tab on your Zmanda Pro Server UI.

If there are any errors triggering a restore, you will be able to view them during zpat runtime.

Base requirements

1. A self-hosted instance of Zmanda Pro Server

2. At-least one live connected device per user

3. Storage Vault must be reachable from the client devices

4. The restore-for-devices.csv file in /opt/zmandapro/automations/config configured

5. Admin credentials to access your Zmanda Pro Server

What will be restored?

Restore will be triggered to a specified target Devicename for all the Protected Items (sources) that were configured for that user. Currently, the latest snapshot for each PI will be restored onto the target device.

CSV Configuration

restore-for-devices.csv

	Header	Description
1	DeviceName string	The target device hostname NOTE: - This device must be in an Online state. - Each DeviceName must be unique in the restore-for-devices.csv file
2	use-ram bool	Use RAM for restore operations to enhance performance for systems with limited RAM. If false, Zmanda Pro will use temp files
3	allow-partial-restore bool	Used to continue the restore job when unreadable data chunks are found. Corresponds to the "Allow partial file restores (zero-out unrecoverable data)" option
4	simulate bool	Simulate the restore operation without actually performing it

Command Execution

Refer Common flags here.

/opt/zmandapro/automations/zpat restore