Installing .deb file on Mint 22

Topic

New Reply

Having a tough time getting the Veeam backup app installed since updating to 22. The frustrating part is that I have done this several times previously on older OS’s.  While trying to cover all bases, I re-installed the Mint OS and downloaded the file using Brave- the original 22 install, including Firefox, seemed to have some odd behaviors.  Point of reference- the completed Veeam install should look like this in Synaptic:

Using the GDebi installer directly on the downloaded file installs just the root app without the dependencies.  Next tried CLI and couldn’t get the correct syntax to run the installation.  The sordid details:

Hoping someone here who’s more familiar with the Terminal could quote the exact commands to get this app installed with dependencies.

Reply | Quote

Replies

Perhaps this will help (be sure to use the commands for Debian/Ubuntu):

https://helpcenter.veeam.com/docs/agentforlinux/userguide/installation.html?ver=60

1 user thanked author for this post.

Slowpoke47

Reply | Quote

[Ascaris]

When you attempt to download it from the repo, you don’t use the whole filename. You use the package name:

sudo apt-get install veeam

Doing that from Synaptic should do the same thing, though they differ a bit in handling errors when they are encountered. The command line will often give you more information about what went wrong in that case, and can offer solutions when Synaptic just fails.

While trying to cover all bases, I re-installed the Mint OS and downloaded the file using Brave- the original 22 install, including Firefox, seemed to have some odd behaviors.

What are the odd behaviors?

 

 

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

• This reply was modified 5 months ago by Ascaris. Reason: Fixed error in the command line (omitted 'install')

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Ascaris wrote:

When you attempt to download it from the repo, you don’t use the whole filename. You use the package name:

See attached, tried several times to get Veeam via Terminal, all failed.  In some cases, message was “missing operand.”  Several times attempted downloads from Veeam site failed, listed in Downloads directory as incomplete.

Ascaris wrote:

What are the odd behaviors?

On some sites, settings revert to defaults.  Email account (Fastmail) displayed erroneous time stamps, off by several hours (cured by Mint re-install), also when new emails received, the message pane auto-scrolls 8+ entries down.  Occasional 403 and 404 errors on Firefox, “you don’t have permission…” same sites open as expected on Brave.  Haven’t seen this last one since re-install.  On Ask Woody site, the “notify me…” box usually (but not always)  unchecks itself (still happens after the re-install).  Probably other one-time oddities that I don’t recall.

Reply | Quote

Eek!

I made a mistake in the command I suggested.

It is meant to be ‘sudo apt-get install veeam’

Somehow I deleted or plain forgot the install operand. I will fix it in the message above to avoid future confusion by anyone who encounters the message, but yeah, it was my error.

I am not sure about all of the other behaviors you mention, but those things would not have anything to do with Veeam. It seems to all be browser related (cookie deletion would cause the things you describe; do you have an addon or have you set the option in Firefox to delete cookies?).

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

1 user thanked author for this post.

Slowpoke47

Reply | Quote

See the link below for “Installing Veeam Agent for Linux in Offline Mode”. From your screenshots, believe you need to follow directions only for “Veeam Agent for Linux (with Kernel Module)” and “Nosnap Veeam Agent”. The third option “Nosnap Veeam Agent for Linux on Power” is only for “IBM Power Systems”.

For each scroll down to the bottom of their respective webpage to see the commands for Debian/Ubuntu. Note the reference below the list of commands: “where: <…> — path to a directory where you have saved Veeam Agent packages”

https://helpcenter.veeam.com/docs/agentforlinux/userguide/installation_offline.html?ver=60

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just now able to get back to this- have 4 downloads:

But not sure which of them will produce a functional Veeam app.

A dumb question- is the proper syntax for the path to the downloaded file

/home/steve/downloads/<file name>?

 

Reply | Quote

Downloads may or may not be capitalized on your setup. Remember that Linux is case sensitive (Windows isn’t), so you have to use the same capitalization for it to work. You would have to check and see if that is the correct location on your system to know for sure.

As for those four downloaded files… you have two that are marked “all” and two that are marked “i386.” The recent versions of Mint should be 64 bit only, so you would want to download the x64 versions of those two files that currently have “i386” in their names.

The 64 bit versions may also be called amd64 even if you do not use an AMD CPU, and this is because AMD wrote the 64 bit extensions to the original x86 (32 bit) instruction set.

On my PC, I have the packages “veeam” (amd64), “veeam-libs” (amd64), and “blksnap” (all) installed. For a Linux version with a recent 64 bit kernel, this would be the setup you want.

The package “veeam” has those other two packages as dependencies, so if you attempt to install “veeam” offline with those other two not installed, it will fail. The best way is to install them all at once, which is what ‘sudo apt install veeam’ would do (you can also use apt-get, but apt is generally preferred now). That will automatically pull in the two dependencies and install them.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Deleted previous Veeam downloads, then started from scratch via Terminal:

Was I meant to have the correct files downloaded for this to work?

Reply | Quote

Another attempt, same pc:

Reply | Quote

Veeam is not in the standard Ubuntu or Mint repos. The Mint repo is installed with a .deb file that you would need to install first.

If you visit this URL with your browser, the download of the repo .deb should begin automatically:

