cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to deassign media

r1
Level 5
this is driving me crazy

i created a test volume pool and put one tape in it , tape 00000A . i am unable to delete the tape or remove it from the volume pool

when i try to delete the pool i get this
the specified pool is not empty . pool still contains medai

i have expired the images on the tape but still unable to deasssign and delete ther media
cannot delete assigned volume  . cannt delete assigned media

i tried the deassignbymedia command but that didn't work either . any ideaS ?
35 REPLIES 35

Christoph_Linde
Level 5
Employee
no

r1
Level 5
they are 2 diffeernt tapes that are having the same issue , i am just focusing on 000007 for now and once i resolve this i am sure it will resolve the other . Thanks

r1
Level 5


doing this command didn't hep

bpexpdate -m 000007 -d 0 -host <mymachinename>
this is what i get

Media 000007 is due to expire at 04/18/2010 15:28:00
Are you sure that the data on this media is not critical to
your business, and you are sure you want to delete 000007 y/n (n)? y
invalid command parameter

that link that andy posted didn't help .

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Please post output of:
nbemmcmd -listmedia -mediaid 000007

Please also share more info about your environment:
Is tmnaim01 your master server or a media server?
If media server, is the server 'alive and well'?

The 'admin' log file might shed a bit of light on how NBU interprets the command and options.
If admin dir does not exist on the master, please create it and try bpexpdate again.
Then post section in log file that deals with bpexpdate.

Will_Restore
Level 6

NetBackup status code: 20

Message: invalid command parameter Explanation: One or more command parameters were not valid. This error can occur when incompatible levels of NetBackup are installed on a master and its media server(s) or client(s). For example, a NetBackup master server has NetBackup 6.5 and the media server or the client has NetBackup 4.5.

r1
Level 5
This is on the master server and we don't have media servers . Master and media is the same server . I am still struggling with this . anyone ?

Thanks

Andy_Welburn
Level 6
It may shed some light on the situation.

Otherwise there may be an inconsistency in the EMM d/b that cannot be determined here. This will require the involvement of Symantec who will probably require you run various commands to identify the 'culprit' - place a call with Symantec if you haven't already.

The only other command that comes to light was when I had a "similar" issue with inconsistent images was nbdelete -allvolumes -force followed by bpimage -cleanup -allclients. This was due to some disk images on a decommissioned media server, but there is a T/N that uses this command to clear the error you are seeing:

http://seer.entsupport.symantec.com/docs/347096.htm

(this was why I earlier asked if you were getting the same error on image cleanup)

r1
Level 5
here is the output Media 000007 is due to expire at 04/18/2010 15:28:00 Are you sure that the data on this media is not critical to your business, and you are sure you want to delete 000007 y/n (n)? y invalid command parameter also that tecnote didn't help - i tried the delete and it returned nothing but still having the same issue

Andy_Welburn
Level 6
I meant from the command:

nbemmcmd -listmedia -mediaid <media-id>

Have you placed a support call yet just in case?

r1
Level 5
-bash-3.00# nbemmcmd -listmedia -mediaid 000007
NBEMMCMD, Version:6.5.5
====================================================================
Media GUID:                     78cd3e38-46ee-11df-8000-8a889b4559fe
Media ID:                       000007
Partner:                        -
Media Type:                     HCART
Volume Group:                   000_00000_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    Added by Media Manager
Barcode:                        000007
Partner Barcode:                --------
Last Write Host:                tmnaim01
Created:                        04/13/2010 15:19
Time Assigned:                  04/16/2010 14:58
First Mount:                    04/16/2010 14:59
Last Mount:                     04/16/2010 15:28
Volume Expiration:              04/16/2010 00:00
Data Expiration:                04/18/2010 15:28
Last Written:                   04/16/2010 15:28
Last Read:                      -
Robot Type:                     TLD
Robot Control Host:             tmnaim01
Robot Number:                   0
Slot:                           15
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               2
Maximum Mounts Allowed:         0
Media Status:                   ACTIVE
Kilobytes:                      0
Images:                         0
Valid Images:                   0
Retention Period:               19
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             0
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    tmnaim01
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    13
Volume Pool:                    test
Previous Pool Name:             -
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -
====================================================================
Command completed successfully.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Any reason why there's a volume expiration date?
The volume expiration date that was added is two days before the data expiration date:

