setdatasync(1M)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXIT STATUS | ATTRIBUTES | FILES | SEE ALSO

NAME

setdatasync- modify the data propagation list used in data synchronization

SYNOPSIS

setdatasync [-i interval] schedule filename
setdatasync cancel filename
setdatasync push filename
setdatasync backup
setdatasync clean

DESCRIPTION

setdatasync enables you to specify a user-created file to be added to or removed from the data propagation list (/var/opt/SUNWssp/.ssp_private/user_file_list). This list identifies the files to be copied from the main to the spare SSP as part of data synchronization for automatic failover. The specified user file and the directory in which it resides must have read and write permissions for user ssp.

---

Note -

Data synchronization uses the available disk space in the /tmp directory to copy files from the main SSP to the spare. If you have files to be copied that are larger than the /tmp directory, those files cannot be propagated. For example, if the data synchronization backup file (ds_backup.cpio) gets larger than the available space in /tmp, you must reduce the size of this backup file before data propagation can occur. The size of the ssp_backup.cpio file will give you an indication of the size of the data synchronization backup file. You can remove the following files:

• $SSPLOGGER/messages.x

• $SSPLOGGER/domain/Edd-recovery files

• $SSPLOGGER/domain/messages.x

• $SSPLOGGER/domain/netcon.x

• $SSPLOGGER/post/files

where x is the archive number of the file. Because these files are propagated from the new main SSP to the spare after a failover, you must remove these files on both the main and spare SSP to prevent the regeneration of these files.

---

The data synchronization process checks the user-created files on the main SSP for any changes. If the user-created files on the main SSP have changed since the last propagation, they are repropagated to the spare SSP. By default, the data synchronization process checks a specified file every 60 minutes. However, you can use setdatasync to indicate how often a user file is to be checked for modifications.

---

Note -

After a file is propagated from the main SSP to the spare, the file is repropagated to the spare only when the file on the main SSP is updated. If you remove a propagated file from the spare SSP, that file will not be automatically repropagated until the corresponding file on the main SSP has been changed.

---

You can also use setdatasync to do the following:

• Propagate a specified file to the spare SSP, without adding the file to the data propagation list.

• Resynchronize the SSP configuration files on the main and spare SSP.

• Erase all entries and temporary files in the data propagation list and remove the data propagation list (useful for single SSP configurations).

OPTIONS

The following options are supported:

backup

Backs up the main SSP, moves the backup data from the main to the spare SSP, and restores the backup data on the spare SSP.

This backup is similar to the backup created when you run ssp_backup, except that it does not back up the /tftpboot directory.

The data synchronization backup does not restore the following files:

• /var/opt/SUNWssp/.ssp_private/machine_server_fifo

• /var/opt/SUNWssp/adm/messages

• /var/opt/SUNWssp/adm/messages.dsbk

• /var/opt/SUNWssp/.ssp_private/user_file_list

• /var/opt/SUNWssp/.ssp_private/.ds_queue

The data synchronization backup can fail if the backup file exceeds the available disk space in the /tmp directory. See the first NOTE in the DESCRIPTION section for details on reducing the size of the backup file.

cancel filename

Removes (cancels) the specified file from the data propagation list, which means the specified file will no longer be propagated to the spare SSP. This option does not actually remove the specified file from the spare SSP. The file name must contain the absolute path and cannot be a symbolic link to another file.

clean

Removes all entries and temporary files from the data propagation list and erases the list. This option is useful for managing disk space in a single SSP configuration, where the data propagation list can grow quite large and consume unnecessary disk space.

This option is to be used for single SSP configurations only. Do not use this option if you have a dual SSP configuration because this option can desynchronize data between the main and spare SSP.

-i interval

Indicates how often the specified file is to be checked for modifications. The default interval is 60 minutes. The interval can range from 1 to 1440 minutes (24 hours).

push filename

Propagates (pushes) the specified file to the spare SSP without adding it to the data propagation list. The file name must contain the absolute path and cannot be a symbolic link to another file.

schedule filename

Adds the specified file to the data propagation list. The file name must contain the absolute path and cannot be a symbolic link to another file. During data synchronization, the file is propagated to the same absolute path on the spare SSP.

EXIT STATUS

The following exit values are returned:

0

Successful completion.

>0

An error occurred.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Architecture	All
Availability	SUNWuessp
Stability	Evolving
MT-Level	Safe

FILES

The following file is supported:

/var/opt/SUNWssp/.ssp_private/user_file_list

Data propagation list

SEE ALSO

datasyncd(1M), showdatasync(1M)

Sun Enterprise 10000 SSP User Guide

SSP 3.5  Last Revised 27 April 2001

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXIT STATUS | ATTRIBUTES | FILES | SEE ALSO