Pre-freeze/post-thaw in Linux guest with Domino

[MartinL]

We are running backups on 3 Linux servers with Domino.

All servers run Domino 9.0.1 and we use Daniel Nashed's start-stop script
https://www.nashcom.de/nshweb/pages/startscript.htm

2 of them is running SLES11 SP4 and here simple scripts running with notes user works:

Code: Select all

#!/bin/sh
/etc/init.d/rc_domino stop

and

Code: Select all

#!/bin/sh
/etc/init.d/rc_domino start

But the last server is SLES 12 SP2 and are another story. Using init.d as notes user requires further authentication as root.
Alternatively Domino can be started/stopped by "systemctl start/stop domino.service".
But no matter what combination in a script i try, Veeam fails executing the script.

Running the script as root i have tried:
Script finished execution with unexpected exit code: 126

Code: Select all

#!/bin/sh
systemctl stop domino.service

Script finished execution with unexpected exit code: 2

Code: Select all

#!/bin/sh
exec systemctl stop domino.service

So the question really just boils down to if anyone have some experience in starting/stopping services using a script in combination with Veeam B&R?

[zuldan]

Hi MartinL, I don't have the answer to your question but out of curiosity are you using the DAOS feature in Domino?

[DGrinev]

Hi Martin and welcome to the community.

How did you try to execute scripts through VMWare quiescence or Veeam?
This would help in further troubleshooting process, as it does seem like a permission issue.

Thanks!

[MartinL]

@zuldan
We are using DAOS on the primary and most critical Domino server. It's running SLES 11, so one of the servers working.

@DGrinev
Thanks for the welcome.

Currently i'm trying to execute them in Veeam under Guest Processing.

[DGrinev]

Martin,

Please can you try to execute scripts under VMWare quiescence, this will help us in isolating the root cause of the issue.
There is existing thread about how to use VMWare tools pre-freeze post-thaw scripts.

Thanks!

[zuldan]

MartinL as you are aware, email attachments are stored in the DAOS database. Since Veeam does not support the Domino backup/restore API, when you restore a mailbox it will most likely not have any attachments. We are not using Veeam to backup Domino because of this problem so I'm interested to know how you are getting around the DAOS issue?

[MartinL]

@DGrinev
Thanks. I will try that in the next backup window.

@zuldan
We have a 30 day Deferred Deletion Interval, so in most cases all NLO files are there.
If some files are pruned you can get a list of missing files on the server:

Code: Select all

tell daosmgr listnlo -o missingnlo.txt database_file_name.nsf

Then get the missing NLO files in missingnlo.txt from earlier backups. If possible, recovered NLO files should be placed in their original subfolder.

After that re-synchronize the DAOS catalog.

[MartinL]

Using VMWare quiescence works. No errors and a complete backup.

Using the simple script:

Code: Select all

#!/bin/sh
systemctl stop domino.service

[DGrinev]

Hi,

You can continue to utilize VMware quiescence with the scripts since it is working flawlessly.
Otherwise, you should troubleshoot permissions issue of the account in Guest Processing menu, as it seems to be the root cause of the issue.

Thanks!

[MartinL]

Hi DGrinev

I'll just stick to VMware quiescence since it works. Thanks for the help.