Running multiple parallel operations fails in SnapManager

Contributors NetAppZacharyWambold akseldavis Download PDF of this page

When you run multiple parallel operations on separate databases that reside on the same storage system, the igroup for LUNs associated with both the databases might get deleted because of one of the operations. Later, if the other operation attempts to use the deleted igroup, SnapManager displays an error message.

For example, if you are running the backup delete and backup create operations on different databases almost at the same time, the backup create operation fails. The following sequential steps show what happens when you run backup delete and backup create operations on different databases almost at the same time.

  1. Run the backup delete command.

  2. Run the backup create command.

  3. The backup create command identifies the already existing igroup and uses the same igroup for mapping the LUN.

  4. The backup delete command deletes the backup LUN, which was mapped to the same igroup.

  5. The backup delete command then deletes the igroup because there are no LUNs associated with the igroup.

  6. The backup create command creates the backup and tries to map to the igroup that does not exist, and therefore the operation fails.

What to do

You must create igroup for each storage system used by the database by using the following command: sdcli igroup create