19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Safeguard Catalogue - Communications Remarks<br />

____________________________________________________________________ .........................................<br />

S 6.32 Regular data backup<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security management<br />

Implementation responsibility: Administrator, <strong>IT</strong> users<br />

To avoid irretrievable losses of data, regular backups must be made. In most<br />

computer systems this can be largely automated. Procedures must be defined<br />

as to what data is saved by whom at what intervals. Development of a data<br />

backup policy is recommended.<br />

Depending on the volume and importance of the data generated and with due<br />

regard to the possible damage in case of loss of such data, the following must<br />

be specified:<br />

- Intervals<br />

Examples daily, weekly, monthly (depending on the data quantities).<br />

- Time<br />

Examples at night, on Friday evening.<br />

- Number of generations to be kept<br />

Example: in case of daily full backup, the last seven backups will be kept,<br />

as well as the Friday evening backups of the past two months.<br />

- Extent of data to be saved<br />

<strong>The</strong> simplest approach is to define partitions or directories to be covered by<br />

regular data backup; appropriate differentiation can make it easier to obtain<br />

an overview and help to save effort and cost.<br />

Example: self-made files and individual configuration files.<br />

- Data media<br />

Examples tapes, cartridges, floppy disks, mirroring on 2nd hard disk.<br />

- Prior wiping of data media prior to reuse (tapes, cassettes).<br />

- Implementation responsibility (Administrator, user).<br />

- Responsibility for monitoring the backup activities, especially in the case<br />

of automatic backup (error messages, remaining storage capacity of data<br />

media).<br />

- Documentation on backups (date, type of backup procedure / selected<br />

parameters; labelling of data media).<br />

In view of the large amount of time and effort involved, it is generally<br />

possible only to make one full backup per day, at the most. It is not possible to<br />

restore the data generated after the last backup. For this reason and to reduce<br />

costs, incremental backups, whereby only the data newly generated since the<br />

last full backup is saved, should be made at regular intervals between full<br />

backups. (If several incremental backups are made between two full backups,<br />

it is also possible to back up only the data generated after the last incremental<br />

backup.)<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Develop data backup<br />

policy<br />

Incremental backups

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!