problem to change the volume and backup

[Pavz]

Hi
i have queries...
I have assigned a volume to the volume pool and took backup.
Then i want to change the volume to other pool but it shows "cannot change the volume pool for assigned volume.cannot change media pool of assigned media"

1.How can i make available the media and reassign to the other pool?

I have made a volume pool with media and took backup lots. But now it shows "Error nbjm (pid=1132) NBU status: 96, EMM status: No media is available"

I have checked the storage unit and volume pool, all contain media and changer.
2. How can i resolve this?
unable to allocate new media for backup, storage unit has none available (96)

[CraigV]

...moved to the NBU forum. You're going to get greater visibility if you post in the correct forum...

[Marianne]

The error message is 100% correct - you cannot change a tape's volume pool once you have written backups to it.

This is also explained in NBU Admin Guide 1 under the topic 'About assigning volumes'.

The media will become available once all the backup images have expired.

To find out why you are seeing status 96, please post output of this command from cmd on the master:

available_media     (command can be found in ....\netbackup\bin\goodies)
If this command produces lots of output, run it again and send output to a text file (e.g available_media > tempfile.txt )

as well as policy config of the one that is now failing with status 96:

bppllist <policy-name> -U  (please note the big U. command can be found in ....\netbackup\bin\admincmd)

PS: Please always tell us which NBU version and which OS - it makes giving advice a lot easier...

[CRZ]

We also have a "Virtual Assistant" for status 96 - it might be worth it to give it a try and see if it can help you solve your problem:

http://www.symantec.com/business/support/index?page=answers&type=wizard&wizardid=NBU090&wizardstepid...

(If for some reason that link doesn't work, hit up our support page and enter "status code 96" in the Knowledge Base Search box.

[Anonymous]

Chris thats a handy wizard, useful for operators to understand the steps and places where a 96 code can result.

+1

[Pavz]

hi

this is Solaris 10 platform and NBU version is 7.1

available-media

media   media   robot   robot   robot   side/   ret    size     status

 ID     type    type      #     slot    face    level  KBytes

----------------------------------------------------------------------------

CatalogBackup pool

DataStore pool

A00000  HCART    TLD      0       41     -       -     -        AVAILABLE

NetBackup pool

O620L3  HCART    TLD      0       17     -       9     14120680 ACTIVE

None pool

test-pool pool

root@cluster2 # /usr/openv/netbackup/bin/admincmd/bppllist test-policy -U

------------------------------------------------------------

Policy Name:       test-policy

  Policy Type:         Standard

  Active:              yes

  Effective date:      01/10/2012 13:15:34

  Client Compress:     no

  Follow NFS Mounts:   no

  Cross Mount Points:  no

  Collect TIR info:    yes

  Block Incremental:   no

  Mult. Data Streams:  no

  Client Encrypt:      no

  Checkpoint:          no

  Policy Priority:     0

  Max Jobs/Policy:     Unlimited

  Disaster Recovery:   0

  Collect BMR info:    no

  Residence:           cluster2-hcart-robot-tld-0

  Volume Pool:         NetBackup

  Server Group:        *ANY*

  Keyword:             (none specified)

  Data Classification:       -

  Residence is Storage Lifecycle Policy:    no

Granular Restore Info:  no

  HW/OS/Client:  Solaris       Solaris10     atlvip

  Include:  /oradata02

  Schedule:          test-schedule

    Type:            Full Backup

    Frequency:       every 7 days

    Maximum MPX:     1

    Synthetic:       0

    PFI Recovery:    0

    Retention Level: 9 (infinity)

    Number Copies:   1

    Fail on Error:   0

    Residence:       (specific storage unit not required)

    Volume Pool:     (same as policy volume pool)

    Server Group:    (same as specified for policy)

    Residence is Storage Lifecycle Policy:     0

    Daily Windows:

root@cluster2 # 

[Marianne]

You seem to have a fairly large tape library (that can take 41 or more tapes) with only 2 tapes in the library?

One tape with a barcode in NetBackup pool and another tape without a barcode in DataStore pool?

Are you trying to change the pool for media id O620L3?

How many media servers do you have in this environment? Media is by default not shared between media servers.

If all the backups on tape O620L3 have been written by the same media server, there should be no reason for policy test-policy to fail with 96.
The backup should be able to append to O620L3 for the following reasons:

media id O620L3 is in the robot,
is in the same pool as specified in policy (NetBackup),
the correct density (hcart),
is the same retention as schedule test-schedule (9),
is not FULL, FROZEN, SUSPENDED, IMPORTED

[Pavz]

yes i am trying to change the pool of media id O620L3

I just make a test policy to take backup and i have done the backup many time. Then it given failed code 96. Nothing was changed.

I have checked the density,policy,test schedule but all are unchanged.

Then i tried to change the volume to another pool and also made expaired but failed.

Is there any way forward to change the volume to another pool. 

[mph999]

Run this command :

bpmedialist -m O620L3, post the output up here .

Thanks,

Martin

[Marianne]

According to available_media output, media-id O620L3 is in the NetBackup pool, contains 14120680 Kb data with retention level of Infinity. The data on this tape was so important that you chose retention level that will never expire.

Ensure that you have enough tapes in the robot for different data usage (volume pools) or else use the same pool for all your backups to save on media usage.

Please also bear in mind that NBU does not mix retention levels on a tape.

Have a look at this TN for a better understanding of how NBU chooses media in a robot:

http://www.symantec.com/docs/HOWTO32854

[Pavz]

Thank u for ur advice....

I ahve enough tape. Now how can i expire the volume.

Please guide me how can i delete my test policy.

[mph999]

You can expire a volume like this :

bpexpdate -m <media id of tape> -d 0 

Be very very very careful with this command.  Once you run it, the tape becomes available for use again and may be overwritten.

If you run this on the 'wrong' tape, you could end up losing data, so be very careful.

Martin

[Marianne · Accepted solution]

To delete test policy - right-click in GUI on policy name, select Delete.

[mph999]

Opps, should have read the question a bit better  - Marianne saves the day ...

[Pavz]

thanks....mph and marianne.but some time it can't delete like this way.that way i raise the question if it have any other way.forcfully

[Mark_Solutions]

bppldelete policyname -M mastername

Just substitue the policy name and master server name in the above - add -v for verbose if it is failing to see why

[Marianne]

 "but some time it can't delete like this way"

You need to give us more .... Are you getting an error?

Can you give us the error message or a screenshot?

Are you logged into the Java GUI as root?