Is a 3500d history functional?

[cesarsj]

My boss wants us to keep a 10-year track record. I would like to confirm that 3500d (ie 10 years) is functional as I will have to configure the history and trends of major items like this.

Our housekeeper is still disabled. My boss wants me to activate only after placing 3500d of history and trends for all important items. Will this option erase the history of items that I don't want to keep history even with housekeeper disabled, or only after I activate housekeeper?

[cesarsj]

Unfortunately I was left unanswered. My question is unclear or why can't they answer because a history of this size has never been tested?

What do you think about my boss idea? I made a calculation with the maximum values that could put:

We have 8000 items.
Suppose everyone has an interval of 30 seconds and I want to store for 10 years. The result I got was 7 terabytes that would be needed. But I think the system would be very slow.

Don't you think too big a history would hurt the system?

[the.monitor]

I read somewhere that using postgresql you can partition off your history tables - this may assist you with long term retention while keeping your historical data out of the way. The "Mastering Zabbix" book should be able to help with this.