Running Linux Mint Mate 20.3. Successful weekly backups for several years. Today forgot to connect b/u medium when starting veeam, got “warning” message in the “success” column. Tried exiting and restarting backup with medium connected, got another warning message.
Not sure what to do next.
Page 1 / 3
What version of Veeam are you using? What is the warning message that you are seeing as that would help? A screenshot or the exact wording. We need more details but if it is a warning it tends not to be a big deal but post what the message is first.
I show an app download:
This is from 2 years ago when I set up a new computer. I think this is the version in use. This warning was due to an error on my part.
I show an app download:
This is from 2 years ago when I set up a new computer. I think this is the version in use. This warning was due to an error on my part.
Ok. Are you able to run a backup successfully now? What caused the warning? Just asking so we can post the answer here to help others that may encounter it.
Are you able to run a backup successfully now? Not as yet. Note two warning messages- the first one was when I forgot the medium, the second was after I exited and reopened the app with the medium connected. Will try again now.
Are you able to run a backup successfully now? Not as yet. Note two warning messages- the first one was when I forgot the medium, the second was after I exited and reopened the app with the medium connected. Will try again now.
Ok let us know how it goes. I see the warnings in the screenshot but the actual message would be nice to see. I think you hit Enter on the message to show it.
Just mad 3rd attempt, saw “running” to 98% completion, then “warning.” BTW- there may have been a veeam update at some point, installed when offered, but I can’t get this system to show update history. Now that I know how, here’s the warning detail:
Just mad 3rd attempt, saw “running” to 98% completion, then “warning.” BTW- there may have been a veeam update at some point, installed when offered, but I can’t get this system to show update history. Now that I know how, here’s the warning detail:
Still unable to see the full warning message. The backup is completing so to me the warning is a moot point and nothing to fuss about. Unless there is a storage issue with space and that is the warning? Hard to know without seeing the entire text of the message.
How can I see that warning message text? Any result other than “success” is new to me. I recall that older backups are deleted by default as needed. I could try a backup on another medium.
How can I see that warning message text? Any result other than “success” is new to me.
Cannot continue with this today. Back tomorrow. Thanks for your replies.
Cannot continue with this today. Back tomorrow. Thanks for your replies.
Not a problem and hpefully you can determine the warning.
Hi @Slowpoke47 -
You can export a log with the following cmd: veeamconfig grablogs
Then, you should be able to view the file (which gets save in the current working directory) by first unzipping it: tar -xvzf <name of file>.tgz
Then, use “cat” cmd to view the log file: cat <job-name>.log , assuming that’s the name of the Job log file.
As Chris shared, it does look like the Job succeeded, but am curious what the warning is….warning could be something like running low on Repository storage where your backups are stored.
Thread starter here- a little more info… system is updated to v. 6.1.2.101.
Yesterday I uninstalled and reinstalled the Veeam app- so, started from scratch. All good during setup, until trying to assign a path to the removable HDD backup target. While in the past IIRC this step was automatic, I now get an error message on various attempts to do this. Also, the browse option doesn’t correctly identify the disk to Veeam either. Can someone tell me the correct syntax to ID the drive to Veeam?
Notice that in this s/shot the elapsed time of the “warning” items are double or more of the “success” items.
See if anyone has encountered the error there and if you need support once you create a support case this is the better place to get assistance.
@Slowpoke47
When you add a folder path in Linux, you generally use the “/” as separator instead of “\” used in Windows. Try that. Another thing to keep in mind..as your typing in the path in Linux..you should be able to use the Tab key to “complete” the name of a given folder or file in your path. So for ex., if you want to progress to /tmp/folder1/folder2/file.txt , you can type /tmp/fo<hit Tab key and it will complete the folder name here>/fo<hit Tab key again to complete the name>/fi<Tab> . Doing this does 2 things → saves typing cramp ..and helps prevent typos when entering a long filename or folder path.
I don’t recall if Agent for Linux itself allows “tab-completion” or not. You might have to type the path out manually. And, I don’t know Linux Mint with MATE (desktop). Anyway..just some (hopefully) extra helpful info when using Terminal/cmd-line.
Also, your error in the screenshot says to not add “sda” to back up. This is basically (most times) your OS disk. Now, this isn’t an option to do (exclude sda) if you only have 1 drive/disk and need to back it up.
If you aren’t/weren’t able to view logs, you would really need to get further assistance from Veeam Support. They do help (best effort) for free product usage. But again...keep in mind, Linux Mint isn’t a supported OS for Veeam Agent for Linux, so you might be at a road block there.
When you add a folder path in Linux, you generally use the “/” as separator instead of “\” used in Windows. Yes, I’m well familiar with that- Linux user for many years. What I don’t know is what to call the disk to satisfy the Veeam system. Tried the default identifier on the directories screen and the alphanumeric (long) identifier that shows in the top header as well.
If all looks correct, I don’t know what else to suggest besides reach out to Support. The error you’re seeing above says to exclude sda. And, I’m not sure what sda is for you or why Veeam Agent would suggest to not include that device.
OK, going thru the steps brings me to the attached screen:
Notice the disk name under “Devices”, left side, also see the alternate name across the top. Neither of those worked as the destination. I chose the name “Veeam backup” and Veeam picked it up, see terminal screen, but I can’t get it accepted and move on. None of the suggestions at the bottom will allow me to select OK or Create directory. Same with tab key. Various selections always bring me to that same error message.
This machine has been making weekly backups for a couple of years now, don’t understand
Hard to say the issue @Slowpoke47 . Again, you can attempt to view logs or reach out to Support.
Just to test, without running the actual backup Job, go back and re-select the scope of what you want to backup and don’t select sda. See if you can then finish the Job creation process.
As Shane has suggested at this point I would reach out to support as we have exhausted what we know and suggestions we can give you. Anything now is just a shot in the dark to try and help but if you want this resolved support is the best path forward.
Now trying to file support claim, can’t make anything happen with Severity field, so can’t proceed.
Now trying to file support claim, can’t make anything happen with Severity field, so can’t proceed.
Do you have a license or are you using Community Edition? If CE select that as it is best effort support as there is no severity only on paid support.
Do you have a license or are you using Community Edition? If CE select that as it is best effort support as there is no severity only on paid support.
Using free edition. Severity box outlined in red, but won’t accept input. “Next” button ghosted, unavailable