Originally Posted by Sayjac
Clicked mostly to read the comments. DT store said normally within ~ 6 months, ones I've had ordered into the store have been ~3 months. Reading here and elsewhere, seems up to a year acceptable. Personal preference for same date or very close. Topic dates seem fine to me. As for dates comparison to a "server",
lost me.
In server applications, that have multiple hard drives and run in a raid5 configuration you would want different date codes for each hard drive.
Lets say you run a raid5 1TB hard drive configuration with qty4 1TB (storage of 4TB) and qty1 ITB (checksum). Data is spread (stripped/stored) across all qty 4 1TB and the checksum is in the remaining 1TB hard drive. If you have a single HD failure, you can easily restore that HD via the three HDs and the checksum HD. That bad HD has a specific date code or lot number.
"The take-away"
If you have two HDs with the same BAD date code, you sustainability increase the risk of a possible dual simultaneous HD failure. There is good chance the other HD may fail soon. This is a non-recoverable HD restoration.Two failed HDs cannot be restored in a raid 5 configuration.
An example:
http://generaltire.custhelp.com/app/answers/detail/a_id/841
If you have qty 4 with 1815, you will be subject to a recall.
Tires produced between May 3 and May 16, 2015 are covered by this voluntary recall program.
If you have qty 1 with 1815 and qty 3 other than 1815, you will have only one tire subject to a recall.
Tires produced between May 3 and May 16, 2015 are covered by this voluntary recall program.