Image Backup (desktop interface only)
Image backup performs a block-level backup, typically to tape. Free space is not backed up. Image backup is used only to provide a base backup for remote seeding and to protect the Catalogic DPX Open Storage Server. For remote seeding, Image runs only as a base backup; for protection of Catalogic DPX Open Storage Server, Image runs as an initial base backup followed by incremental backups. Image backup is not supported for incremental or differential backup of clients. However, if incremental or differential Image backup information exists in the Catalog from an upgraded environment and the Image backups are preserved, the backups can be used for restores. For Linux Users, note that only base backup is supported for remote seeding purposes.
Note the following consideration for Image backup:
Only appropriate device clusters or tape libraries appear in the destination pane of the backup window. DPX directs the data to one of those storage devices.
The minimum amount of free disk space required on the client to run Image backup jobs is as follows:
10% of the total volume size for volumes smaller than 5 GB and 500 MB for volumes greater than or equal to 5 GB.
For Image backups, if the status of a disk object is offline, you cannot browse the disk in the management console or select it for backup.
File exclusion is not supported for Image backup.
Selecting a descendant resource for exclusion by clicking it is not permitted in the source pane of the Image backup window.
Only one snapshot of a volume can exist at any time on a volume. Thus if you run an Image backup of a volume that is currently being backed up by a different Image backup job or a Block backup job, it will fail.
Mount points appear to the right of the volume icon in the format:
{volume_name} mount_point_directoryImage backup does not directly support the backup of active database applications. Run a Block backup after seeding to recover application-consistent data.
Image backup is not supported for clusters.