...
| Page Properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
Resources & Remarks Modification History
|
| Excerpt |
|---|
Deletes all data belonging to a tenant from the core system, including all objects in repository, database, elasticsearch, audit entries and config files. |
...
This command may be useful if all data of a tenant should be deleted. If you are going to use this Before using this command, you should consider ensure that the tenant is already disabled for user login, to prevent any unexpected data manipulations while the deletion process is running. Be Be careful, this operation cannot be undone , nor is there any and there is no automatic data backup.
...
Even objects under retention will be deleted. However, if binary content files are protected by an archive-internal retention, they cannot be deleted via this command.
While the command continuously runs, the deletion of DMS objects is stepwise performed. Each day between the first object creation date and the current day separately. Each date is separately processed. Then again, each day is splitted split in a variable number of time periods, so such that the amount of objects to delete be deleted in each period is approximately equal to the number of fetch-size. Then for For each period, the command is going tofollows this procedure:
...
- Processing of all current
...
- object versions:
- Deleting each repository item
...
- , i.e., binary content files. (individual requests)
- Deleting the objects in the Elasticsearch index. (batch request)
- Deleting all database rows. (batch request)
...
- Processing of all old
...
- versions of DMS objects:
- Deleting each repository item
...
- , i.e., binary content files. (individual requests)
...
- Deleting all database rows. (batch request)
After finishing all time periods for one of a day are finished, all audit entires are going to be deletedentries of this day are deleted. Then, the procedure is repeated for the next day until the current date has been processed. Depending on the number of objects for the tenant, this process can take a long time. While running the task, the process progress is continuously displayed including an estimated completion time.
After handling processing all days, as a last step, the tenants tenant's configuration is going to be deleted.
The following parameters can be given to the maintain-tenant-data-delete command:
| Parameter | Argument Type | Description | Required | Default | Example |
|---|---|---|---|---|---|
--tenant <arg> | string | Tenant for which all data should be deleted. | yes | - | --tenant default |
| string | Target directory for result log. | no | - | --target-directory C:\Users\myusername\ymtenantdeletionlog |
--fetch-size <arg> | int | Fetch size, used to split days in time periods. Each period contains approximate contains approximately as many elements as the specified by The value must be at least 100 and not bigger than 10000. | no | 1000 | --fetch-size 500 |
--what-if | boolean | Setting this flag will prevent only simulate this command, by counting the execution of the deletion. The process will be simulated in order to count all documents that would be deleted without this flag. | no | false | --what-if |
--skip-confirmation | boolean | Setting this flag will skip the initial warning, that all data is going to be deleted. | no | false | --skip-confirmation |
...
In the following example, all objects of tenant default is going to will be deleted. Each day is splitted split in time periods which contains approximate approximately 500 objects.
| Code Block | ||||
|---|---|---|---|---|
| ||||
Lt. Commander>maintain-tenant-data-delete --tenant default --fetch-size 500 Running tenant delete job for 'default' |
...