Home > Storage > PowerScale (Isilon) > Industry Solutions and Verticals > Electronic Design Automation > PowerScale: Best Practices for Semiconductor EDA Design Environments > What to protect?
The table below shows one way to organize the chip design data. It lends itself well in terms of data protection and management:
Data Type | Priority | Protection scheme |
Project directories | Business critical design data | Short-term backup and snapshot, long-term backup |
Scratch directories | Reproducible, transient data | No protection or snapshot |
EDA tools and binaries | Mostly read-only | Weekly backup, no snapshot |
Foundational IP libraries | Mostly read-only | Weekly backup, no snapshot |
Home directories | Business critical user data | Daily backup and snapshot |
Others (QA, test, software repositories…) | Business critical data | Daily backup and snapshot |
Scratch data normally containing data that is transient in nature and used as a dumping ground for large log and results files generated during various design phases.
IT expects that for some reason this data is lost, it should not cause a delay in the design cycle. Therefore, the end-users must be well aware of the IT best practices and data protection policies offered. Even though some end-users want to keep portion of scratch data that can be reproducible but will take very long time to get results. In that situation, short-term snapshots can be configured for scratch areas depending on the business SLAs.