NO_FILE_DELETES Keyword
NO_FILE_DELETES={ON|OFF}
This keyword alters the handling of files on secondary or backup replication managers during a delete operation.
When set to ON, files on any secondary or backup replication data managers are not deleted but rather renamed as '_<filename>.<count>'. By default this keyword is set to OFF.
This keyword must be specified in the replication section that is included in the configuration file for the primary server.
Example:
NO_FILE_DELETES=ON
In this example, all files deleted on the primary server will be renamed on the backup or secondary servers.
Note the following:
The flags in the HOSTnn keyword override the global NO_FILE_DELETES keyword setting. When the NO_FILE_DELETES keyword is used, it takes affect for all secondary or backup replication data managers. However, this keyword can be turned off or on for individual servers by appending additional configuration flag settings to the end of the HOSTnn keywords. This is done by appending a ':' (colon) character after the port number and flags that can be set or cleared. The flags are represented by alpha characters in a comma separated list. A leading '-' (hyphen) character indicates that the flag is to be cleared.
The flags controlling the NO_FILE_DELETES process are:
|
Flag |
For a specific host server, the NO_FILE_DELETES processing is ... |
|
N or n |
enabled. |
|
-N or -n |
disabled |
Examples:
HOST01=N999999:192.168.110.99:3934:N
HOST02=N999999:192.168.110.98:3934:-N
See Also: SUNDM Keywords, SUNADMIN, MAKEMFD
![]() |