MODIFICATION
70 -- DUAL BACKUP SOLUTION
- Notice Date
- 1/20/2015
- Notice Type
- Modification/Amendment
- NAICS
- 334112
— Computer Storage Device Manufacturing
- Contracting Office
- 53560 Hull Street Bldg A33 Rm 1602W, San Diego CA 92152-5001
- ZIP Code
- 92152-5001
- Solicitation Number
- N66001-15-T-7415
- Response Due
- 1/21/2015
- Archive Date
- 2/20/2015
- Point of Contact
- Point of Contact - Shawna Nevins, Contract Specialist, 619-553-4507; BELINDA SANTOS, Contracting Officer, 619-553-4502
- E-Mail Address
-
Contract Specialist
(shawna.nevins@navy.mil)
- Small Business Set-Aside
- Total Small Business
- Description
- AMENDMENT 0004 EFFECTIVE 01/20/2015 THE PURPOSE OF THIS AMENDMENT IS TO: 1. TO INCORPORATE QUESTIONS ASKED AND ANSWERED AS FOLLOWS: Question 9: What is the need or usage of PPD? Answer 9: This is what stated is in the requirements. Both methods have their own advantages and disadvantages. One advantage of PPD is that because the backup is straightforward, it takes less time. A disadvantage of PPD, however, is that the storage administrator must have enough space to store the full backup somewhere until the duplicate data is removed. In case this adds time to the process and uses a lot more storage disk space. Question 10: Is there a reason or requirement to have the full data (redundant data) stored for later retrieval? Answer 10: Yes that is the requirement. Inline deduplication reduces data while it is being sent to the backup device while post- process backs up data first, and then reduces it. Both methods have advantages and disadvantages. Post-processing backs up data faster and reduces the backup window, but requires more disk because backup data is temporarily stored... As we know, with Post-Process Deduplication: A block of data comes into the appliance and is written to storage entirely. Then a separate process reads the block and checks it for redundancy. If it has been processed before (is considered to be a duplicate), it is deleted and replaced with a reference. If the block does not have matches, no changes are made. This method shortens time of data transfer from the source to storage but it requires more free space on a server disk and a lot more I/O than in-line. In-line deduplication: It can be performed on the client side or when data is being transferred from the source to server. A block of data comes into the appliance, which analyses if that block has been processed before. If so, it throws away the redundant block and writes a reference to it. If the block of data is unique, the appliance writes it to the storage. Thus, data block analysis is initiated before it is written. This method of deduplication performs most of the work in RAM, which minimizes I/O overhead and provides disk space savings. Nevertheless, despite its resource-intensity and possible delays, in-line method increases efficiency of global deduplication since immediate processing of data stream coming from several sources allows eliminating duplicates on the fly. Question 11: Will it satisfy to have just In-Line Deduplication on the BackUp Device? Answer 11: In-line deduplication on backup solution is acceptable. There is also a solution that we use for back ups from a central repository to a DR site that stores the data as it comes in and it is stored to both sites simultaneously. This is used in worse case scenarios where having no single point of failure with a full redundant HA Failover back up solution is a must and having data available at all times in case of outages, (Force Majeure) with a back up solution that if one site goes down, the other site will have the data and it is readily accessible. No down time to bring data back up and online. Question 12: Will you be interested in knowing more about our HA Back up solution? Answer 12: Not at this time. Back to PPD and Inline Deduplication. Other advantages is that Inline deduplication recognizes redundant data as it comes in from several different backup data streams and won't forward the full block to target media if it knows it must be duplicated. Performance will usually improve over time as the data deduplication product becomes used to the data set it has to work with and data reduction ratios will improve toward an optimal maximum. Post-process deduplication also looks for duplicated data blocks and replaces them with a pointer to the first iteration of that block. But unlike inline deduplication, post-process deduplication doesn't begin processing backup data until after it has all arrived at the backup target. So, if you regularly back up large amounts of redundant data, you'll be using resources to pump it all into the backup target unreduced. This can cause a head ache with bottlenecking. The primary requirement of post-process data deduplication is that there's enough disk capacity to store the largest potential backup your likely to carry out. If you want to minimize backup times, post-process deduplication could be your best bet. Post-process deduplication has no impact on the length of the backup window. Backup operations are completely unaffected, with data deduplication carried out once the data set is on the target disk. However, if you need to replicate deduped data to an offsite location for disaster recovery (DR), it will work out better to go with inline deduplication instead of sending un- deduplicated data across the (WAN) and then dealing with it post-process. Impact of data deduplication on tape backups Post-process deduplication can be the better choice when you plan to copy data from disk to tape soon after backup. For that reason, if you want to copy to tape soon after backup, it can be done more easily if you have the un-deduplicated data set to hand, as you would in a post-process deduplication scenario. As I perused the Q&A I found that it is your intent to move away from back up to tape. Question 13: The master is the one that contains your Netbackup Database correct? Answer 13: Yes. Question 14: Are you using the Media Server to manage backups and restores of clients and the media server's local data to direct attached or SAN-attached storage (tape/disk)? Answer 14: Yes Question 15: So the SAN Media Server provides all the functionality of a Media Server without the ability to backup and restore data from remote clients. The SAN Media Server is designed for Client - any system that requires protection. The NetBackup client sends and receives data across the (LAN) to and from a NetBackup Master/Media Server. Since the master is the one that contains your Netbackup Database. So it needs lots of disk space and some power. It has the database that runs the schedules and keeps track of tape drives and other backup devices. It also keeps track of media servers correct? Answer 15: There is no SAN Media Server just Netbackup Master and Media servers. Question 16: The media server (which a master can also be a media server) Currently is all backups being done on the tape library? Since the media server has the ability to talk to the clients and gets the data from them and put the info onto the backup device. It also has the ability to send data to the master server and info on the files that it is backing up so the master can add that info to the database. Does this have a direct attached (JBOD) for storage at the Master / Media Server? Or is all the data that's being backed up go straight to the tape library? Are you doing deduplication here at the (NetBackup Master/Media server utilizing Symantec V-Ray technology? Answer 16: Current backups are done on tape and disk (virtual tape library). The virtual tape library supports deduplication. If the deduplication is being done at the NetBackup Master/Media server, it's for this reason also that if your environment contains a mix of disk and tape, post-process deduplication may be better suited to your purposes because there's less disruption to backup and archiving processes from a data deduplication method that carries out its work as a discrete stage rather than incorporating it with backups. But at the same time this method turns out to be absolutely ineffective if rapid data recovery is needed because when a client addresses storage, the system can be busy with deduplication of the next portion of data. Type of the data being processed also substantially influences the effectiveness of Post-Process Deduplication. Let's examine dedupe for a backup application making everyday shots of VM image. Obviously, there will be only a slight difference between such shots as they mostly contain OS and applications' files. The post-process dedupe will be able to figure out whether they are duplicates only when the shots are written to the storage, while in-line dedupe will determine redundancies before shots are stored to the backup. The more node-clients need to be processed, the less effective post-process dedupe appears to be, while in-line on the contrary shows increasing effectiveness. With the intentions of going away from a tape back up library it makes more sense to have a back up solution that does inline deduplication at the back up appliance with removal of duplicate data blocks before it is backed up. For that reason, data deduplication's key challenge is its processing overhead, especially in the case of large data sets. So in my best assessment, I think that the Inline Data Deduplication will be best for your back up approach. I found that The Symantec OpenStorage (OST) Technology API allows intelligent storage devices to interface to NetBackup Media Servers. Then we would provide a software plug-in which is installed on each NetBackup Media Server that is connected to the storage device. OST functionality is available on almost all our supported NetBackup Media Server platforms that we currently use today. With regards to the NetBack Up Master/Media server, the SAN clients can be used with the deduplication option; however, as you know the deduplication must occur on the media server, not the client. We would configure the media server to be both a deduplication storage server (or load balancing server) and an FT media server. The SAN client backups are then sent over the SAN to the deduplication server/FT media server host. At that media server, the backup stream is deduplicated. I believe this is how the SAN client and NetBackup Deduplication are being done. So the client is not enabled for deduplication on the SAN Clients. The data processing for deduplication is incompatible with the high-speed transport method of Fibre Transport. Client-side deduplication relies on two-way communication over the LAN with the media server. A SAN client streams the data to the FT media server at a high rate over the SAN where the deduplication is done on the media server before it hits the SAN. Question 17: Is this correct? Answer 17: Yes. Question 18: Is this what you are currently doing for back ups with NetBackUp? Answer 18: Yes. Question 19: Moving forward where will the Deduplication be done? On the Master/Media server (SAN) or will this all be done on the new back up solution? Answer 19: backup solution. This is where I would like to get some insight and feed back on where you want the deduplication to be done. Question 20: Are you wanting to have deduplication done at the backup storage device? Just wondering where and by which process they deduplication will be done at the Media Server or the new back up solution? Answer 20: deduplication will be done on backup solution. CLOSING DATE REMAINS UNCHANGED. **************************************************************** AMENDMENT 0003 EFFECTIVE 01/14/2015 THE PURPOSE OF THIS AMENDMENT IS TO: 1. TO INCORPORATE QUESTIONS ASKED AND ANSWERED AS FOLLOWS: QUESTION 7: If there exists a NetBackup tape solution why is it necessary to provide additional hardware for a NetBackup Master/Media server on the RFI? A disk based storage solution would just be inserted into the existing NetBackup infrastructure. Can you please expand on the NetBackup master/media server requirement? ANSWER 7: The intent is to move away from a tape based backup system, therefore and Netbackup Master/Server capability is required at both locations. QUESTION 8: Is there a requirement for implementation support from the manufacturer or solution provider to install and configure the duel backup solution? If so, what level of effort/support is required? ANSWER 8: Installation will include support necessary to incorporate backup solution into existing Netbackup environment. CLOSING DATE REMAINS UNCHANGED. **************************************************************** AMENDMENT 0002 EFFECTIVE 01/07/2015 THE PURPOSE OF THIS AMENDMENT IS TO: 1. TO INCORPORATE QUESTIONS ASKED AND ANSWERED AS FOLLOWS: QUESTION 6. Last question; what is the current tape solution in place? Connection? ANSWER 6. Current tape solution is a Storagetek SL500 with 4 LTO5 tape drives fibre channel attached. CLOSING DATE REMAINS UNCHANGED. **************************************************************** AMENDMENT 0001 EFFECTIVE 01/06/2015 THE PURPOSE OF THIS MODIFICATION IS TO: 1. CORRECT THE ANNOUNCEMENT NUMBER IN THE SECOND PARAGRAPH, THE ANNOUNCEMENT NUMBER IS N66001-15-T-7415. 2. TO INCORPORATE QUESTIONS ASKED AND ANSWERED AS FOLLOWS: QUESTION 1. When stating Dual Back Up Solution; does this mean a Dual Node Back up Appliance? Meaning 1 back up appliance in two locations each location having a Dual Back up appliance for no single point of failure at 1 site for each? or does Dual Back Up Solution mean, 1 back up solution at two different sites? ANSWER 1. One backup solution in 2 different locations. QUESTION 2. With the initial specified requirement stating 76TB useable storage space upgradeable to at least 144TB with just the addition of disk storage; does this mean the requirement ask for a back up solution that includes the back up software license to cover 144TB storage initially with just the addition of "disk storage to 144TB" from 76TB useable storage space as the upgrade? ANSWER 2. License only needs to cover initial storage provided, a minimum of 76TBs. QUESTION 3. When stating replication compression between back up storage arrays; does this mean that one back up solution will be a central repository and the second back up solution will be an offsite DR Back up? Then the data from the central repository back up array will then need to have data replication compression between the central repository back up solution compressing the data to the Offsite Disaster Recovery Back up Solution? ANSWER 3. One site will be primary and replication data between the 2 site needs to be compressed. Backup data should be recoverable from either site, both site need to be media servers QUESTION 4. Support for writing to tape; does this mean that there is already a current tape loader appliance in place at 1 or both facilities to connect to the back up solutions? Or does the back up solutions need to have a write to tape included in the solution proposed? ANSWER 4. Tape solution is already in place. QUESTION 5. If there is a requirement needed for a tape loader for tape back up; what is the desired capacity per tape wanted? And how many tape drives? And what is the total tape cartridge capacity wanted in a tape loader for tape back up? ANSWER 5. None required. CLOSING DATE REMAINS UNCHANGED. **************************************************************** This is a SSC Pacific combined synopsis/solicitation for commercial items prepared in accordance with Federal Acquisition Regulation (FAR) Part 12, Acquisition of Commercial Items and FAR Part 13, Simplified Acquisition Procedures. This announcement constitutes only the solicitation. Competitive quotes are being requested under N66001-15-T-7418. This requirement is set-aside for small businesses, NAICS code is 334112 and the size standard is 1000 Employees. Item 0001 DUAL BACKUP SOLUTION **SEE ATTACHED MINIMUM SPECIFICATIONS QTY: 2 EA Item 0002 NON-RETURNABLE DISK FEE **SEE ATTACHED MINIMUM SPECIFICATIONS QTY: 1 LOT Note: UID Labels are required on all equipment with a unit cost of $5,000 or more per DFARS 252-211-7003, Item Identification & Valuation. If there is a cost for the UID Label, please quote a separate line item. "The statement below applies to CLINS ------ To be considered for award, the offeror certifies that the product(s) being offered is an original, new and Trade Agreements Act (TAA) compliant product, and that the subject products are eligible for all manufacturer warranties and other ancillary services or options provided by the manufacturer. Offeror further certifies that it is authorized by the manufacturer to sell the products that are the subject of this action in the US (i.e., that the products are TAA compliant and that the offeror is authorized to sell them in the US). Offerors are required to submit documentation with the offer identifying its supply chain for the product, and certifying that all products are new, TAA compliant, and in their original packaging. By making an offer, offeror also consents to no cost cancellation of the non-compliant awarded items if, upon inspection after delivery, any products provided are not recognized or acknowledged by the manufacturer as new and original products that are eligible for warranties and all other ancillary services or options provided by the manufacturer or that offeror was not authorized by the manufacturer to sell the product in the US, or that the product is in some manner not TAA compliant. " Basis for award: The government anticipates awarding a firm-fixed price purchase order and it will be based on the lowest technically acceptable quote. Quotes will be evaluated on an "all or none" basis. This solicitation document incorporates provisions and clauses in effect through Federal Acquisition Circular Fac 2005-78, Effective 26 Dec 2014 and Defense Federal Acquisition Regulation Supplement (DFARS), DPN 20141216 (Effective 16 Dec 2014) Edition. It is the responsibility of the contractor to be familiar with the applicable clauses and provisions. The clauses can be accessed in full text at www.farsite.hill.af.mil. FAR Clause 52.212-1, Instructions to Offerors Commercial and 52.212-4, Contract Terms and Conditions Commercial Items, incorporated by reference, applies to this acquisition. FAR Clause 52.212-3, Offeror Representations and Certifications -- Commercial Items and DFAR S 252.212-7000 Offeror Representations and Certifications Commercial Item applies to this acquisition in e-Commerce. FAR Clause 52.212-2, Evaluation Commercial Items FAR Clause 52.212-5-Contract Terms and Conditions Required to Implement Statutes or Executive Orders -- Commercial Items applies to acquisition and includes: 52.204-2, Security Requirements 52.209-6, Protecting the Government's Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment. (Dec 2010) (31 U.S.C. 6101 note) 52.214-3, Amendments to Invitations for Bids 52.214-4, False Statements and Bids 52.214-5, Submission of Bids 52.214-6, Explanation to Prospective Bidders 52.214-7, Late Submissions, Modifications, and Withdrawals of Bids. 52.219-6, Notice of Total Small Business Set-Aside 52.222-50, Combating Trafficking in Persons (22 U.S.C. 7104(g)) 52.222-3, Convict LaborE.O. 11755) 52.222-19, Child LaborCooperation with Authorities and Remedies (E.O. 13126) 52.222-21, Prohibition of Segregated Facilities (Feb 1999) 52.222-26, Equal Opportunity(E.O. 11246) 52.222-35, Equal Opportunity for Veterans 52.222-36, Affirmative Action for Workers with Disabilities (Oct 2010) (29 U.S.C. 793). 52.222-37, Employment Reports on Veterans 52.225-13, Restrictions on Certain Foreign Purchases (E.O.'s, proclamations, and statutes administered by the Office of Foreign Assets Control of the Department of the Treasury), 52.232-33, Payment by Electronic Funds TransferCentral Contractor Registration (31 U.S.C. 3332) 52.233-3, Protest After Award (31 U.S.C. 3553) 52.233-4, Applicable Law for Breach of Contract Claim (Pub. L. 108-77, 108-78) DFARS Clause 252-204-7001, Commercial and Government Entity (CAGE) Code Reporting, DFAR 252.211-7003, Unit Identification and Valuation (applies to items over 5k). 52.204-6, Data Universal Numbering System (DUNS). This RFQ closes on January 21, 2015 at 10:00 AM, Pacific Time. All questions and quotes must be uploaded on the SPAWAR e-commerce website at https://e-commerce.sscno.nmci.navy.mil, under SSC Pacific/Simplified Acquisitions/N66001-15-T-7415. The point of contact for this solicitation is Shawna Nevins at shawna.nevins@navy.mil. Please include RFQ N66001-15-T-7415 on all inquiries. All responding vendors must have a completed registration in the System for Award Management (SAM) website prior to award of contract. Information can be found at https://www.sam.gov/.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/be204ef7aaf5c88b319498890c2b23b0)
- Record
- SN03620050-W 20150122/150120234443-be204ef7aaf5c88b319498890c2b23b0 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |