Editing Single Instance Storage (SIS)
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| 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 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. | + | 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. | ||
Advertising:
