Difference between revisions of "Single Instance Storage (SIS)"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
This message occurs when the Single Instance Storage (SIS) change logging metafile is full. Change logging is stopped. New writes to the volume will not be change logged until the next SIS operation. | This message occurs when the Single Instance Storage (SIS) change logging metafile is full. Change logging is stopped. New writes to the volume will not be change logged until the next SIS operation. | ||
Action: | Action: | ||
| − | Issue the <code>[[sis start]]</code> command on the volume to process existing changelogs. To process changelog files more frequently before they reach full, adjust the SIS operation | + | Issue the <code>[[sis start]]</code> command on the volume to process existing changelogs. To process changelog files more frequently before they reach full, adjust the SIS operation schedule with the <code>[[sis config]] -s</code> command. If there is significant loss of savings, then run the <code>sis start -s</code> command, allowing it to run to completion. |
| − | |||
Latest revision as of 10:47, 13 October 2020
This article is a Draft. Help us to complete it.
sis.changelog.full: SIS change logging metafile for volume VOLUME_NAME is full.
This message occurs when the Single Instance Storage (SIS) change logging metafile is full. Change logging is stopped. New writes to the volume will not be change logged until the next SIS operation. Action: Issue thesis startcommand on the volume to process existing changelogs. To process changelog files more frequently before they reach full, adjust the SIS operation schedule with thesis config -scommand. If there is significant loss of savings, then run thesis start -scommand, allowing it to run to completion.
See also[edit]
Advertising:
