[Answer ID: 14531]

What should be done when an error is recorded in the backup log?

Created 07/30/2012 12:12  |   Updated 10/04/2013 12:46

Follow the guide below in case an error has been recorded in the backup log.

Error Code cause solution example
code5 No share folder found on backup target

・Check the LAN cable connection.

・Check the power cables of equipment on the path.

rsync error: error starting client-server protocol (code 5) at main.c(1504)
code12 No communication with backup origin

・Check the LAN cable connection.

・Check the power cables of equipment on the path.

rsync error: error in rsync protocol data stream (code 12) at io.c(515)
Setup detected during back-up Refrain from the setup during back-up.

A setup makes the communication be interrupted temporarily, causing a backup error.
code20 Communication interrupted during backup Refrain from the setup during backup.

A set-up makes the communication be interrupted temporarily, causing a back-up error.
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(242)
code23 Prohibited characters used for file and folder name Change the file and folder name.

rsync error: some files could not be transferred (code 23) at main.c(702)
Data on backup origin modified during backup Refrain from modifying data on the backup origin during back-up.

Modified data is not backed up, causing a back-up error.
Files, the single size of which exceeds 4GB, backed up on USB hard drive with FAT32 format

・Limit the single file size under 4GB.

・Change the format of the USB hard drive.

Following a back-up from the TeraStation to an external USB hard drive with FAT32 format, the upper- and lower-case changed in the folder and file names on the back-up origin TeraStation In case an external USB hard drive is with FAT32 format, refrain from changing the upper- and lower-case in the folder and file names on the back-up origin TeraStation.

The Linux running on the TeraStation distinguishes upper- and lower-case (case-sensitive) in the OS level. On the other hand, no unique rule to handle case-sensitivity in the FAT file system level results in lack of uniqueness in handling files with the same name but in different cases.

Either XFS or EXT3 format is recommended for a stable back-up for the TeraStation.
code24 Data on backup origin modified during back-up Refrain from modifying data on the backup origin during back-up.

Modified data is not backed up, causing a backup error.
rsync warning: some files vanished before they could be transferred (code 24) at main.c
code14、code22 Insufficient memory, backup not completed

・Reduce the number of files to back up.

・Refrain from a simultaneous execution of backup and other functions.

ERROR: out of memory in flist_expand
rsync error: error allocating core memory buffers (code 22) at util.c(120) [sender=2.6.8]

rsync: fork failed in do_recv: Cannot allocate memory (12)
rsync error: error in IPC code (code 14) at main.c(655) [receiver=2.6.8]




 

 



Details


Products

OS / Hardware

Was this answer helpful?
Please tell us how we can make this answer more useful.

Refine your search

Select Product / OS & Hardware

      Enter Keywords or a specified ID