Overriding a Replication Lock

Override the lock for a File Storage replication when performing an action such as an update, move, or deletion.

Required IAM Policy

To override locks, in addition to permissions to manage the replication, you need permissions to manage locks.

To update or delete a replication with a full lock, you must have RESOURCE_LOCK_REMOVE and RESOURCE_LOCK_ADD permissions.

To move a replication with a full lock, you must have RESOURCE_LOCK_REMOVE permission in the source compartment and RESOURCE_LOCK_ADD in the target compartment. If the lock was created by a service, RESOURCE_LOCK_REMOVE and RESOURCE_LOCK_ADD permissions in the compartment of the lock.

  • You can't use the Console to override a File Storage resource lock. Remove the lock, or use the CLI or API.

  • Include the required --is-lock-override parameter with the command to override the lock on a replication. For example:

    oci fs replication update --replication-id <replication_OCID> --is-lock-override true [OPTIONS]

    For more information and examples, see Managing Replications.

    For a complete list of parameters and values for CLI commands, see the CLI Command Reference.

  • Include the required isLockOverride parameter as true with the operation to override the lock on a replication.

    For more information and examples, see Managing Replications.

    For information about using the API and signing requests, see REST API documentation and Security Credentials. For information about SDKs, see SDKs and the CLI.