Is there a place where we can also nudge Synology to get moving along? They put this new requirement in place clearly without a way to avoid interruption from anyone providing solutions on their platform.
In a new release (version 10.4), we have updated the UI for the Repository screen. The repository type menu was removed. The "Store backups in separate files" option was added (enabled by default). Backup repositories created in previous versions of the product keep operating in the way they were configured.
Background: Storing backups in separate files is recommended.
Downside: it has higher space requirements.
Upsides: it is more resilient to network, power, and hardware failures; it does not require running space reclaim; it is suitable for enterprise-grade deduplication storage devices; it supports immutable recovery points.
Solution: If you still want to use the "forever incremental" repository and built-in data deduplication, please uncheck the "Store backups in separate files" checkbox when creating the backup repository.
If you need any further information, please don't hesitate to contact me.
Has forever incremental repository type been discontinued in the latest versions?
I don't see the option when creating a new repository.
I know that forever incremental comes with the annoyance of having to do space reclaims but there is still a use case.
Eg. For doing large backups across a WAN connection. There would be bandwidth issues with doing a weekly full backup across a WAN connection.
I had the same issue on a virtual applience. Boris solution worked for me as well.
1. Connect to the Transporter via SSH (for instance with Putty)
2. cd /opt/nakivo/transporter
3. ./bhsvc stop
./bhsvc -b "<UsePassword>" (creates a masterpassword)
4. Go to the Nakivo configuration > Transporter > edit > enter the masterpassword and connect > accept the certificate
5. Fixed and working again.
@DaniAvni and @Mario, hi!
Currently, the exclusion of specific files from the backup of the Physical machines is not yet supported. However, this feature is in our backlog. We do not have ETA.
We would recommend sending us a support bundle with a detailed description of the feature request so we can pass it to our Product Team.
Thank you a lot for your suggestions! They let us improve.