Contents

1   Introduction

This document describes how to schedule a backup that is to occur at regular intervals.

Note:  

When any of the following backup operations is in progress, a scheduled backup event that is triggered is postponed and retried at regular intervals later:

• Manual backup creation
• Scheduled backup creation
• Backup deletion
• Backup restore

1.1   Prerequisites

This section describes the prerequisites, which must be fulfilled before using the procedure.

1.1.1   Conditions

The following conditions must apply:

• The event name is known.
• The periodic event schedule is known.
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2   Procedure

To schedule a backup that is to occur at regular intervals:

1. Navigate to the BrmBackupScheduler managed object, for example:

   >dn ManagedElement=NODE06ST,SystemFunctions=1,BrM=1,BrmBackupManager=SYSTEM_DATA,BrmBackupScheduler=SYSTEM_DATA

2. Enter Config mode:

   (BrmBackupScheduler=SYSTEM_DATA)>configure

3. Enter the event name, for example:

   (config-BrmBackupScheduler=SYSTEM_DATA)>BrmPeriodicEvent=P_EVENT_20140428_204

4. Create the periodic event by setting the required attributes, for example:

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>days=1

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>hours=5

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>minutes=30

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>weeks=1

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>months=2

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>startTime=2014-06-31T23:59:59

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>stopTime=2015-02-28T23:59:59

   Note:  

   Normally, not all attributes are needed to set.

   The value of these attributes cannot be cleared using the no <attribute_name> ECLI command.

   If Daylight Saving Time (DST) occurs after the scheduling but before the scheduled time (when the backup is created), the timer does not count the minus or plus one hour of time difference. It is the duration of the scheduling interval that matters, not the system clock.

   
   
5. Commit the periodic event:

   (config-BrmPeriodicEvent=P_EVENT_20140428_204)>commit

6. Verify that the periodic event was created:

   (BrmPeriodicEvent=P_EVENT_20140428_204)>show

   In the following example, outputs of periodic event configuration backups are created every 2 months, 1 week, 1 day, 5 hours, and 30 minutes between 2014-06-31 and 2015-02-28:

   BrmPeriodicEvent=P_EVENT_20140428_204 days=1 hours=5 minutes=30 months=2 startTime="2014-06-31T23:59:59" stopTime="2015-02-28T23:59:59" weeks=1