guides:reference:nodebackups
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
guides:reference:nodebackups [2021/10/21 06:43] – ↷ Links adapted because of a move operation pgels | guides:reference:nodebackups [2024/07/03 12:31] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Node backups ====== | ||
+ | |||
+ | Backups are part of the NetYCE lifecycle. As per the [[guides: | ||
+ | |||
+ | Also the NCCM can be used to create backups regularly. | ||
+ | |||
+ | The protocol used to send the backups for modeled nodes can be changed in the [[menu: | ||
+ | |||
+ | This page describe several items for manipulating backup behavior. | ||
+ | |||
+ | ===== Disabling backups ===== | ||
+ | In some cases, like a testlab or until connectivity has been arranged, it is desired to turn off backups for command jobs. | ||
+ | |||
+ | This behavior is changed per vendor and per command and state. | ||
+ | |||
+ | Modify the state_actions table under '' | ||
+ | |||
+ | The example below shows that backups have been disabled for: | ||
+ | |||
+ | * Vendor_type: | ||
+ | * Command: cmd_exec | ||
+ | * State: preconfig and postconfig | ||
+ | * Action: backup | ||
+ | * Disabled: set to ' | ||
+ | |||
+ | > NOTE: [[menu: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | ===== Disable tftpd ===== | ||
+ | |||
+ | The following steps will disable the tftp daemon. | ||
+ | |||
+ | > NOTE: This disables feature like ZTP (Zero touch provisioning) and backups for vendors that only support tftp. | ||
+ | |||
+ | The use of tftp as a file-transfer protocol can be disabled in NetYCE using the global configuration file | ||
+ | ''/ | ||
+ | |||
+ | Locate the line "< | ||
+ | |||
+ | The result is similar to below: | ||
+ | <code xml> | ||
+ | < | ||
+ | < | ||
+ | <configs crontab=" | ||
+ | < | ||
+ | </ | ||
+ | <yce ... | ||
+ | </ | ||
+ | |||
+ | > Note that disabling tftp server will only prevent tftp transfers, it does not control which transfers protocols will be attempted. The Vendor-specific and Hardware specific (see step 3) settings will define this behavior. | ||
+ | |||
+ | As '' | ||
+ | |||
+ | For each vendor_type and model you may choose to use a different transfer protocol, if it was set to tftp or the default behavior was using tftp. You may see the defaults in the [[guides: | ||
+ | |||
+ | Navigate to '' | ||
+ | |||
+ | {{guides: | ||
+ | |||