BackupTime
The time when the backup specified by the Path parameter was created.
When you use the DREINITIAL action and set the Path and RestoreTime parameters, the Content component needs the time of the backup to determine which index commands it has to replay.
- If you restore from a backup created by this Content component, you do not need to set this parameter because Content uses internal information it stores about its backups.
- If you restore from a backup created by a different Content component, you must set this parameter to ensure correct index command replay. You can obtain an accurate time by sending
action=GetBackupData&BackupForRestoreTime=...
to the Content component that created the backup, whereBackupForRestoreTime
is the value you want to use forRestoreTime
.
You can use the following formats to specify your dates:
Format | Explanation |
---|---|
D+/M+/#YY+
|
A date. For example, If the year is a number less than 40, it is read as a year in the 2000s. If the year is a number between 40 and 99, it is read as a year in the 1900s. For example, IDOL Server treats the date as a date in its local timezone. |
YYYY-MM-DD
|
A date in ISO-8601 format. For example, 2017-05-12 |
HH:NN:SS D+/M+/#YY+
|
A time and date. For example, If the year is a number less than 40, it is read as a year in the 2000s. If the year is a number between 40 and 99, it is read as a year in the 1900s. For example, IDOL Server treats the date as a date in its local timezone. |
YYYY-MM-DDTHH:NN:SSZ
YYYY-MM-DDTHH:NN:SS±HHMM
|
A date and time in ISO-8601 formats, with a time zone (either as a literal Z, or a four digit time zone offset). For example, |
HH:NN:SS D+/M+/#YY+ #ADBC
|
A time and date with a time period. For example, For the time period, you can use IDOL Server treats the date as a date in its local timezone. |
N
|
A positive or negative number of days from the current date. For example, |
Ns
|
A positive or negative number of seconds from now. For example, |
Ne
|
Epoch seconds (seconds since 1 January 1970 UTC). For example, |
NOTE: IDOL Server treats any date that does not have explicit timezone information as a date in the local timezone, both in the index and in your query parameters. This behavior might result in non-intuitive matches.
For example, epoch second values are always UTC. The value 1012345000e
matches times as 22:56:40 on 29 January 2002 UTC. If your local timezone is GMT-6, this query might match an indexed date value of 03:56:40 on 29 January 2002 (which corresponds to the same time UTC), because the indexed date is in your local timezone.
Similarly, if your query date is 03:56:40 29/01/2002
, this might match an indexed epoch seconds date of 1012345000
.
Actions: | DREINITIAL |
Type: | String |
Default: | |
Example: | BackupTime=1460900000e
|
See Also: |