system ‑clearLossOfSync

Deletes all clones that have lost synchronization with their parent volumes due to insufficient space. Once a clone has lost synchronization, data integrity cannot be guaranteed. The only option is to delete the clones.

SYNOPSIS

system ‑clearLossOfSync 

   [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}]
   [{‑outputformat | ‑o} { text | xml }]
   [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]

DESCRIPTION

The Oracle FS System utilizes a copy-on-write mechanism to maintain integrity between the source logical volumes and their clones. Synchronization can be lost when the amount of data that is stored in the clone repository has reached the maximum capacity, and the changes that are made to the clones cannot be recorded. The Oracle FS System places the clones offline to prevent access and the Oracle FS System generates a system alert. The Oracle FS System also generates the following types of warnings when the clone repository is within 80% of the maximum allocated capacity:

Sends email notifications to the subscribers of the Call‑Home service.
Displays system alerts and highlights the warning conditions in the Oracle FS System Manager GUI.
Sends email notifications to the subscribers of the system event notification service.
Posts system events to the system event log.

If you receive any of the above alerts or warnings, run one of the following commands to increase the repository size:

For SAN LUNs: lun ‑modify ‑lun lun-id-or-fqn ‑repositoryPercentage capacity-percentage
For NAS filesystems: filesystem ‑modify ‑filesystem filesystem-id-or-fqn ‑dataTier \( -tier tier-id-or-fqn -repositoryPercentage capacity-percentage\) -metaDataTier meta-data-tier-id-or-fqn -metaDataRepositoryPercentage capacity-percentage

Note: The Oracle FS System uses thin provisioning for clones. When creating a given source volume, allocate at least 200 percent of the source capacity for the repository if you expect the clones to be frequently updated by users or applications. If you observe that the clones of a specific volume are frequently losing synchronization, it is because the rate that the data changes combined with the amount of data that is changing causes the clone repository to run out of space faster than anticipated.

If any repository has reached the maximum capacity that has been allocated for the repository, run the system ‑clearLossOfSync command to delete any corrupted clones that might exist on the Oracle FS System. The source volumes are unaffected by running this command.

Note: Only administrators with primary administrator, admin1, and admin2 roles are authorized to run the system ‑clearLossOfSync command.

EXAMPLE

Task

Remove compromised clones from the Oracle FS System.

Parameters

None

$ fscli system -clearLossOfSync