Can we allocate more resources for space reclaim to run faster?

[Mark]

Our space reclaim we run each week, but never get past about 57-58% before stopping for weekend backups and copies offsite, then starting again the next week. Could we administratively allocate more processing resources for the space reclaim to get further at least once, then return them to default? This is running on a Synology NAS.

[Official Moderator]

On 5/6/2021 at 9:21 PM, Mark said:

Our space reclaim we run each week, but never get past about 57-58% before stopping for weekend backups and copies offsite, then starting again the next week. Could we administratively allocate more processing resources for the space reclaim to get further at least once, then return them to default? This is running on a Synology NAS.

Hello, @Mark!

Please generate and send us a new Support Bundle with the main database included for further investigation.

Check how to do it here https://helpcenter.nakivo.com/display/NH/Support+Bundles#SupportBundles-CreatingSupportBundles

Let me know if I can help you with anything else.

[Mark]

that was done this morning with link to URL of this discussion in summary as well as the question that started this 

[Official Moderator]

15 hours ago, Mark said:

that was done this morning with link to URL of this discussion in summary as well as the question that started this 

Great! Our Support Team will do their best to resolve your issue.

If anything extra occurs, don't hesitate to contact me.

[Mario]

@Mark Please keep the forum updated, if you have any news.

reclaim is one of the biggest pain in my point of view at the current status of nakivo.

[Mark]

@Official Moderator it has been a week with no response from support. Assistance is requested.

[Official Moderator]

Hello, @Mark!

I'm sorry to hear that, probably it happened due to the high load. I am sure the Support Team is working on your request. I will contact the team and ask at what stage your Support Bundle is. 

As soon as I have more information, I will get back to you. 

[Official Moderator]

@Mark, could you please tell me the email you indicated in the support bundle? You can send it to me in a private message.

[Mark]

@Official Moderator just messaged; I had not seen your response here requesting that information

[Official Moderator]

@Mark, thank you! Hopefully, we can solve your issue as fast as possible.

[Official Moderator]

@Mark, the Support Team informs me that they received the last support bundle from you on May 11. Since then, you have received a reply and three follow-up messages. However, our Support Team specialists didn't receive a response from you, that's why the ticket is now expired. 

If your issue remains unsolved, please let us know and create a new Support Bundle. I would also kindly ask you to check your email inbox so that the communication process goes smoothly and effectively.

[User]

Can you explain how the problem was solved?
We have a similar problem, our space reclaim is running for about 60 hours each week, which is a very long time. In my opinion, that is too long.

[The Official Moderator]

21 hours ago, User said:

Can you explain how the problem was solved?
We have a similar problem, our space reclaim is running for about 60 hours each week, which is a very long time. In my opinion, that is too long.

To increase maintenance speed in the future, you can add more CPU threads to the repository configuration file. 

Please follow those instructions for Linux-based transporters:

1. Gracefully stop the maintenance.

2. Detach repository.

3. Stop transporter service.

4. Create file ".conf" (command "touch .conf") inside of the system repository folder "../NakivoBackup"

5. Edit file ".conf"  (command "vi .conf") and add the string "maintenance.threads=4" (this will assign 4 threads per maintenance

echo "maintenance.threads=4" >>.conf

6. Change the file permissions and owner to the same as in the NakivoBackup folder (For Linux OS only), for instance:

#chown bhsvc:bhsvc .conf

#chmod 770 .conf

7. Start transporter service.

8. Attach the repository.

9. Re-run maintenance.