Versions Compared

Old Version 21

changes.mady.by.user Former user

Saved on

compared with

New Version 22

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ArgumentPurposeExamples
-backupRecordStoreTo backup the record store where the persisted events are saved. This

./analytics-backup.sh -backupRecordStore -dir /home/user/backup

The above command backs up all the tables in the DAS record store to the /home/user/backup directory.

-backupFileSystemTo backup the file system where data relating to the indexing of events.

./analytics-backup.sh -backupFileSystem -dir /home/user/backup

The above command backs up indexing information relating to all the tables in DAS to the /home/user/backup directory.

-dir <directory>Directory used as the target when backing up the record store/file system, or as the source when restoring already backed up record store/file system. The directly should be specified in every command issued to backup or restore data.

-dir /home/user/backup

The above argument in all the other examples specifies the /home/user/backup directory as the location where backed up data should be stored or as the source from which data should be restored.

-restoreRecordStoreTo restore a record store. Before you use this command, the record store you want to restore should be already backed up.

./analytics-backup.sh -restoreRecordStore -dir /home/user/backup

The above command restores record store data currently saved in the /home/user/backup directory to the current DAS node.

-restoreFileSystemTo restore a file system. Before you use this command, the file system you want to restore should be already backed up.

./analytics-backup.sh -restoreFileSystem -dir /home/user/backup

The above command restores indexing related data currently saved in the /home/user/backup directory to the current DAS node.

-enableIndexing

Indexing is disabled in the data restoration step by default. This is because if the target DAS server is already running, that server will also index the same data causing an index corruption. If you are certain that the target DAS server is not running, you can index the data at the time it is restored by using this argument. If this argument is not used while the target DAS server is not running, the data restored from the time the target server is started up is indexed in the usual way.

./analytics-backup.sh -restoreRecordStore -restoreFileSystem -enableIndexing -dir /home/user/backup

The above command restores both record store data and indexing related data currently saved in the /home/user/backup directory to the current DAS node, and indexes the data at the time of restoration.

-reindexEventsThis switch will make the tool re-index the data already there in a table. This can be useful in a scenario where an the indexing is corrupted for some reason, or if some of the older data is not indexed because it was not mentioned in the schema etc..

./analytics-backup.sh -restoreRecordStore -restoreFileSystem -reindexEvents -dir /home/user/backup

The above command restores both record store data and indexing related data currently saved in the /home/user/backup directory to the current DAS node, and reindexes the event at the time of restoration.

-tables <table list>

This argument is used to specify the list of event tables that should be backed up or restored.

Info

If you do not use this argument to back up data from one or more specific tables, all the available event tables will be backed up.

/analytics-backup.sh -backupRecordStore -tables Table1,Table2,Table3 -dir /home/user/backup

The above command backs up the data of Table1, Table2, Table3 event tables to the /home/user/backup directory.

./analytics-backup.sh -restoreRecordStore -tables Table1,Table2,Table3 -dir /home/user/backup

The above command restores record store data of  Table1, Table2, Table3 event tables that are currently saved in the /home/user/backup directory to the current DAS node.

-tenantId <tenant id (default is super tenant)>

This argument is used to select the tenant ID(s) of which the events should be backed up.

./analytics-backup.sh -backupRecordStore -tenantId abc -dir /home/user/backup

The above command backs up all the event tables of the abc tenant from the DAS record store.

-disableStagingThis argument is used to disable staging. Staging involves including the indication whether the data is indexed or not when backing up/restoring the DAS record store. This task incurs a greater system overhead. Therefore, it is allowed to disable staging when the number of records being backed up/restored is high. Backing up and restoring the file system via -backupFileSystem and -restoreFileSystem allows you to preserve the indexing which would enable searches to be carried out on restored data.

./analytics-backup.sh -backupRecordStore -disableStaging

The above command backs up all the event tables in the DAS record store. Indications of whether data is indexed or not are removed before backing up the records.

-timefrom timeFrom <yy-mm-dd-hh:mm:ss>

This argument specifies the starting time (inclusive) when defining the time period that should be considered when backing up/restoring events.

Info

This argument should be used together with the -timeto argument.

./analytics-backup.sh -backupRecordStore -timefrom 15-10-11-12-40-00 -timeto 15-10-15-17-00-00 -dir /home/user/backup

The above command backs up all the data in the DAS record store created between 12.45PM on 11th October 2015 to 5.00PM on 15th October 2015. The data is backed up in the /home/user/backup directory.

-timeto timeTo <yy-mm-dd-hh:mm:ss>

This argument specifies the ending time (inclusive) when defining the time period that should be considered when backing up/restoring events.

Info

This argument should be used together with the -timefrom argument.


./analytics-backup.sh -backupRecordStore -timefrom 15-10-11-12-40-00 -timeto 15-10-15-17-00-00 -dir /home/user/backup

The above command backs up all the data in the DAS record store created between 12.45PM on 11th October 2015 to 5.00PM on 15th October 2015. The data is backed up in the /home/user/backup directory.

...

Code Block
languagetext
./analytics-backup.sh -restoreRecordStore -tables Table1,Table2,Table3 -backupFileSystem -timefromtimeFrom 15-08-11-08-:00-:00 -timetotimeTo 15-10-15-22-:30-:00 -dir /home/user/backup

...

Code Block
languagetext
./analytics-backup.sh -restoreRecordStore -tables Table1,Table2,Table3 -restoreRecordStore -timefromtimeFrom 15-08-11-09-:00-:00 -timetotimeTo 15-08-11-10-:00-:00 -dir /home/user/backup

...