Volume Expiration:          04/16/2010 00:00
Data Expiration:                04/18/2010 15:28


Extract from Admin Guide II:
You can change the expiration date for any volume in the EMM database. The expiration date is the age of the media, not the age of the data on the media. It is when the media is considered too old to be reliable.
When the expiration date of a volume has passed, NetBackup can still read it.
However, NetBackup does not mount an expired volume for a write access.
NetBackup writes a warning message to the system console log for a read access request for an expired volume. NetBackup generates an error message for a write request to an expired volume.


If you remove the volume expiration date you might be able to expire the data with bpexpdate...

Andy_Welburn
Level 6
This sneaky little expiration date's good at catching you out, not used a lot & therefore oft overlooked perchance?

r1
Level 5

Ok - sorry for the confusing but here we go , i changed that date manually when i was troubleshooting this issue , i admit that i didn't knowwhat the expiration date was so i changed to the 16th . However , this was after running the expiration and deassign command failed . so i changed the expiration date again but it is istill failing , see bellow





-bash-3.00# nbemmcmd -listmedia -mediaid 000007
NBEMMCMD, Version:6.5.5
====================================================================
Media GUID:                     78cd3e38-46ee-11df-8000-8a889b4559fe
Media ID:                       000007
Partner:                        -
Media Type:                     HCART
Volume Group:                   000_00000_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    Added by Media Manager
Barcode:                        000007
Partner Barcode:                --------
Last Write Host:                tmnaim01
Created:                        04/13/2010 15:19
Time Assigned:                  04/16/2010 14:58
First Mount:                    04/16/2010 14:59
Last Mount:                     04/16/2010 15:28
Volume Expiration:              01/01/2011 00:00
Data Expiration:                04/18/2010 15:28
Last Written:                   04/16/2010 15:28
Last Read:                      -
Robot Type:                     TLD
Robot Control Host:             tmnaim01
Robot Number:                   0
Slot:                           15
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               2
Maximum Mounts Allowed:         0
Media Status:                   ACTIVE
Kilobytes:                      0
Images:                         0
Valid Images:                   0
Retention Period:               19
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             0
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    tmnaim01
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    13
Volume Pool:                    test
Previous Pool Name:             -
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -
====================================================================
Command completed successfully.

-bash-3.00# bpexpdate -m 000007 -d 0
Media 000007 is due to expire at 04/18/2010 15:28:00
Are you sure that the data on this media is not critical to
your business, and you are sure you want to delete 000007 y/n (n)? y
invalid command parameter

CRZ
Level 6
Employee Accredited Certified
You didn't say, but your nbemmcmd output seems to imply you're running 6.5.5.  Is this the case?  Has this always been the case?

What do the admin and/or bpdbm log say?  Look for "invalid command parameter (20)" and then give us the 10 or so lines preceding that (or anything marked with a severity of <16> or greater).

It's possible there's some cruft in your EMM database that's preventing you from completing this expiration.  If that IS the case, I'm afraid you won't be able to get it fixed here - you'll need to open a case with us... and probably get it escalated, too.

r1
Level 5

Hi everyone - Update on this . This issue is resolved now and the only way to resolve it is by having a backline engineer with symantec write a code and apply the fix . a fix was wrote by a programmer at symntec that i had to apply . applying 6.5.6 patch will prevet this from happening again . if anyone out there having this exact isue . call symnatec , they will help you because there is simply no other options :) Thanks again for everyone that tried to help . much appreciated

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Thanks for the update! Maybe ask the Symantec engineer if this problem is explicitly referenced in the 6.5.6 Release Update doc? If so, Etrack number?