Patent Application
20170083531
This application claim priority from Chinese Patent Application Number CN2015105959599, filed on Sep. 17, 2015 at the State Intellectual Property Office, China, titled “METHOD AND APPARATUS FOR SELECTING AN INCREMENTAL BACKUP APPROACH,” the contents of which is herein incorporated by reference in entirety.
Embodiments of the present disclosure generally relate to incremental backup.
Computer systems are constantly improving in terms of speed, reliability, and processing capability. As is known in the art, computer systems which process and store large amounts of data typically include a one or more processors in communication with a shared data storage system in which the data is stored. The data storage system may include one or more storage devices, usually of a fairly robust nature and useful for storage spanning various temporal requirements, e.g., disk drives. The one or more processors perform their respective operations using the storage system. Mass storage systems (MSS) typically include an array of a plurality of disks with on-board intelligent and communications electronics and software for making the data on the disks available.
Companies that sell data storage systems are very concerned with providing customers with an efficient data storage solution that minimizes cost while meeting customer data storage needs. It would be beneficial for such companies to have a way for reducing the complexity of implementing data storage.
Embodiments of the present disclosure propose a technical solution for determining a changed data rate of a file system as fast as possible so that an incremental backup approach is selected based on the changed data rate to back up the file system. According to one embodiment, there is provided a method for selecting an incremental backup approach that includes selecting a portion of a current snapshot of a file system; comparing the selected portion with a portion of a historical snapshot of the file system so as to determine a changed data rate of the file system, the portion of the historical snapshot corresponding to the selected portion; and selecting an incremental backup approach based on the changed data rate so as to back up the file system.
Through the detailed description of some embodiments of the present disclosure in the accompanying drawings, the features, advantages and other aspects of the present disclosure will become more apparent, wherein several embodiments of the present disclosure are shown for the illustration purpose only, rather than for limiting. In the accompanying drawings:
Throughout the drawings, the same or corresponding reference numerals represent the same or corresponding parts
Exemplary embodiments of the present disclosure will be described in detail with reference to figures. The flowcharts and block diagrams in the figures illustrate system architecture, functions and operations executable by a method and system according to the embodiments of the present disclosure. It should be appreciated that each block in the flowcharts or block diagrams may represent a module, a program segment, or a part of code, which contains one or more executable instructions for performing specified logic functions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown consecutively may be performed in parallel substantially or in an inverse order, depending on involved functions. It should also be noted that each block in the block diagrams and/or flow charts and a combination of blocks in block diagrams and/or flow charts may be implemented by a dedicated hardware-based system for executing a prescribed function or operation or may be implemented by a combination of dedicated hardware and computer instructions.
The terms “comprising”, “including” and their variants used herein should be understood as open terms, i.e., “comprising/including, but not limited to”. The term “based on” means “at least partly based on”. The term “an embodiment” represents “at least one embodiment”; the terms “another embodiment” and “a further embodiment” represent “at least one additional embodiment”. Relevant definitions of other terms will be given in the description below.
According to one embodiment, a method for selecting an incremental backup approach includes selecting a portion of a current snapshot of a file system. In a further embodiment the method may include comparing a selected portion with a portion of a historical snapshot of the file system so as to determine a changed data rate of a file system, wherein a portion of the historical snapshot corresponding to a selected portion. A further embodiment of the method may include selecting an incremental backup approach based on a changed data rate so as to back up a file system.
Generally, incremental backup refers to a full backup for a file system or a backup for an incremental file since the last incremental backup. Typically, each incremental backup needs to back up files that have been added or modified since the last incremental backup. Typically, this means that an object of the first incremental backup may be files that have been added or modified since the full backup, and an object of the second incremental backup may be files that have been added or modified since the first incremental backup.
Generally, before a backup (either a full backup or an incremental backup) is started, a snapshot for a file system is created. Typically, a snapshot preserves the file system status at exactly a time when the backup is started, so as to prevent subsequent backups from being interfered by possible changes of a file system during the backup process. Traditionally, a backup runs over a snapshot instead of a file system directly. Thus, typically, when a backup of a file system is mentioned, in fact a backup operation takes place on a snapshot of a file system.
Traditionally, when a legacy incremental backup approach is adopted, the traditional incremental backup needs to traverse an entire file system and check each of files one by one, and then backs up the files if the incremental criteria (usually a timestamp) is met. In recent years, generally, a fast incremental backup approach has emerged. Conventionally, fast incremental backup detects differences between a current snapshot and a snapshot that was generated when a last backup was started, checks files from these detected differences, and then backs up the file if an incremental criteria (usually a timestamp) is met.
In some embodiments, selecting a portion of a current snapshot of a file system may include randomly selecting the portion of the current snapshot. In some embodiments, randomly selecting a portion of a current snapshot may include dividing data blocks in a current snapshot into a plurality of groups; and may further include randomly selecting a predetermined number of data blocks in each of a plurality of groups. In some embodiments, selecting a portion of the current snapshot of a file system may include dividing data blocks in a current snapshot into a plurality of groups; and may further include selecting one or more data blocks at a predetermined location in each of a plurality of groups.
In some embodiments, selecting an incremental backup approach based on a changed data rate so as to back up a file system may include comparing a changed data rate with a predetermined threshold. Some embodiment may include, in response to a changed data rate being greater than a predetermined threshold, selecting a legacy incremental backup approach to back up a file system. Some embodiments may include in response to a changed data rate being less than or equal to a predetermined threshold, selecting a fast incremental backup approach to back up a file system. In some embodiments, a predetermined threshold may be between 30% and 50%. In some embodiments, a selected portion may include 1% to 10% of a current snapshot.
According to one embodiment, an apparatus for selecting an incremental backup approach may include a selecting unit configured to select a portion of a current snapshot of a file system. In a further embodiment, the apparatus may include a comparing unit configured to compare a selected portion with a portion of a historical snapshot of a file system so as to determine a changed data rate of a file system, wherein a portion of a historical snapshot corresponding to a selected portion. In a further embodiment the apparatus may include a backup unit configured to select an incremental backup approach based on a changed data rate so as to back up a file system.
In some embodiments, the selecting unit may be further configured to randomly select a portion of a current snapshot. In some embodiments, a selecting unit may be further configured to: divide data blocks in a current snapshot into a plurality of groups; and may further include randomly select a predetermined number of data blocks in each of a plurality of groups. In some embodiments, selecting unit may be further configured to: divide data blocks in a current snapshot into a plurality of groups; and may select one or more data blocks at a predetermined location in each of a plurality of groups.
In some embodiments, backup unit may be further configured to compare changed data rate with a predetermined threshold; and in response to changed data rate being greater than a predetermined threshold, may be configured to select a legacy incremental backup approach to back up the file system; and in response to changed data rate being less than or equal to a predetermined threshold, may be configured to select a fast incremental backup approach to back up the file system. In some embodiments, a predetermined threshold may be between 30% and 50%. In some embodiments, a selected portion may include 1% to 10% of a current snapshot.
In one embodiment there is provided a computer program product that includes a computer readable medium that is carried on computer program code embodied therein and for use with a computer. In a further embodiment, the computer program code may include: code for selecting a portion of a current snapshot of a file system; code for comparing a selected portion with a portion of a historical snapshot of the file system so as to determine a changed data rate of a file system, wherein the portion of the historical snapshot corresponding to a selected portion; and code for selecting an incremental backup approach based on a changed data rate so as to back up a file system.
In one embodiment, a technical solution for selecting an appropriate incremental backup approach based on a changed data rate of a file system according to embodiments of the present disclosure may overcome respective limitations of a fast incremental backup approach and a legacy incremental backup approach under different scenarios (e.g., different changed data rates of a file system), which may help to achieve a better performance. In addition, embodiments of the present disclosure provide a manner with which a changed data rate of a file system may be determined as fast as possible so that a better backup performance may be obtained with little additional overhead.
In one embodiment, usually, it may be a time-wasting operation to compute the changed data rate of a file system. In a further embodiment, Table 1 blow is a test example for a file system with 1,000,000 files, each of which may be 32 KB in size.
In one embodiment, as seen from the first row of Table 1, a full backup of a file system takes 781 seconds. In a further embodiment, as seen from the second row of Table 1, with only 1% data being changed, the time used by a legacy incremental backup amounts to as much as 330 seconds. In a further embodiment, this time may be divided into 2 parts: a file system traverse time and a real data input/output (I/O) time. In a general embodiment, a file system or a snapshot of a file system may contain two parts: a Mode area and a data area. In a further embodiment, for a purposed traversing of a file system or getting differences between snapshots, only an Mode area has to be focused on because the Mode area may contain metadata of a file for incremental criteria filtering and a data area may be used later for real I/O for backup. In a further embodiment, while traversing a file system or comparing differences between snapshots is mentioned, in fact it may refer to an Mode area traversing or comparison.
In the example embodiment as illustrated in Table 1, as data size is only 330 MB, real data I/O time may be only about 1% (around 8 seconds) of the time (781 seconds) used by the full backup, and the rest is file system traverse time, approximately 300 seconds. In a further embodiment, if a file system contains, for example, 20 million files, the file system traverse time may be around 6000 seconds. In a further embodiment, therefore, it may not be feasible to first calculate a changed data rate by traversing an entire file system or comparing all differences between current and historical snapshots of a file system, and then select an appropriate incremental backup approach.
Therefore, according embodiments of the present disclosure, only a portion of a current snapshot of a file system may be selected, a selected portion of the current snapshot may be compared with a corresponding portion of a historical snapshot of the file system so as to calculate a changed data rate of the selected portion of the current snapshot to the corresponding portion of the historical snapshot, and the calculated changed data rate may be used as a changed data rate of the file system. Accordingly embodiments of the present disclosure may provide an approach for determining a changed data rate of a file system as fast as possible.
In some embodiments, selecting a portion of a current snapshot of a file system may include dividing data blocks in the current snapshot into a plurality of groups; and selecting one or more data blocks at a predetermined location in each of the plurality of groups. In a further embodiment, since one or more data blocks at a predetermined location may be selected from each of the groups, this selection operation may also referred to as “even sampling” below. In a further embodiment, for the sake of description, operations of “selecting a portion of a current snapshot of a file system” and “comparing the selected portion with a portion of a historical snapshot of the file system so as to determine a changed data rate of the file system, wherein the portion of the historical snapshot corresponds to the selected portion” (i.e., steps S101 and S102 in
In some embodiments, sampling rate is between 1% and 10%. In an example embodiment, a sampling rate of 1% may be adopted. In a further embodiment, data blocks in a current snapshot may be divided into a plurality of groups and each group contains 100 data blocks, and then a first data block may be selected from the first group. In one embodiment, it should be understood the number of resulting groups may depend on a size of the file system. In a further embodiment, a first data block in a first group may be compared with a corresponding data block in a historical snapshot of a file system, so as to calculate a changed data rate of a first data block in the first group to a corresponding data block in the historical snapshot (abbreviated as a first changed data rate). In a further embodiment, a first data block is also selected from a second group, and a first data block in the second group may be compared with a corresponding data block in a historical snapshot of a file system, so as to calculate a changed data rate of the first data block in the second group to the corresponding data block in the historical snapshot (abbreviated as a second changed data rate), and so on, until changed data rates of the first data blocks in all groups to corresponding data blocks in the historical snapshot are calculated. In a further embodiment, an average of a first changed data rate, a second changed data rate, . . . , and a last changed data rate may be calculated, and the calculated average may be used as a changed data rate of a file system.
In a further embodiment, it may be understood that, no operation is performed on data blocks in each group that are not selected. In one embodiment, it should be understood that for purpose of illustration, description has been presented to the example that a first data block may be selected from each group when a sampling rate is 1%. In a further embodiment, a data block at any appropriate location may be selected from each group, such as the second, the third data block and the like, and the scope of the present disclosure is not limited in this regard.
Similarly, In one embodiment, a sampling rate of 2% may be adopted. casein a further embodiment, for example, the first two data blocks may be selected from a first group, and then the first two data blocks in the first group are compared with corresponding data blocks in a historical snapshot of the file system. In a further embodiment, in an “even sampling” approach as discussed above, one or more data block at a predetermined location may be selected from each group. In a further embodiment, a resulting changed data rate of a file system may be obviously higher or lower than a real value because it may be possible that selected data block(s) may have a highest or a lowest changed data rate.
In a further embodiment a “random sampling” approach in which selecting a portion of a current snapshot of a file system is proposed, which may include randomly selecting a portion of a current snapshot. In some embodiments, randomly selecting a portion of a current snapshot may include dividing data blocks in a current snapshot into a plurality of groups; and may further include randomly selecting a predetermined number of data blocks from each of the plurality of groups.
In a further embodiment, like “even sampling” approach, a sampling rate between 1% and 10% may be adopted in a random sampling approach. In an example embodiment, a sampling rate of 1% may be adopted. In a specific embodiment, like the “even sampling” approach, data blocks in a current snapshot may be divided into a plurality of groups, each of which contains 100 data blocks, and then a data block may be randomly selected from the first group. In a further embodiment, a randomly selected data block in a first group may be compared with a corresponding data block in a historical snapshot of a file system, so as to calculate a changed data rate of a randomly selected data block in a first group to a corresponding data block in a historical snapshot (abbreviated as a first changed data rate for short). In a further embodiment, a data block may also randomly be selected from a second group, and a randomly selected data block in a second group may be compared with a corresponding data block in a historical snapshot of a file system, so as to calculate a changed data rate of a randomly selected data block in a second group to a corresponding data block in a historical snapshot (abbreviated as a second changed data rate), and so on, until changed data rates of randomly selected data blocks in all groups to corresponding data blocks in a historical snapshot are calculated. In a further embodiment, an average of a first changed data rate, a second changed data rate, . . . , and last changed data rate may be calculated, and the calculated average may be used as a changed data rate of a file system.
In one embodiment, Table 2 below shows a test result of testing a file system with 1,000,000 files using the “random sampling” approach. In a further embodiment, in the test, real changed data rate varies between 1% and 99%, and sampling rate varies between 1% and 10%. In one embodiment, the first column (incremental rate) in Table 2 indicates how many files in a file system have actually changed, i.e., real changed data rate of a file system, and the second to the eleventh columns indicate changed data rates (wherein sampling rate is between 1% and 10%) of a file system that may be determined in a “random sampling” approach. In a further embodiment, by calculating a respective difference between each of the second to the eleventh columns and the first column, errors between changed data rates determined in the “random sampling” approach and real changed data rates of a file system may be obtained. In a further embodiment, the last column in Table 2 shows a resulting maximum positive error, and the second last column shows a resulting maximum negative error. In a further embodiment, a maximum of 100 maximum positive errors and a maximum of 100 maximum negative errors may be determined respectively, just as shown in the last row in Table 2. In a further embodiment, as seen from the last row in Table 2, changed data rate of a file system that is determined in the “random sampling” approach ranges between 96.93% and 102.6% of the real changed data rate of a file system. In a further embodiment, as seen from Table 2, in a “random sampling” approach, although a small amount of data may be sampled (sampling rate is between 1% and 10%), the changed data rate of a file system may be determined with higher accuracy.
Still with reference to
In one embodiment, Table 3 below shows respective test results of testing a file system with 1,000,000 files, each of which is 32 KB in size, in a legacy incremental backup approach and a fast incremental backup approach.
In a further embodiment involving a test, first a full backup may run on a file system, so that a time used for running a full backup may be obtained as shown in the second row of Table 3. In a further embodiment, a certain number of files in a file system may be changed, and the changed data rate may be between 1% and 100%. In an example embodiment, for a changed data rate of 1%, actually 10,000 files may be changed, as shown in the third row, the second column from the right of Table 3.
In a further embodiment, as seen from Table 3, as the changed data rate of a file system increases, speed of a fast incremental backup may slow down. In a further embodiment, when the changed data rate of a file system is less than or equal to 40%, a fast incremental back may cost less time than a legacy incremental backup. In a further embodiment, when the changed data rate of a file system is more than 40%, for example, amounts to 45%, the case reverses, i.e., a fast incremental backup may cost more time than a legacy incremental backup.
In relation to Table 3,
As seen from Table 3 and
In on embodiment, time spent by performing a “sampling survey” operation (hereinafter abbreviated as “sampling survey time”) may be further computed from examples in Table 3. In a further embodiment, specifically, for a file system with 1,000,000 files, if the changed data rate is 1%, a total backup time may be around 330 seconds, wherein the total backup time contains traversing time of a file system and real data I/O time. In a further embodiment, traversing time of a file system should be less than 330 seconds. In a further embodiment, for sake of easy computing, an approximate value, 300 seconds, may be used as a traversing time of a file system. In a further embodiment, supposing a sampling rate is 5%, a sampling survey time may be calculated as below:
In a further embodiment, it can be seen that the sampling survey time is around 30 seconds.
In a further embodiment, therefore, Table 3 may be updated, that is, one column may be added to describe time spent in a “smart incremental backup”, so as to compare “smart incremental backup”, legacy incremental backup and fast incremental backup. In a further embodiment, updated Table 3 is as shown in Table 4 below.
In one embodiment, as seen from Table 4, when the changed data rate is 40% for example, time spent in a smart incremental backup approach (i.e., fast incremental backup on the basis of sampling survey) according to the present disclosure may be about 536 seconds, which is only 30 seconds (sampling survey time) more than time spent in an existing fast incremental backup approach (e.g., 506 seconds as shown in Table 4). In a further embodiment, a smart incremental backup approach according to the present disclosure may achieve a better backup performance with little additional overheads. In a further embodiment in relation to Table 4,
Below is an example of pseudo code for an existing fast incremental backup approach.
As seen from the fourth to ninth lines of the above pseudo code, an incremental backup approach is a globally defined configuration item, which can be either configured as a fast incremental backup or a legacy incremental backup. Moreover, a fast incremental backup is always run if configured, and apparently, this method may not flexible enough in many cases.
Below is an example of pseudo code for a smart incremental backup approach according to the present disclosure.
Embodiments of the present disclosure further provide an apparatus for selecting an incremental backup approach.
In some embodiments, selecting unit 401 may be further configured to randomly select a portion of a current snapshot. In some embodiments, selecting unit 401 may be further configured to: divide data blocks in a current snapshot into a plurality of groups; and randomly select a predetermined number of data blocks in each of the plurality of groups. In some embodiments, selecting unit 401 may be further configured to: divide data blocks in a current snapshot into a plurality of groups; and select one or more data blocks at a predetermined location in each of the plurality of groups.
In some embodiments, backup unit 403 may be further configured to: compare the changed data rate with a predetermined threshold; in response to the changed data rate being greater than a predetermined threshold, select a legacy incremental backup approach to back up a file system; and in response to the changed data rate being less than or equal to a predetermined threshold, select a fast incremental backup approach to back up a file system. In some embodiments, a predetermined threshold may be between 30% and 50%. In some embodiments, a selected portion may include 1% to 10% of a current snapshot.
As shown in
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
In particular, according to embodiments of the present invention, the process as described above with reference to
Generally, various exemplary embodiments of the present disclosure may be implemented in hardware or application-specific circuit, software, logic, or in any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executed by a controller, a microprocessor or other computing device. When various aspects of the embodiments of the present disclosure are illustrated or described into block diagrams, flow charts, or other graphical representations, it would be understood that the blocks, apparatus, system, technique or method described here may be implemented, as non-restrictive examples, in hardware, software, firmware, dedicated circuit or logic, common hardware or controller or other computing device, or some combinations thereof.
Besides, each block in the flowchart may be regarded as a method step and/or an operation generated by operating computer program code, and/or understood as a plurality of coupled logic circuit elements performing relevant functions. For example, embodiments of the present disclosure include a computer program product that includes a computer program tangibly embodied on a machine-readable medium, which computer program includes program code configured to implement the method described above.
In the context of the present disclosure, the machine-readable medium may be any tangible medium including or storing a program for or about an instruction executing system, apparatus or device. The machine-readable medium may be a machine-readable signal medium or machine-readable storage medium. The machine-readable medium may include, but not limited to, electronic, magnetic, optical, electro-magnetic, infrared, or semiconductor system, apparatus or device, or any appropriate combination thereof. More detailed examples of the machine-readable storage medium include, an electrical connection having one or more wires, a portable computer magnetic disk, hard drive, random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical storage device, magnetic storage device, or any appropriate combination thereof.
The computer program code for implementing the method of the present invention may be written with one or more programming languages. These computer program codes may be provided to a general-purpose computer, a dedicated computer or a processor of other programmable data processing apparatus, such that when the program codes are executed by the computer or other programmable data processing apparatus, the functions/operations prescribed in the flowchart and/or block diagram are caused to be implemented. The program code may be executed completely on a computer, partially on a computer, partially on a computer as an independent software packet and partially on a remote computer, or completely on a remote computer or server.
Besides, although operations are depicted in a particular sequence, it should not be understood that such operations are completed in a particular sequence as shown or in a successive sequence, or all shown operations are executed so as to achieve a desired result. In some cases, multi-task or parallel-processing would be advantageous. Likewise, although the above discussion includes some specific implementation details, they should not be explained as limiting the scope of any invention or claims, but should be explained as a description for a particular embodiment of a particular invention. In the present specification, some features described in the context of separate embodiments may also be integrated into a single embodiment. On the contrary, various features described in the context of a single embodiment may also be separately implemented in a plurality of embodiments or in any suitable sub-group.
Various amendments and alterations to the exemplary embodiments of the present disclosure as above described would become apparent to a person skilled in the relevant art when viewing the above description in connection with the drawings. Any and all amendments still fall within the scope of the non-limiting exemplary embodiments of the present disclosure. Besides, the above description and drawings offer an advantage of teaching, such that technicians relating to the technical field of these embodiments of the present disclosure would envisage other embodiments of the present disclosure as expounded here.
It would be appreciated that the embodiments of the present disclosure are not limited to the specific embodiments as disclosed, and the amendments and other embodiments should all be included within the appended claims. Although particular terms are used herein, they are used only in their general and descriptive sense, rather than for the purpose of limiting.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2015105959599 | Sep 2015 | CN | national |
