Hi there,
Good Morning!
Tip of the day is related to Data Protector (Session abort)
Scenario: If you happen to abort a backup session that was already started and running, do not abort the session directly. (Assuming the backup is copied to tape library.)
Follow the steps below:
> Cancel all the devices that are running
> Then abort the session (either from CLI/GUI)
After the media agents are aborted, you will see the message like below:
[Normal] From: BSM@server01.fp.sa.com "backup_spec01" Time: 1/31/2014 10:28:03 PM
Device canceled by user dpuser1@mgmt01.fp.sa.com
[Normal] From: BMA@server01.fp.sa.com "ESL01_D01" Time: 1/31/2014 10:29:11 PM
ABORTED Media Agent "ESL01_D01"
Good Morning!
Tip of the day is related to Data Protector (Session abort)
Scenario: If you happen to abort a backup session that was already started and running, do not abort the session directly. (Assuming the backup is copied to tape library.)
Follow the steps below:
> Cancel all the devices that are running
> Then abort the session (either from CLI/GUI)
After the media agents are aborted, you will see the message like below:
[Normal] From: BSM@server01.fp.sa.com "backup_spec01" Time: 1/31/2014 10:28:03 PM
Device canceled by user dpuser1@mgmt01.fp.sa.com
ABORTED Media Agent "ESL01_D01"
Reason:
Aborting the session directly would not allow the media agents to a clean exit, which might end in damaging the media headers, chances are there for the media to get stuck in drive, media might be marked as poor.
It is always wise to abort the media agents and then your session.
Have a Great day!
No comments:
Post a Comment
Hi, Just in-case, your comment will be published only after my approval.