Abstract: Described are ion implantation devices, systems, and methods, and in particular to an ion source that is useful for generating an aluminum ion beam.

Abstract: A first flag is set on a backup file to which data to be backed up is written. The first flag indicates that the backup file should be automatically retention locked after a cooling off period is over. Before the cooling off period is over, a request is received to open the backup file for writes. The request is allowed and upon allowing the request, the first flag is cleared and a second flag is set on the backup file indicating that writes are in progress. The clearing of the first flag excludes the backup file from being automatically retention locked after the cooling off period is over.

Abstract: Making inline deduplicated backups of protected data using group fingerprints resident in a storage server by generating group fingerprints on a storage server for a backup client that is not capable of using group fingerprints, from individual fingerprints generated for each segment of protected data divided into variable size segments and then grouped together. Each fingerprint comprises a signature for a respective data segment. The method further maintains the group fingerprints for files resident on the storage server, compares, in the storage server, respective group fingerprints for these files with a new backup file to be backed up from the backup client to determine duplicated data between these files, and converts the new backup file to a virtual synthetic backup during a backup time of the new file.

Abstract: Embodiments of a targeted deduplication process that splits protected data into variable size segments, generates a fingerprint for each segment, and then combines fingerprints into groups to form group fingerprints. An embodiment auto-generates and persists the group fingerprints for the backups which are already on the storage server, thus enabling the backup client to fetch these fingerprints using an identifier and enforce synthesis for the new backup or replication copy against any previously written backup. For this embodiment, group fingerprints are generated on the storage server itself, rather than being generated on and pushed from the backup client for mere storage on the storage server, so that, as files are ingested, the storage server also auto-generates group fingerprints on its own.

Abstract: A backup system stores recipes during backup file creation when virtual synthetic backups are used, where a recipe comprises a specific sequence of steps used to generate the backup file. Replication logic of the backup system replays the recipe to generate the same backup file on the backup target so that an old backup combined with new backup data comprises the recipe. Embodiments of a server-side group fingerprint system include a process to auto-generate recipes for server resident files by formulating a file as a series of L1 fingerprints which are in turn a set of L0s and GFPs where some of the L1s are shared with other files. The recipe can be used to convert the representation of the file from a native fingerprint based representation into a virtual synthetic format.

Abstract: Described are ion implantation devices, systems, and methods, and in particular to an ion source that is useful for generating an aluminum ion beam.

Abstract: Systems and methods for using certificate authority certificates inline as part of a file transfer protocol are described. A backup system may receive a request from a client system for a first secure communications channel secured with a previously-shared encryption key. The backup system may transmit a message via the first secure communications channel that indicates that the backup system is one-way CA certificate encryption capable based on the client version of the backup application of the client system. In response to a query, received via the first secure communications channel, to create a second secure communications channel, the backup system may transmit, via the first secure communications channel, the one-way CA certificate after a comparison of security settings indicates that one-way CA certificate encryption is the highest encryption level available. The second secure communications channel may then be set up to transmit encrypted client data.

Abstract: Systems and methods for using certificate authority certificates inline as part of a file transfer protocol are described. A backup system may receive a request from a client system for a first secure communications channel secured with a previously-shared encryption key. The backup system may transmit a message via the first secure communications channel that indicates that the backup system is one-way CA certificate encryption capable. In response to the message, the client system may transmit a query to create a second secure communications channel. The backup system may then transmit, via the first secure communications channel, the one-way CA certificate to the client system. Once the client system has been configured for CA certificate-based communication, the second secure communications channel may be established. The client system may then transmit, via the second secure communications channel, encrypted client data for storage on the backup server.

Abstract: Embodiments of file restores in a Data Domain (DD) file system implementing a DD Bandwidth Optimized Open Storage Technology (DDBoost) library that translates application read and write request to DDBoost application program interfaces (APIs). A prefetch queue processor creates an intent to read the file. The application passes the file handle of the file, and the destination handle where the data must be read into. As the queue is processed, the prefetch for the request (handle/offset/length) is passed to the file server. The filesystem processes the request to open the file to load into memory. As the read request for the same file reaches the filesystem the file data is read from memory for writing to the destination handle. An extended DDBoost API expression is defined to pass the current path and destination path to the application.

Abstract: Embodiments of small file restore process in deduplication file system wherein restoration requires issuing a read request within an I/O request to the file system. The process places the small files in a prefetch queue such that a combined size of the small files meets or exceeds a size of the prefetch queue as defined by a prefetch horizon. A queue processor issues a read request for the first file in the queue, scans the prefetch queue to find a read request for a file at the prefetch horizon, and prefetches the file at the prefetch horizon. The prefetch queue essentially constitutes a hint from the client that a read I/O is imminent for purposes of filling the read-ahead cache and preventing a need to issue a blocking I/O operation.

Abstract: Embodiments of small file restore process in deduplication file system wherein restoration requires issuing a read request within an I/O request to the file system. A prefetch queue processor creates an intent to read the file, rather than opening the file upon receiving the request. During this step, the application passes the file handle of the file, and the destination handle where the data must be read into. As the queue is processed, the prefetch for the request (handle/offset/length) is passed to the file server. The filesystem processes the request to equivalently ‘open’ the file, and bring the data into memory. As the read request for the same file reaches the filesystem the file data is read from memory for writing to the destination handle.

