Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

changing expiration on imported images

Updated: 21 May 2010 | 10 comments
Nathan Kippen's picture
0 0 Votes
Login to vote
Is anybody else running into problems with changing the expiration date on imported images?  I've imported several tapes and I need to change the retention on them -- however I keep getting an error that the "media not found in EMM database" ...  Can somebody test this to see if this is a bug?
 
Netbackup 6.0MP5
HP-UX 11.23
1 Master / 4 Media Servers
SSO
 
(I've tried changing expiration date on the individual images and also for the tape, but the results are the same.)
discussion Filed Under:

Comments

Fred2010's picture
17
Dec
2007
0 Votes 0
Login to vote

Hey Nathan,
 
Try adding the -HOST MEDIA_SERVER_NAME option in the BPEXPDATE command.
 
Maybe another server is owning the media???
 
Fred
Nathan Kippen's picture
17
Dec
2007
0 Votes 0
Login to vote

Thank you for the suggestion..
 
I've been working with VERITAS/Symantec for the last week or so, but haven't found resolution yet to my problem.  I have to changing some logging settings and haven't been able to stop/restart services because we're a 24/7 operating center.  I'll post the answer on this thread if I ever get one.  Thanks.
 
 

Symantec Certified Specialist in Symantec NetBackup 7.0
(NBU 7.1.0.2, ACSLS, DataDomain, NDMP...)
Don't forget to vote or mark solution!

Srikanth Gubbala's picture
17
Dec
2007
0 Votes 0
Login to vote

Hi,
 
you can check this command, i was successfull in changing the retention period of all the images on the tape using this command
 
after executing it takes time to change the retention
 
bpexpdate: -m <media_id> -d <mm/dd/yyyy HH:MM:SS | 0 | infinity>
 
example : /usr/openv/netbackup/bin/admincmd/bpexpdate -m DP0023 -d 12/28/2007 00:00:00
 
above example is change the retention from existing retention to 12/28/2007
 
regards,
Srikanth.

regards, Srikanth.

Nathan Kippen's picture
18
Dec
2007
0 Votes 0
Login to vote

Thank you for the suggestions.  I've actually already tried these things but had no luck.  Again I think it's probably something related to tape IDs not being in all my NB databases ... Whenever I try changing the expiration whether a specific image is targeted or an entire tape and with every combination of command options, my attempts are unsuccessful.  Once I find the reason why I can't change the expiration I'll post details on this thread.  Again, thank you.

Symantec Certified Specialist in Symantec NetBackup 7.0
(NBU 7.1.0.2, ACSLS, DataDomain, NDMP...)
Don't forget to vote or mark solution!

Stumpr's picture
20
Dec
2007
0 Votes 0
Login to vote

GENERAL ERROR: When attempting to expire a media in Veritas NetBackup (tm) 6.0 with the bpexpdate command, the message "requested media id was not found in the EMM database" is received.
 
Exact Error Message
Requested media id was not found in the EMM database

Details:

Overview:
When attempting to expire a media in NetBackup 6.0 with the bpexpdate command, the message "requested media id was not found in the EMM database" is received.

Troubleshooting:
If there are database inconsistencies with a media, bpexpdate may not be able to expire it, though it lists as assigned.  

For example, if a volume is assigned, it is normally expected that it would have a associated media server name recorded in the Enterprise Media Manager (EMM) database.  This is the media server that currently "owns" the media.

If a volume is assigned, but does not have a media server listed in the EMM database, there is an inconsistency.  Therefore, bpexpdate may not work and a procedure must be followed to ensure that the media is expired.  Media in this sort of predicament may or may not have unexpired images associated with it.

Log Files:  N/A

Resolution:
The procedure for analyzing and eliminating inconsistencies for a media is as follows, using "A00001" as an example media ID:

1. Use nbemmcmd to list the media server record for the media ID.  If the Media Server: hostname appears as NONE, yet there is a value for Time Assigned:, this indicates an incomplete EMM media record.  In the output below, "A00001" is assigned, but has no associated media server.  

nbemmcmd
Unix: /usr/openv/netbackup/bin/admincmd/
Windows: <Install_dir>\NetBackup\bin\admincmd

Command syntax example and output:
nbemmcmd -listmedia -mediaid A00001

NBEMMCMD, Version:6.0(20050906)
=====================================================
Media GUID:      a5ea9a7a-8d50-13f4-8018-cef85f775cf7
Media ID:        A00001
Partner:         -
Media Type:      HCART
..
Barcode:         A00001
Partner Barcode: --------
Media Server:    NONE
Created:         04/27/2005 16:20
Time Assigned:   05/04/2005 04:20
..
=====================================================
Command completed successfully.

2. Determine if the media ID exists in the merge table.  If the media ID appears in this listing, then a different issue exists, do not proceed further.  Contact Symantec Technical Services for assistance with getting this media ID out of the merge table.  The following example shows no media IDs in the merge table:

nbemmcmd
Unix: /usr/openv/netbackup/bin/admincmd/
Windows: <Install_dir>\NetBackup\bin\admincmd

Command syntax example and output:
nbemmcmd -listmedia -mergetable

The following number of records were found:0
Command completed successfully.

3. From the same path, type "bpimmedia -mediaid A00001" to determine if there are any images on this piece of media.  If there are no images, then no output will be displayed.  If there are images, an IMAGE line and FRAG line will appear for each valid image on the media ID.

4. As long as the media ID does not appear in the merge table, the bptm command can be used to build a complete media record for each affected media ID.  Then the volume can then be unassigned and expired.  This will require the media ID of the affected media, as well as the density and the volume pool number. The following example is from a Solaris 9 server with a media ID of A00001, a density of HCART, that resides in Volume Pool 1 (NetBackup).

bptm
Unix: /usr/openv/netbackup/bin/
Windows: <Install_dir>\NetBackup\bin\

Command syntax example:
bptm -makedbentry -m A00001 -den hcart -poolnum 1

5.  Once this command completes, run the "nbemmcmd -listmedia -mediaid A00001" command again from step 1.  There should now be a valid Media server: hostname.  

6. The tape can now be expired with the bpexpdate command:

bpexpdate
Unix: /usr/openv/netbackup/bin/admincmd
Windows: <Install_dir>\NetBackup\bin\admincmd

Command syntax example and output:
bpexpdate -m A00001 -d 0  

Are you SURE you want to delete A00001 y/n (n)? y

Now that the media is expired, it can be used for backups again and will be overwritten.  If there were images found in step 2 for this media, or if it is desired to retain the data on this media, an import should be performed immediately to ensure that valuable data is not overwritten on that media
 
 

Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige

Nathan Kippen's picture
20
Dec
2007
0 Votes 0
Login to vote

Thanks for your post Bob; unfortunately, I already went through that technote without luck.
 
I should be hearing back from VERITAS today ... I've finally been able to cycle services and send VERITAS some logs that they requested.
 
nk

Symantec Certified Specialist in Symantec NetBackup 7.0
(NBU 7.1.0.2, ACSLS, DataDomain, NDMP...)
Don't forget to vote or mark solution!

Stumpr's picture
20
Dec
2007
0 Votes 0
Login to vote


Nathan Kippen wrote:
... I already went through that technote without luck.


LOL
I should have known because you our a sharp techie. Your a regular contributer. Thanks for helping out in this forum. Keep up the good work.
 

 

Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige

hstankovic@bost.com's picture
19
Oct
2009
1 Vote -1
Login to vote

Can't get to the /usr/openv/netbackup/admincmd directory ????

When I tried to get to the directory for running the commands on a Unix plateform the admincmd doesn't exist.  Thoughts on why this might be?

This is what I have under the /usr/openv/netbackup directory:

drwxrwxrwx   5 root       bin             96 Jul 23  2007 help
-rwxrwxrwx   1 root       bin          34211 Jul 23  2007 vfm_master.conf
-rwxrwxrwx   1 root       bin            104 Jul 23  2007 version
-rwxrwxrwx   1 root       bin           3655 Jul 23  2007 nblog.conf.template
drwxrwxrwx   9 root       bin           4096 Sep 30 15:38 client
drwxrwxrwx   2 root       bin             96 Sep 30 15:39 dbext
drwxrwxrwx  12 root       bin           4096 Oct  7 15:22 db
-rwxrwxrwx   1 root       root          3607 Oct  9 13:47 nblog.conf
drwxrwxrwx  16 root       bin           4096 Oct 15 11:13 logs
-rwxrwxrwx   1 root       sys           2753 Oct 15 16:21 nbsvcmon.conf
drwxrwxrwx   2 root       sys             96 Oct 17 15:21 remote_versions
-rw-r--r--   1 root       root           132 Oct 17 15:44 bp.conf
-rw-r--r--   1 root       sys              6 Oct 19 00:00 version_master
drwxrwxrwx  13 root       bin           4096 Oct 19 09:29 bin

J.Hinchcliffe's picture
19
Oct
2009
0 Votes 0
Login to vote

Should have been a new thread

(Just an FYI this is a brand new question you should have started a new thread)

/usr/openv/netbackup/bin/admincmd

the admincmd is inside the bin dir  - you just need to go down one more dir

I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows

hstankovic@bost.com's picture
19
Oct
2009
0 Votes 0
Login to vote

Your right

Your right I should have started a new thread, sorry.  Thanks for pointing out my error in the path, I didn't see it before.  :)