![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 1579034.1 : Sun Storage 7000 Unified Storage System: Unable To Destroy Replication Snapshots
In this Document
Created from <SR 3-7697476591> Applies to:Sun Storage 7110 Unified Storage System - Version All Versions and laterSun Storage 7210 Unified Storage System - Version All Versions and later Sun Storage 7310 Unified Storage System - Version All Versions and later Sun ZFS Storage 7120 - Version All Versions and later Sun Storage 7410 Unified Storage System - Version All Versions and later 7000 Appliance OS (Fishworks) SymptomsUnable to destroy replication snapshots in a project. The following error is displayed: This snapshot is in use by a replication action and can only be destroyed by destroying the corresponding action.
Even though we have not configured replication on this project, the (project) snapshots are created automatically and we are not able to delete them.
CauseWhenever replication is configured, regardless of whether it is a share level replication or a project level replication. The snapshot is created from the project level, for which every single filesystem and LUN within that project will get snapshotted.
Beside from the above, this can also happen if the share is moved into a different project when there is a replication action on the original project. The snapshot is no longer maintained as part of the replication action, and it cannot be deleted as long as the replication action on the original project still exists.
SolutionIt is not possible to remove those snapshots. If only some of the shares are required to be replicated within a project, consider keeping those shares that require replication in a separate project. Hence, avoiding non-replicated shares to get snapshot together within the same project.
If the issue is seen due to moving of the share to a different project when there is a replication action on the original project, then please contact Oracle Support to help resolve the issue. Check the uuid included in the snapshot name to see which replication action it corresponds with. Replication UUIDs can be listed on the source with: echo "::walk nas_repl_action|::nas_repl_action " | mdb -R ./mdb <akd core>
If it corresponds with an action on a different project, then the share was moved from one project to another. In order to delete this obsolete snapshot, either the customer will have to delete the corresponding replication action, i.e. the one on the original project (which means starting replication over from scratch on that project), or an Oracle engineer can do the following remotely: > svcadm disable -t akd
> zfs rename <old_snapshot> <new_snapshot> ex: zfs rename pool-0/local/BTZ/btz_backups@.rr-1492dccc-0efa-447c-e4ed-e4d935f16e76-23aef @todelete > svcadm enable akd Then the customer should be able to delete that snapshot (@todelete) via the BUI. NOTE: the usual precautions are to be taken when stopping akd: check cluster status, etc. Some customers require a maintenance window.
Attachments This solution has no attachment |
||||||||||||||||
|