Abstract: Embodiments of small file restore process in deduplication file system wherein restoration requires issuing a read request within an I/O request to the file system. The process places the files in a prefetch queue such that a combined size of the files meets or exceeds a size of the prefetch queue as defined by a prefetch horizon. A file handler disassociates prefetch streams from read streams. The handler prefetches the read operations and stores them in memory. The stream corresponding to a read will only open as the read requests hit the queue processor. As a result, the stream usage is very low, since the I/O, worker threads and the read streams are disassociated from each other.

Abstract: During a current backup of a file system of a client, a determination is that a file in the current backup includes first data regions found in a file from a previous backup, and second data regions that are new. A virtual synthetic file is generated by writing the second data regions, and synthesizing the first data regions by referencing the file from the previous backup. A request received to restore the particular file includes identifications of other files still present at client. A determination is that the particular file corresponds to the virtual synthetic file and that the other files still present at client include the file from the previous backup. The second data regions are read to send to client. A complete version of the particular file is assembled at client using the file from the previous backup, still present at client, and the second data regions.

Abstract: Embodiments for a system and method for secure authentication of backup clients in a way that eliminates the need to create users for backup client authentication anywhere in the backup ecosystem, and which eliminates the need for credentials, such as passwords that need protection, updating and synchronization. Such embodiments use a short-term token, such as a JSON web token, for both client and server authentication within the system, and verifies that the tokens grant access using the public key corresponding to the private key assigned to the directory objects by the creator of the directory objects.

Abstract: Embodiments of a targeted deduplication process that splits protected data into variable size segments, generates a fingerprint for each segment, and then combines fingerprints into groups to form group fingerprints. The group fingerprints are stored on and retrieved from a server by a client to identify duplicate data present on a server during the backup process on an “as needed” basis. The specific group fingerprints sent are based on knowledge of previous backups of the asset, either learned or provided as a hint from the backup application. Once it is known that a specific group fingerprint is present on the server, a virtual synthetic request can be generated instead of a traditional deduplication process. This enables virtual synthetic backups for applications that do not have sufficient knowledge of changed blocks from a previous backup to use the virtual synthetic operations on their own.

Abstract: A database manager maintains a database including information tracking a set of storage units and a set of storage appliances on which the storage units currently reside. At least a portion of the tracking information is cached in a server cache at a namespace redirection server. Some of the tracking information is cached in a set of client caches at a set of clients. A request to access a storage unit is received at a client. A lookup is made into a client cache at the client to find a storage appliance having the storage unit. A determination is made that there is a problem accessing the storage unit using the client cache. So, the namespace redirection server is queried for updated tracking information concerning a location of the storage unit. The client assists the namespace redirection server with management of the server cache.

Abstract: A request is received to restore a file at a deduplicated storage system to a client. The file resides at the storage system as a synthetic file based on a base file at the storage system. The request includes an indication that the base file is also present at the client. Metadata generated during a backup of the file to the storage system is reviewed. The metadata includes references to data determined to be in the base file at the storage system, and references to other data determined to not be in the base file at the storage system. The other data determined to not be in the base file is read from the storage system and transmitted to the client. Upon receipt, the client assembles the requested file using the base file present at the client and the other data determined to not be in the base file.

Abstract: Embodiments of small file restore process in deduplication file system wherein restoration requires issuing a read request within an I/O request to the file system. The process places the files in a prefetch queue such that a combined size of the files meets or exceeds a size of the prefetch queue as defined by a prefetch horizon. A file handler disassociates prefetch streams from read streams. The handler prefetches the read operations and stores them in memory. The stream corresponding to a read will only open as the read requests hit the queue processor. As a result, the stream usage is very low, since the I/O, worker threads and the read streams are disassociated from each other.

Abstract: One example method includes by a data source entity, querying a data storage entity to determine if it has adequate under-utilized resources to perform a portion of a data seeding process. When the data storage entity indicates to the data source entity that the data storage entity has adequate unused resources to perform the portion of the data seeding process, initiating, by the data source entity, the data seeding process, and the data seeding process includes transmitting data from the data source entity to the data storage entity for storage in a temporary file at the data storage entity, and the data that is transmitted is data that was targeted to be protected by a data protection process. Finally, the data protection process may be performed so that only data not already present at the data storage entity is transmitted by the data source entity to the data storage entity.

Abstract: Embodiments of small file restore process in deduplication file system wherein restoration requires issuing a read request within an I/O request to the file system. A prefetch queue processor creates an intent to read the file, rather than opening the file upon receiving the request. During this step, the application passes the file handle of the file, and the destination handle where the data must be read into. As the queue is processed, the prefetch for the request (handle/offset/length) is passed to the file server. The filesystem processes the request to equivalently ‘open’ the file, and bring the data into memory. As the read request for the same file reaches the filesystem the file data is read from memory for writing to the destination handle.