Abstract: A system and method for maintaining multiple inode containers is used to manage file system objects in a single logical volume of a network storage server. The system provides multiple inode containers to store metadata for file system objects in the logical volume. The system may use a first inode container to store private inodes used by the storage server and a second inode container to store public inodes that are useable by clients of the storage server. During a replication process, a source storage server generates a set of replication operations based on inodes in the public inode container and excluding inodes in the private inode container. In a destination server implementing multiple inode containers, the server generates inodes based on the replication operations and stores the inodes in the public inode container. These new inodes are stored in the public inode container with the same inode number or identifier as the corresponding inode on the source storage server.

Abstract: A file system in a storage system allows a user to designate data as write-once read-many (WORM) data. The WORM data are stored in a first set of storage media of the storage system. Signature data are generated from the WORM data. Using the signature data, the integrity of the WORM data can be verified.

Abstract: Methods of iterating through a set of data objects on a source server, copying them to a destination server, and preparing a mapping database correlating source and destination data object identifiers are described and claimed. The mapping database also includes data retention policy information and policy discrepancy information. Systems using similar methods, and software to perform similar methods, are also described and claimed.

Abstract: An operating system is simulated to run in conjunction with a native operating system, allowing processes originally developed for the operating system being simulated to be ported to the environment of the native operating system with a minimum of effort. Ported processes will consume resources of both operating systems, the native operating system and the simulated operating system, that are cleaned or otherwise removed when the ported process ends by setting up a monitoring facility to detect when the ported process ends. When that occurs, the simulated operating system resources are cleaned by a cleanup process that impersonates the ported process that ended. The cleanup process is also monitored, so that when it ends, additional cleanup processes are called into action to cleanup the system resources of the remaining simulated operating system used by the ported process that ended, and the system resources used by the cleanup process.

Abstract: An operating system is simulated to run in conjunction with a native operating system, allowing processes, particularly multi-threaded processes, originally developed for the simulated operating system to be ported to the environment of the native operating system with a minimum of effort. In their natural environment the processes being ported have the capability of requesting that other processes be terminated. This capability is provided in the simulated system and in a multi-threaded environment of the simulated system. Processes executing in the simulated system, even if multi-threaded, also have the capability of protecting against being stopped when executing critical code.

Abstract: An operating system is simulated to run in conjunction with a native operating system, allowing processes originally developed for the operating system being simulated to be ported to the environment of the native operating system with a minimum of effort. In the event a ported process attempts to communicate with a terminated process before the simulated operating system is notified of the termination, the attempt at communication will return an error. In response, a series of checks are performed to determine if the error was the result of termination of the process with which communication was attempted, or a more serious error that should be reported to the native operating system for action to protect the integrity of data.