Achiziție - Servere și sisteme de stocare (perioada 2024-2025)
Achiziție Agentia Servicii Publice
Informație generală
Servere și sisteme de stocare (perioada 2024-2025)
Surse de finanțare
suma planificată 43,450,153.71 MDL
Detalii achiziție
Documente
Persoană de contact
Clarificări
Pentru a evalua corect datele despre performanta sistemelor propuse, propunem spre acceptare:
1. Rezultate testelor de performanta sunt acceptate numai din partea producătorului, cu indicația metodologiei/instrumentelor de calcul performantei
2. Autoritatea is rezerva dreptul de a cere prezentarea metodologiei/instrumentelor de calcul a performantei de către producător ca calcularea a fost făcută exact pentru modelul propus in licitație, nu pentru seria de modele in general
3. Ofertantul accepta, ca pentru a proteja investitiile/alegerea corecta, autoritatea isi rezerva dreptul de a întoarce/returna echipamente livrate, daca in decurs de 30 zile din ziua livrarii au fost depistate necorespunderea cerințelor, inclusiv cele de performanta, fără orice consecințe financiare pentru Organizator.
Cerințele tehnice minime și obligatorii specificate în documentația de atribuire rămân nemodificate.
1. Acceptarea și validarea performanței echipamentelor se va face conform specificațiilor și cerințelor tehnice publicate, inclusiv prin furnizarea rezultatelor testelor de performanță, realizate cu instrumente standardizate.
2. Nu se vor introduce cerințe suplimentare privind metodologia de testare sau acceptarea exclusivă a rezultatelor furnizate de producător.
3. Condițiile de livrare și recepție sunt reglementate conform cadrului legal aplicabil achizițiilor publice și nu vor fi modificate.
Reieșind din experiența globala si RM, ca durata exploatării a dispozitivelor de păstrare date (storage) este cea mai lunga, si pentru a evalua corect TCO, cerem pentru soluții sa fie incluse in pret toate licențe funcționale/limitări de extindere/etc. daca nu sunt soluții cu licențe „all inclusive”. Iar daca licențe sunt limitate in timp, atunci trebuie sa fie incluse in preț cel puțin pentru 10-12 ani (sau alta perioada la discreția organizatorului).
Cerințele minime și obligatorii specificate în documentația de atribuire rămân nemodificate.
Toate licențele necesare pentru funcționarea și administrarea sistemului de stocare, inclusiv actualizările și patch-urile periodice, trebuie să fie incluse în ofertă și furnizate pe o bază perpetuă, valabile pentru întreaga durată de viață a sistemului. Nu se acceptă licențe cu limitare de timp sau necesitatea unor costuri suplimentare ulterioare.
Taking into account that you requested SSDs as storage modules, please accept also superior storage modules, like NVMe, that are with advanced functions like internal NVMe tiering of data in order to achieve the best performance and best response time for both read and write operations that are performed at the NVMe level or NVMe level encryption or the possibility to detect ransomware attacks
Also by accepting this superior technology, NVMe, you will not have any impact in compatibility or performance for the applications that you will run on a storage that uses NVMe modules instead of SAS SSDs.
The protocol that the disk uses (SAS or SATA or NVMe) is only at storage hardware physical level and is not visible and doesn’t have any impact at LUN / volume / pool level, nor at the data that are stored on this (like operating system, databases, applications, virtual environment, etc).
NVMe drives use superior technology providing better durability and reliability, especially under heavy use (like the workload profile asked in this RFP). In all studies, NVMe demonstrated significantly lower failure rates compared to SAS SSDs under continuous heavy loads
The technical requirements specified in the procurement documentation represent the minimum and mandatory criteria. Therefore, modifications or deviations from these requirements are not accepted.
For Lot 3, only Enterprise-grade SAS SSDs utilizing TLC or eTLC technology are eligible, as explicitly stated in the specifications.
For Lot 4, the requirement is for Enterprise-grade NVMe/Flash SSDs, in line with the published criteria.
Any alternative proposals that do not comply with these specific requirements cannot be accepted.
Taking into account that all storage vendors recommend that for very IO intensive workloads (like in this case when 300.000 IOPS are needed for the storage) not to activate / use deduplication function because it induces a very high CPU utilisation (load that can’t be really estimated because of data pattern by a performance sizing tool) . This high CPU utilisation is generated when data is deduplicated (when is written to disks) and then re-hidratate, when data needs to be read and send to host.
Main disatvantages of deduplication:
Performance Overhead -> Deduplication processes can require significant CPU and memory resources, leading to potential performance slowdowns during data writes and reads.
Limited Use Cases: It may not be effective for all types of data. For example, highly dynamic data with frequent changes can limit deduplication effectiveness and reduce compression ratios.
Taking all this arguments into consideration, please accept that the performance should be done only with compression active.
The technical specifications clearly state that the required performance of 300,000 IOPS must be achieved with inline data reduction, including both deduplication and compression.
These requirements represent minimum and mandatory criteria, ensuring the intended efficiency and storage optimization. Therefore, modifications or exclusions of deduplication from the inline data reduction process are not accepted.
All submitted solutions must comply with the stated requirements in full.
Taking into account that all storage vendors recommend that for very IO intensive workloads (like in this case when 500.000 IOPS are needed for the storage) not to activate / use deduplication function because it induces a very high CPU utilisation (load that can’t be really estimated because of data pattern by a performance sizing tool) . This high CPU utilisation is generated when data is deduplicated (when is written to disks) and then re-hidratate, when data needs to be read and send to host.
Main disatvantages of deduplication:
- Performance Overhead -> Deduplication processes can require significant CPU and memory resources, leading to potential performance slowdowns during data writes and reads.
- Limited Use Cases: It may not be effective for all types of data. For example, highly dynamic data with frequent changes can limit deduplication effectiveness and reduce compression ratios.
Taking all this arguments into consideration, please accept that the performance should be done only with compression active (compression should be done only by dedicated harware components).
The requirement specifies that the minimum performance of 500,000 IOPS must be achieved with inline data reduction, including both deduplication and compression.
These specifications are mandatory and cannot be modified, as they ensure compliance with the project’s objectives regarding storage efficiency and optimization.
Proposed solutions must fully meet these requirements without alterations.
Taking into consideration that the requested storage equipment is block only (protocols requested are FibreChannel or iSCSI and also the requested connection is Fibre Channel 32 Gbps only), please accept also storage equipments that support only block storage protocols (iSCSI and FC) for performance monitoring and prioritization mechanism for Storage QoS.
The published technical specifications clearly state that the storage system must provide deduplication functionality at both the block level (iSCSI/FC LUN) and file level. These requirements are mandatory and cannot be modified.
The requested storage solutions must fully comply with the specified deduplication and compression capabilities, including support for both block and file-level storage as outlined in the tender documentation.
Taking into account that all major storage vendors use global deduplication in oder to achive the best data deduplication efficiency (using a single deduplication table for the entire system, give significantly better deduplication ratio and also the performance for the entire system is not so havely impacted compared with having one deduplication table for each volume of the storage), please accept that the proposed storage solution should have deduplication globally across the system.
Also having in mind that for deduplication at volume level, the performance of the entire system induces a huge performance penalty because for each volume of the system needs to have an dedicated deduplication table, which is not shared with the other volumes from the storage equipment, which results also into a very low deduplication efficiency (at the system level).
The technical specifications clearly state that deduplication must operate both at the volume level and globally across the system, ensuring optimal storage efficiency. This requirement is mandatory and cannot be modified.
The proposed storage solution must fully comply with these specifications by supporting both volume-level and global deduplication, as outlined in the tender documentation.
Taking into account that each storage vendor let’s the option active / disable storage efficiency features, recommend that this features not to be used for very IO intesive workloads (like in this case when 300.000 IOPS or 500.000 IOPS are needed for the storages). Please accept storage equipments for which we can activate / deactivate the deduplication features in order to achieve best performance and best response times for your applications. As in all best practices, deduplication is not recommended for IO intensive workloads because it induces an high utilisation of the CPU when data is deduplicated (when is written to disks) and then re-hidratate, when data need to be read and send to host
The technical specifications explicitly require that deduplication must remain continuously active and cannot be disabled or bypassed by system administrators or any other means to ensure consistent storage efficiency and data integrity.
Therefore, the proposed storage solution must fully comply with this requirement, and solutions that allow deduplication to be disabled do not meet the mandatory specifications.
Taking into consideration that snapshots are used only for temporary recovery of data (not as backup solution) as the snapshots are depended on the source volumes (if the source volume will be deleted then all snapshots will not be available anymore) also as the source data changes, old snapshots retain the original data, which can lead to fragmentation and exponential growth in the occupied space, and a large number of snapshots kept over the long term can end up occupying as much space as the original data or even more. Each snapshot creates a reference to the source data. As the number of snapshots increases, the system must manage more reference points and check which version the data is in.
Having all this aspects in mind, please reconsider the minimum number of snapshots and accept storage solutions from well consecrated storage vendors, like DELL, IBM, NetApp, that have minimum 250 snapshots per volume and supports minimum 10.000 snapshots per system.
The requirement specifies that the system must support a minimum of 365 snapshots per shared volume to ensure long-term operational and recovery needs.
While we acknowledge that some enterprise storage vendors (DELL, IBM, NetApp) may have different snapshot configurations, the stated requirement remains mandatory. The ability to support a minimum of 365 snapshots per volume is essential for meeting operational flexibility required by Agency duet o operation of national importancy wide number of the Registers, long-term retention policies, and compliance needs.
Therefore, the proposed storage solution must comply with this specification, and solutions offering a lower number of snapshots per volume do not meet the required criteria.
Requirement (Lot 4): “Audit and compliance:
- The system must provide audit logs and reports detailing encryption operations, key management activities, and access attempts, ensuring transparency and regulatory compliance.
- Logs should be exportable and compatible with industry-standard security information and event management (SIEM) systems.”
Clarification question:
Please let us know if this feature needs to be included in the offer or needs to be supported via feature upgrades?
The requirement specifies that the system must provide audit logs and reports detailing encryption operations, key management activities, and access attempts, ensuring transparency and regulatory compliance. Additionally, logs must be exportable and compatible with industry-standard SIEM systems.
This feature must be included in the offered solution and should not rely on future feature upgrades. The audit and compliance functionalities are essential for meeting security, regulatory, and operational transparency requirements and must be fully available at the time of deployment.
Any proposed solution must fully comply with these specifications to ensure immediate compatibility with security monitoring and compliance frameworks.
Requirement (Lot 4): “Key backup and recovery:
- The system must include mechanisms for secure backup and recovery of encryption keys, supporting integration with external key management systems (KMS) compliant with KMIP (Key Management Interoperability Protocol) standards.
- Key rotation and lifecycle management should be automated and configurable to align with organizational policies and compliance requirements.”
Clarification question:
Please let us know if this feature needs to be included in the offer or needs to be supported via feature upgrades?
The requirement clearly states that the system must include mechanisms for secure backup and recovery of encryption keys and support integration with external Key Management Systems (KMS) compliant with KMIP standards. Additionally, key rotation and lifecycle management must be automated and configurable to meet organizational policies and compliance standards.
This feature must be included in the offered solution and should not rely on future feature upgrades. Key backup and recovery are essential components of encryption security, ensuring compliance with regulatory requirements and protecting critical data integrity.
The proposed solution must fully comply with these specifications at the time of deployment to ensure seamless security management and integration with external KMS.