Methods and systems for backing up a search index

• US 9,922,061 B2
• Filed: 05/09/2014
• Issued: 03/20/2018
• Est. Priority Date: 05/14/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Paksoy, Mustafa, Bergan, Jeffrey M., Maheshwari, Kanishka
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Le, Jessica N
• Application Number:
  US14/274,554
• Publication Number:
  US 20140250082A1
• Time in Patent Office: 1,411 Days
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/2272 Management thereof
• CPC Class Codes: G06F 2201/80 Database-specific techniques

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.

Claims

1. A method for generating a secondary search index while a primary search index is being used for indexing or querying, the method comprising:

creating, with one or more processors of a computing environment, the secondary search index as a staged copy of the primary search index by suspending indexing for a period of time long enough to make a temporary copy of the primary search index to a staging location;

segmenting, with the one or more processors of the computing environment, the staged copy of the primary search index, wherein the secondary search index has multiple segments that are handled asynchronously through a message queue, wherein each segment is a readable index that contains only a subset of the primary search index;

storing the segments in a pre-selected memory location of the computing environment sequentially;

copying the segments to a storage device with an asynchronous message queuing structure;

performing, with the one or more processors of the computing environment, additional indexing to the secondary search index based on information from one or more replay logs corresponding to one or more tenants in a multitenant environment to keep the indexes up to date within a pre-selected amount of time, wherein the one or more replay logs tracks activity that occurs after index backup is initiated; and

maintaining the secondary search index within a pre-selected threshold of current utilizing the replay logs.

2. The method of claim 1 further comprising compressing the segments of the staged copy.

3. The method of claim 1 wherein the primary search index is an index to be backed up in a multitenant environment, wherein

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 are only allowed access data identified by a tenant ID associated with the respective client entity, and

the multitenant environment is at least a hosted database provided by an entity separate from the client entities, and provides on-demand database service to the client entities.

4. The method of claim 3 wherein the primary search index to be backed up is an index corresponding to a single tenant ID within the multitenant environment.

5. The method of claim 3 wherein the primary search index to be backed up is an index corresponding to a multiple tenant IDs within the multitenant environment.

6. The method of claim 1 wherein the one or more replay logs comprises at least one replay log for create and update operations and at least one replay log for delete operations.

7. An article of manufacture comprising a non-transitory computer-readable medium having stored thereon instructions capable of, when executed by one or more processors, cause a computer to:

create, with one or more processors of a computing environment, the secondary search index as a staged copy of the primary search index by suspending indexing for a period of time long enough to make a temporary copy of the primary search index to a staging location;

segment, with the one or more processors of the computing environment, the staged copy of the primary search index, wherein the secondary search index has multiple segments that are handled asynchronously through a message queue, wherein each segment is a readable index that contains only a subset of the primary search index;

store the segments in a pre-selected memory location of the computing environment sequentially;

copy the segments to a storage device with an asynchronous message queuing structure;

perform, with the one or more processors of the computing environment, additional indexing to the secondary search index based on information from one or more replay logs corresponding to one or more tenants in a multitenant environment to keep the indexes up to date within a pre-selected amount of time, wherein the one or more replay logs tracks activity that occurs after index backup is initiated; and

maintain the secondary search index within a pre-selected threshold of current utilizing the replay logs.

8. The article of claim 7 further comprising compressing the segments of the staged copy.

9. The article of claim 7 wherein the primary search index is an index to be backed up in a multitenant environment, wherein

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 are only allowed access data identified by a tenant ID associated with the respective client entity, and

the multitenant environment is at least a hosted database provided by an entity separate from the client entities, and provides on-demand database service to the client entities.

10. The article of claim 9 wherein the primary search index to be backed up is an index corresponding to a single tenant ID within the multitenant environment.

11. The article of claim 9 wherein the primary search index to be backed up is an index corresponding to a multiple tenant IDs within the multitenant environment.

12. The article of claim 7 wherein the one or more replay logs comprises at least one replay log for create and update operations and at least one replay log for delete operations.

13. A system comprising:

one or more user electronic systems;

a server electronic system communicatively coupled with the one or more user systems via a network, the server system to create, with one or more processors of a computing environment, the secondary search index as a staged copy of the primary search index by suspending indexing for a period of time long enough to make a temporary copy of the primary search index to a staging location, to segment, with the one or more processors of the computing environment, the staged copy of the primary search index, wherein the secondary search index has multiple segments that are handled asynchronously through a message queue, wherein each segment is a readable index that contains only a subset of the primary search index, to store the segments in a pre-selected memory location of the computing environment sequentially, to copy the segments to a storage device with an asynchronous message queuing structure, to perform, with the one or more processors of the computing environment, additional indexing to the secondary search index based on information from one or more replay logs corresponding to one or more tenants in a multitenant environment to keep the indexes up to date within a pre-selected amount of time, wherein the one or more replay logs tracks activity that occurs after index backup is initiated, and to maintain the secondary search index within a pre-selected threshold of current utilizing the replay logs.

14. The system of claim 13 wherein the server electronic system is further configured to compress the segments of the staged copy.

15. The system of claim 13 wherein the primary search index is an index to be backed up in a multitenant environment, wherein

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 are only allowed access data identified by a tenant ID associated with the respective client entity, and

the multitenant environment is at least a hosted database provided by an entity separate from the client entities, and provides on-demand database service to the client entities.

16. The system of claim 15 wherein the primary search index to be backed up is an index corresponding to a single tenant ID within the multitenant environment.

17. The system of claim 15 wherein the primary search index to be backed up is an index corresponding to a multiple tenant IDs within the multitenant environment.

18. The system of claim 13 wherein the one or more replay logs comprises at least one replay log for create and update operations and at least one replay log for delete operations.