SLM version: 1.2.1
CPU: Quad Core 2.4 Ghz Dual Processors(Xeon), having 16 cores.
Mem: 28 GB
file system information:


/dev/cciss/c0d0p6 ext3 227G 144G 83G 64% /var/opt/novell/sentinel_log_mgr/data
/dev/cciss/c0d1p1 ext3 1.1T 143G 901G 14% /slm_archive


/slm_archive is the file system where we take backup of sentinel.

almost a month back, we shutdown the sentinel log manager service to
take the backup via following command


./ -m backup -c -e -l -s -f /slm_archive/24062013/full_backup.tar.gz"


and it took complete 68 hours to complete/finish.

back in March 2013, on the same system, just before upgrading the SLM
1.1.x to 1.2.1, we took the backup via same command, and it was
completed only within 2.5 hours.

we opened the SR for this issue, and got the following response from
> The backup utility provided by Sentinel can backup all of the data in a
> sentinel system ans restore this data back to the point of the backup.
> There a few areas of the backup which needs special attention, this is
> around the backup of the event data. Event data can be a very large data
> set, which consists of a very large number of relatively small files.
> The backup process uses standard shell commands to add these files to a
> tar file, once the files are copied and all of the other pieces of the
> backup have been copied to this location, the set is then compressed.
> The copy of the small files can take an extremely long time to complete.
> When doing a system down backup this can cause and outage for an
> excessive amount of time, which would not be desirable. Using the same
> source and target subsystem for this backup can slow this down even
> further.
> In deployments where the data set is quite big and the downtime time,
> during the backup must be limited, a better solution would be to use a
> 3rd party backup solution to backup the event data in conjunction with
> this utility to backup the configuration data. It is very important for
> a successful backup that the configuration data backup is current. With
> this method a full backup scheme can be designed using incremental of
> differentiation backup and full backups at a less frequent interval.


sharfuddin's Profile:
View this thread: