QUESTIONS ANSWERS.pdf
PDF 220 KB Posted
- Attached to
- IHS1471354 - IT System Backup Solution - PAO Federal contract opportunity
- Solicitation number
- RFQ-23-PHX-065
About this file
This document contains questions and answers regarding solicitation number RFQ-23-PHX-065 for an IT system backup solution for the Department of Health and Human Services Indian Health Service Phoenix Area Office. The solution requires backup appliances to be installed at nine sites, with usable storage capacities ranging from 30 to 480 terabytes. Nightly incremental backups are performed with a 60-day retention period. The appliances will be physical devices standalone from production systems, connected via SFP+ to the local area network for backups. Replication from sites to the central DR location in Albuquerque will occur over the internal WAN. All appliances must be of the same brand for interoperability.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Manual_Exhibit_5-5_1A_IEERepresentationForm.pdf | ||
| Pricing Schedule.xlsx | XLSX spreadsheet | |
| Combined Synopsis - Final.pdf | ||
| SOW.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
IHS1471354 - IT System Backup Solution - PAO
No�ce ID: RFQ-23-PHX-065
QUESTIONS & ANSWERS
1. In the SOW, PAO is asking for Hardware and Software with 5 years of support and in the pricing schedule, the descriptions list 3 years of support (36 months). Would PAO like to see year 4 and 5 as options years, or amend the pricing schedule to reflect 5 years, (60 Months) up front?
Answer: 3 years (36 months) Base, and 2 Option Years
2. We believe the capacity for PIMC and ABQ posted in this RFQ to be less than what is required. Our understanding is the software at PIMC and ABQ should both have a qty of 480 instead of qty 240, due to the size of the mission critical data sets that these locations will be backing up. If agreeing to make these changes to the software sizing the affiliated hardware associated to the software would need to change as well. If confirmed that these changes need to be made, the attached Pricing schedule attached would be accurate to reflect these changes.
Answer: PHX Area Office excepts changes to storage requirement, per revised pricing schedule and revised SOW (site storage increase)
PIMC - Appliance with 480TB Usable storage for backups, with SFP+ connections;
The following site will be the DR site for the above locations. This site will host a backup appliance and be the target for replication:
Albuquerque, NM – Appliance with 480TB usable storage for replication, with SFP+ connections or FedRamp approved cloud storage service
3. Please need more clarifica�on per site of quan��es of SFP + connec�ons. For example. Please provide quan�ty and configura�on leter for each of the sites:
4.
i. PAO – Appliance with 60TB Usable storage for backups, with SFP+ connec�ons;
https://sam.gov/opp/832f5e76d27c4c5d9c6ea5fe5c5c4dfb/view
ii. PIMC - Appliance with 480TB Usable storage for backups, with SFP+ connec�ons;
iii. Whiteriver - Appliance with 60TB Usable storage for backups, with SFP+ connec�ons;
iv. Parker - Appliance with 30TB Usable storage for backups, with SFP+ connec�ons;
v. Ft. Yuma - Appliance with 30TB Usable storage for backups, with SFP+ connec�ons;
vi. Hopi - Appliance with 30TB Usable storage for backups, with SFP+ connec�ons;
vii. Ft. Duchesne - Appliance with 30TB Usable storage for backups, with SFP+ connec�ons;
viii. Elko - Appliance with 30TB Usable storage for backups, with SFP+ connec�ons.
ix. The following site will be the DR site for the above loca�ons. This site will host a backup appliance and be the target for replica�on:
x. Albuquerque, NM – Appliance with 480TB usable storage for replica�on, with SFP+ connec�ons or FedRamp approved cloud storage service
Answer: All sites will be confirmation A, which includes 4 copper 10GB, 2 10/25GB SFP and 2 32GB SFP. We would only need the 2 10GB transceivers for these devices, no 25GB or 32GB transceivers required.
5. How many incremental are ran each week, and how long do you retain those?
Answer: Nightly incremental (snapshot) backups are ran on all systems nightly. 60-day retention (we reserve the right to change retention requirements.
6. Do you run weekly fulls, and how long do you keep those?
Answer: One time full as initial baseline. See Incremental Question above for retention.
7. Do you run a monthly backup, and how long do you keep those?
Answer: No
8. Do you do yearly backups, and how long do you keep those?
Answer: No
9. What is the total UNIQUE Front End TB at each of these sites where an appliance is going to be installed?
Answer:
PAO – 24.4TB
PIMC – 18.0TB
Whiteriver – 11.8TB Parker – 6.0TB Ft. Yuma – 7.1TB Hopi – 8.3TB Ft. Duchesne – 3.1TB Elko – 3.0TB
Albuquerque – 30TB
10. What is the annual data growth per year? ie 10%
Answer: 10%
11. Is there migra�on of exis�ng data?
Answer: No migration
12. Is there data in excess of the disk size iden�fied on the appliances in the quote sheet and
SOW?
Answer: No
13. Should there be an expandable cloud datastore price per TB quoted for backup and data storage?
Answer: No
14. Will the appliances quoted be VMWare VMs going into current VMWare clusters as virtual machines, or physical hardware being installed and added to the exis�ng clusters?
Answer: Backup appliances will be standalone physical devices. Only integration into production systems will either be APIs or Proxy VMs
15. Will these be SFP+ connected to exis�ng SAN storage arrays, and if there are SANs, are they part of a global file system?
Answer: This is data backup only. The SFP+ connection is to the LAN for network connectivity
16. Is there an exis�ng VPN and secure network solu�on for connec�vity of the backup systems and other compute resources right now?
Answer: Replication from site to central system is over internal WAN (MPLS, SDWAN, DMVPN)
17. Can the hardware be same size and specs, but different brand name?
Answer: Complete solution should all be of the same brand for cohesion and interoperability between site and central DR location
File details come from the government source that posted it. Updated .