Abstract: An index to be backed up in a computing environment is identified. A staged copy of the index to be backed up is created. The staged copy of the index is segmented. The segments are uploaded to a pre-selected location.

Abstract: An index to be backed up in a multitenant environment is identified. The multitenant environment includes data for multiple client entities, each identified by a tenant identifier (ID) having one of one or more users associated with the tenant ID. Users of each of multiple client identities can only access data identified by a tenant ID associated with the respective client entity. The multitenant environment is a hosted database provided by an entity separate from the client entities, and provides on-demand database service to the client entities. A staged copy of the index to be backed up is created. The staged copy of the index is segmented. The segments are uploaded to a pre-selected location.

Abstract: An index to be backed up in a multitenant environment is identified. The multitenant environment includes data for multiple client entities, each identified by a tenant identifier (ID) having one of one or more users associated with the tenant ID. Users of each of multiple client identities can only access data identified by a tenant ID associated with the respective client entity. The multitenant environment is a hosted database provided by an entity separate from the client entities, and provides on-demand database service to the client entities. A staged copy of the index to be backed up is created. The staged copy of the index is segmented. The segments are uploaded to a pre-selected location.

Abstract: Secondary indexing mechanisms are disclosed. A first index is created in a database environment. The index has a scope defined by a set of files that meet a pre-selected criteria. Second index generation is initiated. Te second index has the same scope as the first index. A first time period between initiation of the generation of the second index and completion of the second index is determined. The second index is swapped with the first index in an atomic swap operation. The indices may be generated for a multitenant database environment. Catch up indexing may be performed for the secondary index.