Calling all C++/COM experts: I need this already mostly completed VSS project completed to my needs.

(Runtime and executable) [login to view URL] (source link) [login to view URL] Above you will find a link to a project that is very well written already in pure unmanaged C++. (opens in Visual studio 2010) Its main purpose is to create a shadow copy (point in time snapshot) of a disk/volume utilizing Windows VSS (Volume Shadow Service) and then you are able to copy the files (including those locked by the OS) to the destination of your choice. (IE , external backup drive) Use the 1.0.0.0 release. x86 and x64 projects will need to be done both the same. but start with the x64 if possible. It can also do Incremental backups of this data, which means that after the initial backup is created, it can snapshot again and only backup changes that have occurred since the last full backup. **With that said, the project is not completed** to suit my needs and I don't have the C++ experience to complete it, but the necessary changes, from what I have been able to uncover are not that complicated. I need to make some changes that include traversing folders that even the administrator account does not have access too, and I also need ALL of the file permissions (ACLS) to be copied along with the data as its being copied to the backup location. In other words, I need an exact duplicate of the ORIGINATING VOLUME (IE. Drive C) The hobocopy source project works nearly flawlessly, the author simply hasn't invested the time into implementing a few security procedures that I would like to see in the project. I have outlined what I believe needs to be done. Read the "Advanced Project Options" to see more details and requirements for the project. If you are already lost and confused, you probably shouldn't bid. ## Deliverables Below is a full list of the REQUIRED changes needed to the hobocopy project as it stands at version 1.0.0.0 **1)** The backup MUST BE ABLE to traverse every directory in the volume. Which means that it must impersonate SE_BACKUP/SE_RESTORE and utilize FILE_FLAG_BACKUP_SEMANTICS From [login to view URL] [login to view URL] "You need to open the file with the flag FILE_FLAG_BACKUP_SEMANTICS. Neither CopyFile nor MoveFile set the flag when they call CreateFile internally. Microsoft uses the undocumented function PrivCopyFileExW. It sets the FILE_FLAG_BACKUP_SEMANTICS when it calls CreateFile internally. "The only supported way to back up a file while bypassing all security is to exlpicitly call CreateFile with FILE_FLAG_BACKUP_SEMANTICS, and then use the documented APIs BackupRead or BackupWrite. This is the only way to reliably capture all metadata associated with the file (alternate streams, sparseness, DACL, SACL, attributes, extended attributes, hard links, object ID, etc.)" **2)** Ensure that when the source files and folders are copied to the destination that ALL folder and file permissions and CACLS properties are transferred to the destination folder/file. In other words, the destination must explicitly match the source. **3)** It needs to copy the file/folder structure as fast as possible, utilizing the best possible buffer settings to ensure maximum transfer speed. **4)** **NOTE THIS IS NOT A REQUIREMENT to BID**, but if you can figure this out, and implement it, we will make it contractual and your bid price can reflect this. Ultimately I don't like the way that hobocopy just copies each file as it reads it from the source. It is slow, and there is no compression. I would like to see the source files/folders streamed into a compressed ISO image that has some compression capability. Please reply without a bid if you just have questions. I am open to fair bids and I left the bidding field open. I understand this is a slightly more complex project, but I also know that the implementation isn't that the first three requirements are not all that complicated to an experienced C++ programmer. I have spoken to Craig Candera (Author of hobocopy) and he stated that the implementations I am looking at are not that difficult, he just doesn't have the time or necessity now to implement the features. Even with compensation adequate.