VERITAS NetBackup will not allow an assigned media to be moved to a different volume pool.

Article:TECH20603  |  Created: 2009-01-28  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH20603
Article Type
Technical Solution


Environment

Issue



VERITAS NetBackup will not allow an assigned media to be moved to a different volume pool.

Error



Change pool of failed: cannot change volume pool for assigned volume (91)

Solution



Once a media has been handed to NetBackup by Media Manager for the use of client backups, the media is transitioned from being 'available' to 'assigned'. From the NetBackup databases viewpoint, this implies the following:

    - the volume database (volDB) is populated with information such as; the media status being assigned, the assigned time, and the volume pool to which the media belongs, etc.

    - the media database (mediaDB) of the Media Server who conducted the backup is also populated with information such as; the volume pool to which the media belongs, its retention level, etc.

    - the image database is populated with information on the backup images such as backup ids, copy number, which Media Server(s) conducted the backups, etc.

It is imperative that the databases are consistent with one and another!
In the context of volume pools, once a media in a specific volume pool has been used for backups (i.e. it contains valid images), it is committed to be in that volume pool. VERITAS NetBackup will not allow a media to have data written from 2 unique volume pools in order to maintain the consistency of its databases.

Should there be a reason as to why the volume pool of a media needs to be changed while it contains valid images, then the consequences must be understood as this may cause database inconsistency, which in turn may lead to data loss and database cleaning problems such as Error 94 (see TechNotes 247898 and 245430 in the "Related Documents" section below). Although manual manipulation of the databases can be performed to change the volume pool of a media, it is not recommended, unless of course it is to synchronize the databases from an otherwise inconsistent state (see TechNote 247898).

If the volume pool of a media needs to be changed (in an environment where the databases are already in a consistent state) then the safest choices of solutions are as follows:

    1. Wait for all of the images associated with that piece of media to expire. Once this has taken place, the media should be automatically deassigned from the volDB, after which time it is free to be moved to another volume pool.

    OR

    2. Manually and immediately expire all the images with the bpexpdate command, and then change the tape to the desired volume pool.


Commands

    - For immediate expiration of all images:

      UNIX platforms:  /usr/openv/netbackup/bin/admincmd/bpexpdate -ev <media_id> -d 0
      Windows platforms:  install_path\VERITAS\netbackup\bin\admincmd\bpexpdate -ev <media_id> -d 0

    NOTE: Once this command is executed, all valid images associated with this media id are immediately deleted from the image database.


    - For changing volume pools:

      UNIX platforms:  /usr/openv/volmgr/bin/vmchange -p <pool number> -m <media_id>
      Windows platforms:  install_path\VERITAS\volmgr\bin\vmchange -p <pool number> -m <media_id>  

      where <pool number> is the pool number of the desired new volume pool;
          <media_id> is the id of the media to which the change is to be applied.



Legacy ID



248093


Article URL http://www.symantec.com/docs/TECH20603


Terms of use for this information are found in Legal Notices