BUG REPORT: The Vault eject setting "suspend immediately" fails to suspend media when duplication is skipped.

Problem

BUG REPORT: The Vault eject setting "suspend immediately" fails to suspend media when duplication is skipped.

Error Message

vltrun@suspendMediaGenEject^187: Not suspending MDA=AAA104 with no suspend host set

Solution

Bug: 1282306

Detail/Symptoms:
In NetBackup 6.5 and above, the suspend mode NOW is honored only by the duplication step and catalog backup step.

If these two steps are OFF, the suspend NOW doesn't work on the corresponding media (duplication media and catalog media) as expected.

Log Files:
Running egrep against the vault.xml file demonstrates these settings:
# egrep -i "profile id|duplication |suspend" ../../db/vault/vault.xml            
     <PROFILE Id="2" LastMod="12120237339225360" Name="my_dsu">
       <DUPLICATION DiskDeleteHours="1" DupPriority="99999" Multiplex="NO" SharedRobots="NO" Skip="NO" SortOrder="1">
       <EJECT EjectMode="MANUAL" Skip="NO" Suspend="NO" SuspendMode="NOW" UseRbtorVaultPrefENE="YES">
     <PROFILE Id="3" LastMod="12120255253831530" Name="suspend_only">
       <DUPLICATION Skip="YES"/>
       <EJECT EjectMode="MANUAL" Skip="NO" Suspend="NO" SuspendMode="NOW" UseRbtorVaultPrefENE="YES">

From the output of egrep run against the Vault log, it can be seen that the suspend doesn't happen:
# egrep -i "duplication skip|DuplicationJob::monitor_l|ejectm|suspendm|suspend" 12269.txt
18:33:56.621 [12269] <4> vltrun@save_vault_conf()^187: DUPLICATION Skip=NO DiskDeleteHours=1 SharedRobots=NO Multiplex=NO SortOrder=1 DupPriority=99999
18:33:56.626 [12269] <4> vltrun@save_vault_conf()^187: EjectMode=Manual
18:33:56.627 [12269] <4> vltrun@save_vault_conf()^187: SuspendMode=NOW
18:44:22.450 [12269] <8> vltrun@DuplicationJob::monitor_log^187: Found Job Complete. LINE=18:44:17 INF - Status = successfully duplicated 4 of 4 images.
18:44:31.967 [12269] <2> vltrun@SuspendMedia^187: suspending media AAA104 with host myhost
18:44:32.089 [12269] <2> vltrun@SuspendMedia^187: suspend media even if allocated
18:44:32.432 [12269] <2> vltrun@SuspendMedia^187: media AAA104 with host myhost is suspended successfully
18:44:33.806 [12269] <2> vltrun@VltSession::lock_and_operate^187: OP: suspend_media
18:44:33.807 [12269] <2> vltrun@VOpMinor::doOperation^187: OP=suspend_media
18:44:33.807 [12269] <8> vltrun@DoSuspend^187: Skipping suspend, function not enabled in Params
18:44:35.591 [12269] <4> vltrun@AddSelectedImagesEjectMedia^187: MDA=AAA104 HOST=NONE to be added to eject.list
18:44:35.593 [12269] <4> vltrun@AddAddonEjectMedia^187: No addon_medialist file found
18:44:35.594 [12269] <4> vltrun@AddDLMEjectMedia^187: No DLM pools specified for Eject
18:44:48.886 [12269] <2> vltrun@GenMediaEjectList^187: ADDed media=AAA104 SUSPEND host=NONE for Eject
18:44:48.888 [12269] <2> vltrun@GenMediaEjectList^187: SuspendMode is NOW, suspending media for this session
18:44:48.889 [12269] <2> vltrun@suspendMediaGenEject^187: entering...
18:44:55.639 [12269] <4> vltrun@suspendMediaGenEject^187: Not suspending MDA=AAA104 with no suspend host set

Workaround:
1. Create profileA to do just duplication to vault volume pool.
2. Run a session with profileA.
3. Create profileB to do just deferred eject with suspend mode set to "NOW/immediately".
4. Run the session with profileB.
5. This fix ensures that, on step 3, eligible media are suspended during the geneject processing.

Please apply the appropriate release update to resolve this issue.

ETA of Fix:
The formal resolution to this issue (Etrack 1282306) is included in the following patch release:
  • NetBackup 6.5 Release Update 3 (6.5.3)
This release is available at the support web site at:
 http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)