https://repository.veeam.com/apt/stable/amd64/veeam-repo_1.0.0-13_amd64.deb

Once you install that, you can then install Veeam from the repo and have it updated in the normal way.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Ascaris wrote:

Once you install that, you can then install Veeam from the repo and have it updated in the normal way.

Installed that file, 2nd attempt- 1st attempt displayed error message, additional file needed gnupg2.  This file offered in Synaptic search along with another- devscripts- installed both, then installed the file in your post.  New attempt at Veeam install failed:

In the s/shot, the first attempt was before the gnupg2 install, the second was after.

Reply | Quote

Some progress, but can’t get past this screen to set schedule:
Tabbing to “next” brings me here:

Selecting “OK” brings me back to the previous s/shot, selecting “Advanced” offers encryption but I can’t get to “Schedule”.

 

Reply | Quote

Slowpoke47 wrote:

I can’t get to “Schedule”.

UPDATE:  after floundering around awhile, got past the “Schedule” screen, b/u now running.

Reply | Quote

Aargh, spoke too soon.  Had one good “test” update a couple of days back, today backup attempts fail with a message “warning” or “failed.”  No clue why, same pc, same destination, same everything.  But a tech agent on the Veeam blog suggests that Mint 22 is the problem, as it is not officially supported.

But if true- why did it work the first time?

 

Reply | Quote

Further efforts- first 5 to HDD used previously, 6th to alternate target (64GB stick).  Note the widely differing elapsed times. Neither target medium shows any data.

Reply | Quote

I doubt there is any compatibility issue with Mint. It’s very much Ubuntu beneath the surface.

The backup finishing with warning is still okay in those screenshots. It is just telling you that it expected to be able to do an incremental backup but did not find the old backup set, so it did a full backup. That happens to me too from time to time, when I have changed some thing that leads the program to not see my old backup. It would be possible to troubleshoot it and figure out why it is not recognizing the existing backup set, but generally I don’t worry about it and let it do its thing (I will clean up the old backups, partial or whole, later on.)

If the target media are not showing the backups, then it is probably going to the local folder where the external media were thought to be mounted (but were really not).

In case you are not exactly sure how this works, I will explain (and if you do know, forgive the overexplaining please!)

You have a root filesystem, signified by the slash symbol alone:

/

It is on your root volume (by definition). With a standard ext4 filesystem, all of the other drives will be mounted to the root directory tree (all of the folders on the root volume, like /etc, /home , and so on).

For example, if you plug in an external drive, the system will usually be configured to automount that drive. If the external drive is called extHDD, that means it would be mounted to /media/steve/extHDD (remember that Linux is case sensitive).

The /media folder is on your root volume. Within that, the steve folder (/media/steve) is as well. When the system automounts your drive, it will attempt to create a folder within /media/steve, usually using the name of the external drive. So in this case, it would create /media/steve/extHDD as a folder on the root volume. Having a folder there is necessary to mount something to it.

If creating that folder is successful, the system will then mount the root of the external volume to /media/steve/extHDD. Once that mount has completed, if you navigate to /media/steve/extHDD, you will be at the root of the external drive. That location is known as the mount point for that drive.

So at that point, you can specify that mount point as a target for your backups. That usually works pretty well! But sometimes a mishap occurs, and rather than guessing that something has gone awry and telling you about what it thinks may have gone wrong, it just does what it is told, which can result in unwanted results.

Remember when I mentioned that when automounting, the system attempts to create the folder in /media/steve that is the same as the name of the external drive? If there is already a folder there by that name, a leftover from a previous mount perhaps, it will not be able to create a directory by that name, so it will add a 1 on the end of the name and try again. ‘extHDD’ would become ‘extHDD1’, and it would mount your drive there. If that also fails, it will keep adding to the number until it gets one that works. You would still be able to use the drive from its icon in the file manager without noticing any difference.

The problem is that when it comes time for a program that has been told to expect the drive at a certain location, it might not actually be there. Veeam will find the /media/steve/extHDD folder (we know it is there, because its presence prevented the automounter from being able to mount to that location), and it will try to write the backup into that location. But in this case, it is not your external HDD at all… it is a folder on the root volume!

That is why you sometimes get a message that you cannot back up because the target location would be in the backed up data. If you tell it to back up your root volume, but the target for the backup is on that root volume, it won’t work, because it would be an endless loop. When it comes time to back up the location of the backup, it would keep going forever, because the backup file keeps changing, meaning it has to be backed up again… forever!

If your intended backup did not go to where you thought it was going to, it must have gone somewhere else. You can move that backup to the desired location manually, but if you have the time, it is easier just to delete the backup that is in the wrong location, make sure the place that the automounter would mount the drive is empty (inside /media/steve, there should not be anything when there is no external drive attached), and then plug in the drive, make sure it is mounted where Veeam expects, and let it do the backup again.

You have made a lot of progress by yourself… you’re getting better! My apologies for sometimes taking so long to reply (feel free to direct message me if you need a quicker answer… I see the notifications for those right away).

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

2 users thanked author for this post.

Elly, Slowpoke47

Reply | Quote

Two successful backups now completed.  Looks like I’m back on track with this.

 

Reply | Quote