Erasing Symantec Protection Network files

You can erase Symantec Protection Network files if you no longer need them. When you erase Symantec Protection Network files, Backup Exec removes the data from both the Symantec Protection Network folder and the disk. It also removes the file references from the catalog. However, the Symantec Protection Network file remains for use with future backup jobs.

Caution:

You cannot restore the data that you erase. Before you erase files, be sure that you no longer need them.

To erase a Symantec Protection Network file

  1. On the navigation bar, click Devices.

  2. Expand the icon for the computer where the Symantec Protection Network folder is located.

  3. Under Symantec Protection Network, select the Symantec Protection Network folder that contains the file that you want to erase.

  4. In the Results pane, select the file that you want to erase.

  5. In the task pane under Media Tasks, select Erase media, quick.

  6. Click OK to continue.

  7. Click Yes, or if more than one file was selected, click Yes to All.

  8. Select the appropriate options as follows:

    Job name

    Type a name for the job or accept the default name.

    Job priority

    Select the priority for the job.

    The following options are available:

    • Lowest

    • Low

    • Medium

    • High

    • Highest

  9. If you want a person or group to be notified when the job completes, in the Properties pane, under Settings, click Notification.

    See Setting up notification for alerts.

  10. Do one of the following:

    To run the job now

    Click Run Now.

    To set scheduling options

    Under Frequency, click Schedule.

    See Scheduling jobs.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.