Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.11 Microsoft Exchange Server User Guide

Export data for deleted backup copies

This option enables you to export results of deleted backup copies to a .csv file so that you can download an Excel file of the data.

Steps

  1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.
  2. From the Assets window, select the tab for the asset type for which you want to export results of deleted backup copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.
  3. Select one or more protected assets from the table, and then select More Actions > Export Deleted Copies.
    If you do not select an asset, PowerProtect Data Manager exports the data for deleted backup copies for all assets for the specific asset type.
  4. Specify the following fields for the export:
    1. Time Range
      The default is Last 24 Hours.
    2. Copy Status

      In order to export data for deleted backup copies, the backup copies must be in one of the following states:

      • Deleted—The copy is deleted successfully from protection storage, and, if applicable, the agent catalog is deleted successfully from the agent host.
      • Deleting—Copy deletion is in progress.
      • Deletion Failed—Copy deletion from protection storage is unsuccessful.
      NOTE You cannot export data for backup copies that are in an Available state.
  5. Click Download.
    If applicable, the navigation window appears for you to select the location to save the .csv file.
  6. Save the .csv file in the desired location and click Save.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\