Hello, @DWigginsSWE, thank you for your patience during our investigation. In response to your query, I'd like to clarify that, indeed, in the current NAKIVO workflow for S3 repositories, data is initially copied to a "transit" folder and subsequently merged into the repository.
However, it's essential to note that the duration of moving data from the "transit" folder depends on the volume of the data being transferred. In some cases, this step may take more time.
For now, it's not possible to improve the performance of this last step as it is done on the S3 repository side after the solution's API request. Should you require any further assistance or have additional questions, please don't hesitate to reach out by email: firstname.lastname@example.org.
There should be a few support bundles on file already from other tickets this week.
As a security admin, the request is pretty simple. Please include the following details in reports:
Which files were found to contain malware
What malware was detected
As an extra, it would be great to have these reports emailed to a security team as they may not be the same people as the backup operators. But a good start would be to include a little more logging/detail in malware reports.
Hello, @Leslie Lei,
Thank you for your post. We acknowledge the importance of optimizing the backup process for efficiency. Currently, we leverage VSS/LVM-based snapshots to read data from the source physical host whenever possible. Our approach involves comparing data with existing backups using hash sums to determine changes at the block level. We do not use file-level comparisons.
In instances where snapshotting is not possible, we resort to low-level reading by sectors on the source disk.
The existing change tracking mechanism is not ideal, and we are working on improvements to speed incremental backups. This improvement has been added to our development roadmap, although a specific ETA is not available at this stage.
We have also forwarded your request to our development team. To help our team understand your environment and solution plan, consider sending us a support bundle. For information on how to create and send a support bundle, please refer to: https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm
We value your input and look forward to any further insights you may have.
Hello, @Leslie Lei. We are currently working on improvements to the retention policies in our software to be included in a release in early 2024.
In the meantime, as a temporary solution, you can enable the legacy retention approach. To enable this approach, in expert settings, you should activate the "Legacy" parameter "system.job.default.retention.approach" accessible in the expert settings. For more details: https://helpcenter.nakivo.com/User-Guide/Content/Settings/Expert-Mode.htm).
With the legacy retention approach, you can specify the backup storage duration for 3 years, for example. Important: If setting for 3 years, the parameter should be set to 4 to achieve the goal you described - 3 for the past 3 years plus 1 for this year.
We'll forward your request to our development team.
To help our team understand your environment and solution plan, consider sending us a support bundle.
For information on how to create and send a support bundle, please refer to: https://helpcenter.nakivo.com/User-Guide/Content/Settings/Support-Bundles.htm