Examples of systems described herein include a file server virtual machine of a virtualized file server configured to manage storage of a plurality of storage items. The file server virtual machine including a file system configured to receive an access request directed to a storage item of the plurality of storage items and associated with a user. The file system is further configured to retrieve an access control list having permissions information associated with the storage item, and to cache a permissions profile for the user including all permissions pertaining to the user for the storage item. The file system is further configured to determine whether the access request is permissible based on the cached permissions profile.

Generating a storage interface includes receiving a request for documents, detecting an accounting workflow type corresponding to request, and identifying a document organizational structure matching the accounting workflow type. Further, a virtual storage interface is built using an index on the documents and according to the document organizational structure, and presented.

A virtual file organization system, method and program product are disclosed. Included is a system that assigns classification tags to files stored within a storage system based on a natural language processing (NLP) context analysis of each file; and a virtual smart folder that is viewable within a user interface, wherein: opening the virtual smart folder causes a set of virtual subfolders to be displayed in which each virtual subfolder includes a category title; opening of a virtual subfolder causes a set of files residing at disparate locations in the storage system to be displayed; and the files displayed by opening the virtual subfolder each include an assigned classification tag that is associated with the category title of the virtual subfolder.

One example method includes an interface for mounting virtual disks from multiple sources. The interface may interface with different sources using appropriate programming interfaces. The virtual disks are then mounted in the interface. The virtual disks can be analyzed to identify the associated partitions. Volume configurations are determined for the partitions. The files for the partitions are remounted in the interface.

A method for managing file based backups (FBBs) includes obtaining, by a FBB metadata file manager and by an application, a file request for a file stored in a FBB, wherein the FBB is stored in a backup storage system, identifying, using a FBB metadata file of the FBB, a storage location of the file, initiating generation of a temporary storage device, storing a copy of the file in the temporary storage device using the storage location and the FBB, and initiating, after the storing, access to the copy of the file for the application.

A system for managing storage space for a computer may include at least one processor programmed to determine a maximum data space for a computing task. The at least one processor may also be programmed to create a file having a maximum size equal to or greater than the maximum data space. The at least one processor may further be programmed to create a virtual device linked to the file and mount a filesystem inside the virtual device. The at least one processor may also be programmed to mount the virtual device. The at least one processor may further be programmed to determine that the computing task is completed. The at least one processor may further be programmed to unmount the virtual device.

An information processing apparatus is able to access a file storage region which is formed in accordance with job defining information that defines tasks of a job and a file to be created in each of the tasks. The file storage region is formed for each job or each job and each task. A file related to a job or a task is stored in a corresponding file storage region. The information processing apparatus includes a processor which is configured to: obtain job status information concerning a status of each job for which a file storage region is formed; and select, a display element indicating files stored in a first file storage region, a file as a subject file to be displayed, from among the files stored in the first file storage region, in accordance with the status of a first job corresponding to the first file storage region.

The present technology pertains to synchronizing contents of a directory external to a synchronized directory by a content management system. The content management system is configured to synchronize only objects in the synchronized directory. Accordingly, the present technology creates an anchor object that represents the directory external to the synchronized directory within the synchronized directory. The anchor object includes special attributes that indicate to the synchronization client that the anchor object represents an external directory, and allows the contents of that directory to be synchronized directly to a server on the content management system without first storing the contents of the external directory on the hard drive of the client device.

A manifest file from a container image for a cross-platform application that has been containerized for execution on a source platform specifies image layers for the cross-platform application within the container image and are ordered from a first image layer through a last image layer. The manifest file specifies exclusion/inclusion directories related to containerized execution of the cross-platform application on a target platform different than the source platform. Starting with the first image layer and ending at the last image layer, each image layer is unpacked at the target platform by copying files from the image layer to a directory at the target platform in accordance with the identified exclusion/inclusion directories. A version of the cross-platform application corresponding to the image layers as unpacked at the target platform is executed in a containerized manner.

One example method includes receiving a set of database parameters, creating one or more simulated databases based on the database parameters, receiving a set of target characteristics for the database, based on the target characteristics, slicing a datastream into a grouping of data slices, populating the simulated database(s) with the data slices to create the database collection and forward or reverse morphing the database from one generation to another without rewriting the entire database collection.