Database backup to disk terminates during a copy operation:
BR278E Command 'cp /oracle/C11/sapdata...':
write failed, file system is full
BR279E Return code from 'cp /oracle/C11/sapdata...': 1
BR222E Copy of /oracle/C11/sapdata... to ... failed.
Cause and prerequisites
Feature of the UNIX file system: more space is required in the file
system than just the size of the new file. The additional space
is used for fine system administration information. When large
datasets are involved, the 100 KB reserve used by brbackup may
be too small.
Second possible cause: rounding error in the compression factors
used to estimate the size of compressed files when compress = yes.
Third possible cause: the backups are performed relatively far apart (e.g. once a week) or mass changes were made to the database (e.g. upgrade, reorganization, data transfer), and the old compression rates are no longer current as a result.
Solution
The reserve for file system administration information in brbackup will
be increased. Corrected in 2.1F.
The rounding error with the compression factors were corrected in
2.1H and 2.2B.
In SAP 2.2D+/2.2E/2.1K, a general solution to the problem is to distribute the existing space reserve among all the directories.
After mass changes in the database, and before the next backup is started, we recommend starting a dummy compression run by calling "brbackup -k only".
Temporary solution: use backup_mode init
Key word: BR-BACKUP
No comments:
Post a Comment