Forwarded to devs "Data Transfer Statistics" not correct after restore or migrator

[nethubonline]

Username:

TITLE

"Data Transfer Statistics" not correct after restore or migrator

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.48
CentOS 7

PROBLEM DESCRIPTION

Backup subscription abc.com in server A, then restore it in server B;
Server B use Migrator to migrate abc.com in server A to server B;

then "Data Transfer Statistics" is not correct

STEPS TO REPRODUCE

By Backup & Restore:

1. fresh install server B
2. Backup abc.com in server A
3. Upload & Restore abc.com in server B
4. Server B > Subscriptions > abc.com > Statistics > "Data Transfer Statistics

By Migrator

1. fresh install server B with migrator extension
2. use migrator to migrate abc.com from server A
3. Server B > Subscriptions > abc.com > Statistics > "Data Transfer Statistics

ACTUAL RESULT

Statistics are different on Server A & B

Server A​	Server B:​

EXPECTED RESULT

Server A & B show same statistics result

ANY ADDITIONAL INFORMATION

All data in AWStats are no problem, only "Data Transfer Statistics" in Plesk

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[IgorG]

Thank you.
The bug PMT-5065 has been created.

 

[nethubonline]

Hi, I found that this problem is not fixed since 2022, may we know if there is any update?

 

[Bitpalast]

I think it is questionable if this is really a bug. It may be a deficiency that stats are not included in migration, but maybe rather a feature request to include them than a bug. There will also be users who want it exactly the way that on a new server traffic statistics start counting from zero and not from what they were on an old server.

 

[nethubonline]

Thanks Bitpalast

I still think it is a bug, because after migration the "Data Transfer Statistics" is not counting from zero, but is weird that include the month of the migrate date and also a month of 2 years.



If "including stats in migration" is a feature that not yet supported, then there should be no any statistics after migration.

 

[Sebahat.hadzhi]

A fix for that issue has not been introduced yet. We understand that the resolution might be taking more than expected and we would like to apologize for the inconvenience. It is on team's agenda, but there are more pressing and critical issues prioritized. Thank you for your patience and understanding in the meantime.