Vault does not eject any tapes and the error "Rejected - No frag in robotGroup" is seen in the vault detail log for the session ID.
Exact Error Message
Rejected - No frag in robotGroup
Rejected - No frag in robotGroup
Details:
\netbackup\db\vault\vault.xml (Windows)
\Volmgr\bin\vmquery -pn (Windows)
Figure 2 - Session ID from the vault job details
Troubleshooting:
Once the above information has been collected, perform the following:
1. Inspect the RobotVolumeGroup entry specified at the Vault Name level under which the profile that is not ejecting tapes resides. It should be something similar to 00_000_TL8 (see Figure 3).
Figure 3 - Robotic Volume Group in the vault.xml file
2. Check where one of the images (that suffered the error) resides by performing the following:
Resolution:
If the vmquery output shows a volume group different to the one specified in the vault configuration file (vault.xml), then the tapes will never be ejected. There are two different ways to resolve this, as follows:
A. The vault configuration will need to be changed so that it specifies a new Robotic Volume Group.
To do this:
B. Change the robotic volume group associated with the media to match what the vault is looking for.
To do this:
CAUTION:
Overview:
The error "Rejected - No frag in robotGroup" may be seen when Vault has been configured to eject "original" tapes, but no tapes were picked up for ejection. A possible reason for this is that the Robotic Volume Group is incorrect in the Vault configuration. Vault will only eject tapes that belong to the Robotic Volume Group specified at the "Vault Name" level of the configuration. Figure 1 shows where to find the Robotic Volume Group information.
Figure 1 - Robotic Volume Group in the Vault configuration GUI
Log Files:
To determine if the Robotic Volume Group is incorrect, the following information will need to be collected:
The error "Rejected - No frag in robotGroup" may be seen when Vault has been configured to eject "original" tapes, but no tapes were picked up for ejection. A possible reason for this is that the Robotic Volume Group is incorrect in the Vault configuration. Vault will only eject tapes that belong to the Robotic Volume Group specified at the "Vault Name" level of the configuration. Figure 1 shows where to find the Robotic Volume Group information.
Figure 1 - Robotic Volume Group in the Vault configuration GUI
Log Files:
To determine if the Robotic Volume Group is incorrect, the following information will need to be collected:
(i) The name of the vault and the profile that is not ejecting tapes.
(ii) The vault configuration file:
/usr/openv/netbackup/db/vault/vault.xml (UNIX)
(iii) The output of the command:
/usr/openv/volmgr/bin/vmquery -pn (UNIX)
Note: Use the volume pool name(s) listed in the Eject tab of the profile (that is not ejecting tapes). There may be more than one volume pool listed. This command should be run for each volume pool.
(iv) The \netbackup\vault\sessions\\SIDXXX directory (Windows)
The /usr/openv/netbackup/vault/sessions//SIDXXX directory (UNIX)
where "XXX" matches the session ID from the job details in activity monitor. Figure 2 below shows the session ID.
Figure 2 - Session ID from the vault job details
Troubleshooting:
Once the above information has been collected, perform the following:
1. Inspect the RobotVolumeGroup entry specified at the Vault Name level under which the profile that is not ejecting tapes resides. It should be something similar to 00_000_TL8 (see Figure 3).
Figure 3 - Robotic Volume Group in the vault.xml file
2. Check where one of the images (that suffered the error) resides by performing the following:
(i) From the detail.log file within the sid directory, find an image that exhibits the error message:
04:37:19.841 [23584] ImgFilterVaulted(): Image: hostname_1135991212 Rejected - No frag in robotGroup
(ii) Then run the bpimagelist command to obtain details of this image:
# /usr/openv/netbackup/bin/admincmd/bpimagelist -backupid hostname_1135991212
IMAGE hostname 0 0 7 hostname_1135991212 policy 13 ...
HISTO -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
FRAG 1 1 14327919 0 2 15 1 C01243 ...
The FRAG line shows that the image is on tape C01243
(iii) Check the volume group where tape C01243 resides using the vmquery -m
# /usr/openv/volmgr/bin/vmquery -m C01243
==================================================
media ID: C01243
media type: 8MM cartridge tape (4)
barcode: ABCO1423
media description: NT|826|S981|20040421
volume pool: Duplicate (6)
robot type: TL8 - Tape Library 8MM (6)
robot number: 0
robot slot: 43
robot control host: spnbu02-nbu
volume group: 00_000_TL8
vault name: NT
vault sent date: Mon Oct 04 14:19:22 2004
vault return date: ---
vault slot: 834
vault session id: 57
vault container id: -
created: Wed Mar 17 14:02:45 2004
assigned: Sun Oct 03 14:37:13 2004
last mounted: Sun Oct 03 18:00:29 2004
first mount: Wed Mar 17 14:04:50 2004
expiration date: ---
number of mounts: 8
max mounts allowed: ---
status: 0x0
==============================================
Resolution:
If the vmquery output shows a volume group different to the one specified in the vault configuration file (vault.xml), then the tapes will never be ejected. There are two different ways to resolve this, as follows:
A. The vault configuration will need to be changed so that it specifies a new Robotic Volume Group.
To do this:
1. Open the NetBackup Administration GUI and expand Vault Management.
2. Right-click on the name of the vault that is incorrect, and click Change.
3. Change the Robotic Volume Group entry to match the Volume Group entry in the vmquery output and save.
4. Re-run the vault profile and the tapes should be ejected
B. Change the robotic volume group associated with the media to match what the vault is looking for.
To do this:
1. Open the NetBackup Administration GUI and expand Media
2. Right-click on the media you want to change.
3. Select "Change Volume Group" from the drop down menu.
4. Use the drop down menu to select the proper Volume Group entry in the vmquery output (or type it in) and click OK.
5. Re-run the vault profile and the tapes should be ejected.
CAUTION:
I. For Resolution A - If the Vault Offsite Volume Group for the Vault concerned already houses tapes of a certain media density, then ensure that the Robotic Volume Group being changed in the Vault configuration also houses tapes of the same media density. If the media density differs, then eject will fail at the point when Vault tries to move the tapes to the offsite volume group (most likely with error 101 media type and volume group mismatch) . This is because a volume group (offsite or robotic, other than "---") cannot house more than one media density.
Note: The media density is not an issue for Resolution A if the Vault Offsite Volume Group is not yet assigned to any particular media density at the time of the eject. However, as soon as it does, it is obliged to stick with that media density. It is only freed from this obligation if all the tapes in it are moved elsewhere (to another volume group).
II. For Resolution B - the move of medias / tapes to another volume group will only succeed if the volume group that the tapes are moving into either already houses the same density, or is not yet assigned to a particular media density. Moving medias of a certain media density to a volume group of another media density will result in error 101 (as above).
No comments:
Post a Comment