User's Manual

You do not need to manually build the directory tree structure, as the nested directory path is
built automatically step-by-step during the backup procedure.
In most cases, Avaya recommends that you not overwrite a previous backup. System
administrators typically want to make a copy of the environment both before and after making
maintenance updates, and in some cases want to store a history online.
To establish flexibility in the backup approach, a number of special values are supported in the
eCAB module. These special values are valid only in the BU_To_Path_str field
• The special value [timestamp] is used at the beginning of the backup to calculate the
current time stamp, formatted in a 14-character string containing both date and time
indication (YYYYMMDDHHNNSS). The path is dynamically recalculated, and provides a
new unique directory path:
- C:\Temp\[timestamp]\SOPHO Messenger@Net\Mdb becomes C:\Temp
\20011009190312\SOPHO Messenger@Net\Mdb
The special value [weekday] is used at the beginning of the backup to calculate the current
time stamp, formatted in a one-character string containing the day of week indication
(1=Monday, 2=Tuesday, 3=Wednesday, and so on. The path is dynamically recalculated,
and provides a new unique directory path:
- C:\Temp\[weekday]\SOPHO Messenger@Net\Mdb becomes C:\Temp\3\SOPHO
Messenger@Net\Mdb
The special value [weekdayname] is used at the beginning of the backup to calculate the
current time stamp, formatted in a character string containing the name of the day of week
(Monday, Tuesday, Wednesday, and so on). The path is dynamically recalculated, and
provides a new unique directory path. The day of week is in the language identified in the
regional settings of the Windows environment:
- C:\Temp\[weekdayname]\SOPHO Messenger@Net\Mdb becomes C:\Temp
\Wednesday\SOPHO Messenger@Net\Mdb
An example of an entry typically found in this field is as follows: C:\Temp\[weekday]\SOPHO
Messenger@Net\Mdb
BU_To_File_str
This field specifies the file name of the destination file, which is, in most cases, the same as
the source file. Therefore, Avaya recommends that you specify the same value as in
BY_From_File field.
An example of an entry typically found in this field is as follows: Messenger_CFG.mdb
Table: eBACKUP
194 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? infodev@avaya.com