Move deduplication database new drive

Detach the vault, copy the folder, which you initially specified for deduplication database, to the new place, attach the vault, specifying the path and the new path to deduplication database. If you specified the same folder during vault's creation, then leave ".meta", "computers" folders and {guid}_l.fdb, unified_data.ds.* files in their place and move only {guid}_u.db3 to the new location of deduplication database.

Hello,

i have detached the vault, reattached it and i hve not copied the deduplication database.
So the stroage node is recreating the database. But his is very slow.
i have waited 9 hours and the node is not ready. At the moment recreating.
Is this a normal behaviuor?

Server has actual hardware, 12 cores, 60 GB RAM.

We have added SSD because backup speed was "slow".

Regards

Yes, recreation of dedup database is a slow process, not exactly 'normal' , but it's what you can expect. How big is your dedup database?

Old database size was about 80 gigabytes on the old drive.
Now, after 11 hours he has recreated 5 gigabytes on the new drive

i can see, the deduplicated data is consuming 7 TB on our storage, at the moment i can not see the deduplication and compression ratio...

Regards

It will take much time - at least 11*16 hours. If you still have original deduplication database, it would be better to cancel attachment operation, and attach it again, now specifying deduplication database (copied to SSD disk) instead of recreating it.