Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[STaaS] System cleanup #4098

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions user-guide/Advanced_Functionality/Databases/STaaS/STaaS.md
Original file line number Diff line number Diff line change
Expand Up @@ -241,6 +241,10 @@ Before migrating your data over to STaaS, make sure you are aware of the [limita
> [!NOTE]
> In case of issues during or after the migration, revert the `DB.xml` file to its previous state and re-trigger the migration process. If you want to be certain no data inconsistencies are possible, contact [STaaS support](mailto:[email protected]).

## Deleting a system

When [Disconnecting a system from dataminer.services](xref:Disconnecting_from_dataminer.services#permanently-disconnecting-from-dataminerservices) or [Removing a DaaS system](xref:Removing_a_DaaS_system), all STaaS data for that specific system, including backups, will be removed 7 days after the deletion. Upon request, all STaaS data can be recovered within those 7 days.

## Limitations

To **migrate existing data** to STaaS, the following limitations apply:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ To **reconnect your system**, you will need to change the startup type for the D
> - Skyline Communications will no longer be able to provide [Proactive Support](xref:Proactive_Support) for your DMS.
> - All data for the DMS that was saved on dataminer.services will be lost, including shares, settings, and users and permissions configured on dataminer.services.
> - If your DMS consists of one or more fully self-hosted DataMiner Agents, these will continue to work, but you will no longer have access to dataminer.services features.
> - If your DMS uses DataMiner **Storage as a Service** (STaaS), **all data will be permanently lost** and the system will become unusable.
> - If your DMS uses DataMiner **Storage as a Service** (STaaS), **all data will be permanently lost** 7 days after the system is disconnected, and the system will no longer be usable.
> - If you use **DataMiner as a Service** (DaaS), this will **delete your system**. See [Removing a DaaS system](xref:Removing_a_DaaS_system).

To disconnect a DataMiner System from dataminer.services:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ uid: Removing_a_DaaS_system
# Removing a DaaS system

> [!WARNING]
> When you remove a DaaS system, the system will be decommissioned. Within 7 days after you remove the system, you can still recover it by contacting [[email protected]](mailto:[email protected]). However, the cloud identity and shares will be lost, and the system will receive a new cloud identity within your organization upon recovery.
> When you remove a DaaS system, the system will be decommissioned. Within 7 days after you remove the system, you can still recover it by contacting [[email protected]](mailto:[email protected]). However, the cloud identity, shares and all [Storage as a Service (STaaS) data](xref:STaaS) will be lost, and the system will receive a new cloud identity within your organization upon recovery.

1. Make sure you are logged in to dataminer.services with an account that has either the **Admin or Owner** role on organization level, or the **Owner** role on system level.

Expand Down