Gavino Posted September 2, 2025 Posted September 2, 2025 I keep getting a 403 Forbidden message every time I post. It is SOOOOO frustrating. I'm going off this. https://helpcenter.nakivo.com/User-Guide/Content/Backup/Creating-Proxmox-VE-Backup-Jobs/Backup-Job-Wizard-for-Proxmox-VE-Options.htm There is all kinds of incomplete and contradictory info there. If only this forum would let me post the information I want to post without rudely shoving a "403 Forbidden" in my face, after I have spent hours researching and describing the damn issue. If it lets me say this much... One part says "Place the scripts in the appropriate folders on each VM" another section on the same page says "Place a script file on the machine on which the Director is installed" What is it? It's all over the place. Another section links to a knowledge base article saying "See also Application-Aware Mode for Linux VMs for script examples, but there are no script examples. I'm pulling my hair out with the product, and now I'm pulling my hair out trying to post about why I'm pulling my hair out. Quote
The Official Moderator Posted September 3, 2025 Posted September 3, 2025 On 9/2/2025 at 8:24 AM, Gavino said: I keep getting a 403 Forbidden message every time I post. It is SOOOOO frustrating. I'm going off this. https://helpcenter.nakivo.com/User-Guide/Content/Backup/Creating-Proxmox-VE-Backup-Jobs/Backup-Job-Wizard-for-Proxmox-VE-Options.htm There is all kinds of incomplete and contradictory info there. If only this forum would let me post the information I want to post without rudely shoving a "403 Forbidden" in my face, after I have spent hours researching and describing the damn issue. If it lets me say this much... One part says "Place the scripts in the appropriate folders on each VM" another section on the same page says "Place a script file on the machine on which the Director is installed" What is it? It's all over the place. Another section links to a knowledge base article saying "See also Application-Aware Mode for Linux VMs for script examples, but there are no script examples. I'm pulling my hair out with the product, and now I'm pulling my hair out trying to post about why I'm pulling my hair out. In case we are talking about scripts in the job (so called pre- and post-job scripts), these scripts should be located on NAKIVO director machine and they are executed on NAKIVO director machine. On the other hand, these scripts could initiate other scripts on necessary (backed-up) machines. Quote
Gavino Posted September 5, 2025 Author Posted September 5, 2025 Thank you. The main source of confusion is this legacy page: https://helpcenter.nakivo.com/Knowledge-Base/Content/Application-Awareness-Issues/Application-Aware-Mode-for-Linux-VMs.htm?Highlight=pre-freeze-script That is the knowledge Base article for Application Aware Mode for Linux VMs - exactly what I was investigating. On my Linux VMs I was doing what it says there which is "put the custom scripts called pre-freeze-script and post-thaw-script into the /usr/sbin directory " and every time I did I was getting errors about not finding the scripts. Unfortunately my Google search brought that page up up first, so I was confident that scripts had to live on the guest VM. It was only after that, that I read the link I originally posted .....to be continued... Quote
Gavino Posted September 5, 2025 Author Posted September 5, 2025 This was the next thing that I read.... https://helpcenter.nakivo.com/User-Guide/Content/Backup/Creating-Proxmox-VE-Backup-Jobs/Backup-Job-Wizard-for-Proxmox-VE-Options.htm And then I read "NAKIVO Backup & Replication allows you to run custom pre-freeze and post-thaw scripts on Linux-based VMs to enable application awareness." but the wording is somewhat ambiguous. I read it as like the scripts themselves are on the Linux-based VMs, reinforcing what the KB article says. But for Linux they aren't on the guest VMs - they are external - but are only run on the Linux VMs. Better wording might be something like "NAKIVO Backup & Replication allows you to run custom pre-freeze and post-thaw scripts stored with the Director. These are then sent to the Linux-based VM for execution as part of Application Awareness. Note that it is only FreeBSD hosts that must have scripts stored on the VM itself - see below for details". Anyway I highly recommend updating or just removing that old KB article if it is no-longer relevant. It was last modified in 2021. ---to be continued.... Quote
Gavino Posted September 5, 2025 Author Posted September 5, 2025 How does Nakivo separate Windows and Linux Director-based scripts? I don't want to reference Linux scripts in my mixed Linux and Windows job, and have it foul up Windows. A huge improvement would be to copy what you do in the Schedules section but for scripts. Have a "Add Job Scripts" button, and then out pops what you have now with the pre and post script buttons. But the difference is, you can now state which VMs the scripts apply to. Add you can add multiple Job Scripts sections. Quote
The Official Moderator Posted September 5, 2025 Posted September 5, 2025 6 hours ago, Gavino said: Thank you. The main source of confusion is this legacy page: https://helpcenter.nakivo.com/Knowledge-Base/Content/Application-Awareness-Issues/Application-Aware-Mode-for-Linux-VMs.htm?Highlight=pre-freeze-script That is the knowledge Base article for Application Aware Mode for Linux VMs - exactly what I was investigating. On my Linux VMs I was doing what it says there which is "put the custom scripts called pre-freeze-script and post-thaw-script into the /usr/sbin directory " and every time I did I was getting errors about not finding the scripts. Unfortunately my Google search brought that page up up first, so I was confident that scripts had to live on the guest VM. It was only after that, that I read the link I originally posted .....to be continued... In this case, these are different scripts. Scripts that are configured in a specific job (pre- and post-job scripts) are located on the NAKIVO director. They are initiated on each job run and do not depend on a specific VM inside the job. In case the script should be executed for some specific VM only, this VM should be located in a separate job. Also, these scripts should consider the OS on which the NAKIVO director is installed. Mentioned "pre-freeze" and "post-thaw" scripts are located on a specific Linux VM OS level, and they are initiated by VMware tools on the VM OS level when a VM app-aware snapshot is created by ESXi. In most cases, it is enough to create an app-aware snapshot of the ESXI level to have a consistent backup. Creating specific scripts could be necessary only for some VMs, that contain more sensitive data or services and such VMs could be split to separate jobs. Please clarify in detail your use case for a more detailed analysis and answer. Quote
Gavino Posted October 11, 2025 Author Posted October 11, 2025 (edited) Thanks I am fine with all those now. I was initially confused about script locations, but I now know that the Linux pre and post scripts are placed on the Director, and for pfSense/FreeBSD, they are on the guest VM. For my pfSense scripts, I just force a filesystem flush to disk. Seems to work for me. For the Linux ones - I haven't actually used them as backups seem to coalesce fine without them. I was thinking of using them to stop two docker containers (unifi application, and unifi database for said application), but I'd only want this for a single VM in a backup job of 7 VMs - which is a problem as the scripts apply to all VMs in the job, and I do not want to create multiple jobs. As a customer using this product regularly - I don't like the idea of attaching pre-post scripts to the whole job. I have 3 Windows, 3 Linux and a pfSense/FreeBSD guest in a single job, and that works very well. But the script situation is not good. Imagine if I wanted different scripts for every VM - I'd end up with 7 different backup jobs. That's just crazy. If I was designing this product, one of the first things I'd do is separate that out. I mocked up my idea for this: Within Data Protection you'd have Jobs, and Job Scripts. Jobs are your regular backup jobs as per usual. Job Scripts are a new concept. They can have a pre and/or post script file (at least one). The scripts can be edited right within Nakivo. The folders are user-created, but I have separated them out based on OS to show how I'd use them. You could then attach a named Job Task to a job, which would then be the default for every VM of that Job. You can also attach them to individual VMs of a Job. Attaching to a VM would overwrite any Job Script attached to the Job. Pretty simple concept. Shouldn't be too hard to implement. Edited October 11, 2025 by Gavino Quote
The Official Moderator Posted October 14, 2025 Posted October 14, 2025 On 10/11/2025 at 8:34 AM, Gavino said: Thanks I am fine with all those now. I was initially confused about script locations, but I now know that the Linux pre and post scripts are placed on the Director, and for pfSense/FreeBSD, they are on the guest VM. For my pfSense scripts, I just force a filesystem flush to disk. Seems to work for me. For the Linux ones - I haven't actually used them as backups seem to coalesce fine without them. I was thinking of using them to stop two docker containers (unifi application, and unifi database for said application), but I'd only want this for a single VM in a backup job of 7 VMs - which is a problem as the scripts apply to all VMs in the job, and I do not want to create multiple jobs. As a customer using this product regularly - I don't like the idea of attaching pre-post scripts to the whole job. I have 3 Windows, 3 Linux and a pfSense/FreeBSD guest in a single job, and that works very well. But the script situation is not good. Imagine if I wanted different scripts for every VM - I'd end up with 7 different backup jobs. That's just crazy. If I was designing this product, one of the first things I'd do is separate that out. I mocked up my idea for this: Within Data Protection you'd have Jobs, and Job Scripts. Jobs are your regular backup jobs as per usual. Job Scripts are a new concept. They can have a pre and/or post script file (at least one). The scripts can be edited right within Nakivo. The folders are user-created, but I have separated them out based on OS to show how I'd use them. You could then attach a named Job Task to a job, which would then be the default for every VM of that Job. You can also attach them to individual VMs of a Job. Attaching to a VM would overwrite any Job Script attached to the Job. Pretty simple concept. Shouldn't be too hard to implement. Thank you for the details and explanation. We have created a feature request for our Product Team to improve the processing/execution of scripts. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.