Node disqualified, best actions

[Alexey]

Hello @ByteBlitz,
Welcome to the forum!

@ByteBlitz

by using the same identity for the new node as the old.

ouch…
This is a wrong move. The disqualification is permanent and not reversible.
I would assume that you stopped the clone already.

1. Stop both nodes.
2. Move blobs folder from the clone to the original node data location with joining data with the similar blobs, but without a replace of files so, it should move only new files.
3. Delete the second node completely.
4. Start the first one (we will hope that it will survive)
5. Generate a new identity for the second node (not copy!), sign it with a new authorization token and run the second node with its own identity (not cloned) and clean storage.

@ByteBlitz

Will all data from EU1 be garbage collected and I will get space back on my (old) node?

no. You need to do it manually, for example, using this way: How To Forget Untrusted Satellites.
I would recommend to add the EU1 satelliteID with its host and port to the untrusted list for the first node, as described in this article.

@ByteBlitz

how to gracefully exit the node and how long will it typically take to exit?

It’s not needed. If your first node didn’t lost the remained data, it can work, but without a EU1 satellite is now on.
However, you may do a Graceful Exit, it will take exact 30 days and all that time the node must be online:

Graceful Exit Guide (new procedure as of 2023-10-?)

Warning: Read this carefully before you start Please read the following information carefully and ask any questions your might have before executing graceful exit. Once graceful exit is started there is currently no way to stop or cancel it. Think about the consequences twice before you call it. Requirements: Storage node has joined the network more than 15 months ago (requirement temporarily reduced to 6 months). Storage node is healthy and hasn’t lost any significant amount of data. Disqua…