Abstract: A backup system override may be specified to allow a backup system to access a backup created on an old storage device. For example, an archival backup may be accessed long after the storage device that created the backup has been decommissioned. The file history information in the backup may specify a storage device no longer accessible by the backup system. An override in the backup system allows the backup system to access the backup with the file history information through a different storage device than the storage device that created the backup. The different storage device may have a different name and/or be of a different type than the original storage device that created the backup. The override may also allow access to command scripts and links in the backup.

Abstract: Databases may be backed up on a mass storage device. Storing the database backup on mass storage, rather than tape drive, allows operations, such as from a database manager, with large input/output to improve performance. A method of backing up a database to a mass storage device may include receiving, at a database manager, a call from a backup utility to copy data from a source file to a destination file, performing, at the database manager, a plurality of input/output requests, in response to the call, to copy data from the source file to the destination file, and returning, to the backup utility, status information regarding completion of the call Placing the database backup on mass storage can further enable use of that backup as a shadow or alternate database.

Abstract: Databases may be copied to a shadow database on amass storage device. The structure of the files containing the database, such as blocking information and a dump history, may be copied in whole to the mass storage device. The method may include creating a shadow database on a mass storage device, populating the shadow database with data from a production database, idling an application accessing the production database to create an idle point in the production database, and updating the shadow database to the production database.

Abstract: Database backup performance may be improved by copying only used portions of a database file. When the database file includes allocated but un-used pages, the unused pages are not replicated during a database backup. By replicating only the allocated and used pages in the database, the backup time may be decreased and the amount of storage required in the second file may be decreased.

Abstract: A backup system override may be specified to allow a backup system to access a backup created on an old storage device. For example, an archival backup may be accessed long after the storage device that created the backup has been decommissioned. The file history information in the backup may specify a storage device no longer accessible by the backup system. An override in the backup system allows the backup system to access the backup with the file history information through a different storage device than the storage device that created the backup. The different storage device may have a different name and/or be of a different type than the original storage device that created the backup. The override may also allow access to command scripts and links in the backup.

Abstract: Files may be assigned to groups for processing in an efficient manner. For example, a group may include a list of file names for processing together. The file names are assigned to the group by a user. When a command is executed on the system for modifying a file, the group name is provided along with the command rather than the file name or list of individual file names. The command automatically executes repeatedly for each file name associated with the group name.

Abstract: Various approaches for processing a B+ tree data structure are described. In one approach, in a first transaction a first insert operation to a first data page of a first index page in the B+ tree data structure is detected, and then it is determined whether performing the first insert operation would block a second insert operation in a second transaction concurrent with the first transaction. At least one empty second data page is created in response to determining that the second insert operation would be blocked by the first insert operation. The B+ tree data structure is updated to include the at least one second data page in the B+ tree data structure, and the updated index pages and second data page are committed to retentive storage. Thereafter, the first insert can be completed.

Abstract: Various approaches for processing a B+ tree data structure are described. In one approach, in a first transaction a first insert operation to a first data page of a first index page in the B+ tree data structure is detected, and then it is determined whether performing the first insert operation would block a second insert operation in a second transaction concurrent with the first transaction. At least one empty second data page is created in response to determining that the second insert operation would be blocked by the first insert operation. The B+ tree data structure is updated to include the at least one second data page in the B+ tree data structure, and the updated index pages and second data page are committed to retentive storage. Thereafter, the first insert can be completed.