Skip to main content
Start a Conversation

Unsolved

S

SydJunaidShah

1 Rookie

 • 

6 Posts

19

May 19th, 2025 11:25

if I didnt apply networker directives is there any risk when recovring the bacup when needed if yes what directive should applied for LOGS

what directive should be applied for LOGS for Size Grew so that every log should be backup with no loss when recovering

SYSLOG-OSADMIN: /rsyslog          level=incr,    723 GB 05:29:42   2549 files
completed savetime=1747608941
94694:save: The backup of save set '/rsyslog' succeeded.
--- Job Indications ---
Warning: `/rsyslog/rsyslog_custom/eprobdb2/dbus-daemon.log' size grew during save
Expected 569817421 bytes for `/rsyslog/rsyslog_custom/eprobdb2/dbus-daemon.log', got 569818064 bytes

bbeckers1

2 Intern

 • 

191 Posts

June 20th, 2025 17:59

https://www.dell.com/support/kbdoc/en-us/000050052/error-warning-file-name-size-grew-during-save?lang=en "NetWorker: Backup reports 'Warning <file> size grew during save'"

"

This article applies to NetWorker
Change Product

Symptoms

Backup succeeds but gets marked as failed in NMC. The failure message indicates: Error: 'Warning-'<file-name>' size grew during save'. 
129292:save: Successfully established Client direct save session for save-set ID '3634349703' (nw_client_name:/dir) with Data Domain volume 'DataDomain.001'.
nw_client_name: /dir level=incr, 117 MB 00:00:03 8 files
completed savetime=1503641693
94694:save: The backup of save set '/dir' succeeded.
--- Job Indications ---
Warning: `/dir/some_file' size grew during save
Expected 59674974 bytes for `/dir/some_file', got 59680075 bytes
nw_client_name:/dir: retried 1 times.

Cause

This is expected behavior. This warning appears when any file has a large change rate during the backup session; for example, logs.

Resolution

This is a WARNING, not a FAILURE. The warning can be mitigated by applying logasm to the directory/file in a NetWorker directive.

logasm enables file changes during backup sessions. logasm can be used for log files and other similar files where a file changing during a backup operation is not noteworthy.

Setting logasm on a specific directory/file does not resolve the warning for all directories/files on the client, but it can be set recursively on a directory tree. Create a separate logasm for each directory/file path if it is not part of an already specified directory tree within a recursive logasm. Apply this directive to each client that reports this warning once configured.

"

So the directive ONLY mitigates the alert/warning, it does nothing wrg to the files being open and thus changing during save. For log files however it would not be an issue, would it? We ignore it (and set the workflows to not cause an error status when this occurs).

It is an actual issue if is is reported for for example database files, as those should not end up in the filesystem backup anyways and should have been skipped using an appropriate directive, those of course should be backed up using the appropriate nw module or via a dump/export to disk (and have that dump backed up).

Regular restore testing should show if this may an issue (which it unlikely is).

Also it is only reported for linux/unix systems, while for windows systems it wouldn't even be reported. Alas some open file files (like for example open database files) might even be silently skipped because they are locked in a specific way (while you would want to at least see that in the logs but it doesn't).

Was this post helpful?

View All

No Events found!

Top