Smart log parser for backup software to ease troubleshooting
View Patent ↗In one example, a method can be performed that involves receiving user input concerning a failure of a data protection job, and performing various operations automatically without requiring further user input or action. Such operations include querying a database, based on the user input, to identify a log file, accessing the log file and extracting information from the log file based on the user input, using information extracted from the log file to identify a potential cause of the failure, and generating a report that lists the potential cause of the failure.
1. A method, comprising:
mapping a backup application module to a plurality of log files stored in a database, wherein the database stores log files for each of multiple modules of the backup application;
receiving input concerning a failure of a data protection job associated with the backup application module, wherein the user input includes first user input that identifies the failed data protection job and second user input; and
performing the following operations automatically without requiring further user input or action:
querying a database with a query, based on the first user input, to identify a log file from the plurality of log files mapped to the backup application module and associated with the data application module;
accessing the log file and extracting information from the identified log file based on the second user input, wherein the second user input defines a scope of the identified log file to be reviewed;
reviewing the log file in accordance with the second user input;
extracting information from the identified log file based on the second user input; and
generating a report that lists the potential cause of the failure, wherein the second user input acts as a filter when extracting information to eliminate extraneous information from the report.
2. The method as recited in claim 1 , wherein the method is performed by a smart log parser core engine of the backup application.
3. The method as recited in claim 1 , wherein the data protection job is one of: a backup operation; a restore operation; a recover operation; or, a clone operation.
4. The method as recited in claim 1 , wherein the information extracted from the log file is associated with one or more particular timestamps specified in the user input.
5. The method as recited in claim 1 , wherein accessing a log file comprises accessing only a log file that includes information about the failure.
6. The method as recited in claim 1 , wherein receiving user input comprises receiving user input that comprises one or more timestamps and/or an identity of a failure node.
7. The method as recited in claim 1 , wherein receiving user input comprises receiving a user query as to whether or not a failure has occurred.
8. The method as recited in claim 1 , wherein the identified log file is associated with a specific backup module of the backup application.
9. The method as recited in claim 1 , wherein the data protection job is a block based data protection job.
10. The method as recited in claim 1 , wherein a portion of a user input workflow is implemented in the form of a wizard.
11. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, perform the operations:
mapping a backup application module to a plurality of log files stored in a database, wherein the database stores log files for each of multiple modules of the backup application;
receiving user input concerning a failure of a data protection job associated with the backup application module, wherein the user input includes first user input that identifies the failed data protection job and second user input; and
performing the following operations automatically without requiring further user input or action:
querying a database with a query, based on the first user input, to identify a log file from the plurality of log files mapped to the backup application module and associated with the data application module;
accessing the log file and extracting information from the identified log file based on the second user input, wherein the second user input defines a scope of the identified log file to be reviewed;
reviewing the log file in accordance with the second user input;
extracting information from the identified log file base on the second user input; and
generating a report that lists the potential cause of the failure, wherein the second user input acts as a filter when extracting information to eliminate extraneous information from the report.
12. The non-transitory storage medium as recited in claim 11 , wherein the method is performed by a smart log parser core engine of the backup application.
13. The non-transitory storage medium as recited in claim 11 , wherein the data protection job is one of: a backup operation; a restore operation; a recover operation; or, a clone operation.
14. The non-transitory storage medium as recited in claim 11 , wherein the information extracted from the log file is associated with one or more particular timestamps specified in the user input.
15. The non-transitory storage medium as recited in claim 11 , wherein accessing a log file comprises accessing only a log file that includes information about the failure.
16. The non-transitory storage medium as recited in claim 11 , wherein receiving user input comprises one of: receiving user input that comprises one or more timestamps and/or an identity of a failure node; or, receiving a user query as to whether or not a failure has occurred.
17. The non-transitory storage medium as recited in claim 11 , wherein the identified log file is associated with a specific backup module of the backup application.
18. The non-transitory storage medium as recited in claim 11 , wherein the data protection job is a block based data protection job.
19. The method as recited in claim 1 , wherein a portion of a user input workflow is implemented in the form of a wizard.
20. A server comprising:
one or more hardware processors; and
the non-transitory storage medium as recited in claim 11 .