Alternately, if you ssh to the host and have X11 forwarding enabled, your $DISPLAY may automatically be set to something like "localhost:10", representing your SSH connection and it will tunnel the traffic over the connection. This is in the form of "HOST:SCREEN", where HOST is your hostname or IP address of the X display, and SCREEN is the number associated with the display - this is usually 0 for most direct usage.
You need to set the $DISPLAY variable to point to your X display (MobaXterm). Note that I have not tried this specifically. But if you are running MobaXterm in single window mode, you could possibly do it like a VNC session. When you are running MobaXterm, you already have a desktop GUI on your local system - running another one would be strange. Part of the problem is that most of the desktops are easiest to run on the console itself, or a local virtual frame buffer like VNC.
(if you were trying to get it working on the console, you need to set the default boot target - not 100% how to do that on Ubuntu.) I assume you are talking about having a desktop, but remotely displayed on your local system running MobaXterm. This is why I said it may be easier to simply learn to use the terminal better GUI over SSH is potentially one of those rabbit holes(time sinks).Įdited to more clearly articulate the point I was trying to make. Holes that once you go down, you have to go deeper, and deeper, and deeper, until you find your problem, and the time spent tracking these issues down can grow exponentially. You may find with some experience that Linux has a number of rabbit holes.
Most people think they have backups and then find out too late that the plan was insufficient resulting in loss. Even knowing the answers to these type of questions wouldn't get you close to 100% redundant but it would address the more common failure domains. The questions aren't fully comprehensive but meant to guide towards a stronger methodology.
There are tradeoffs for every decision in a backup plan (referred to as a Business Continuity/Disaster Recovery plan at the professional level). How do you save as little data as you can, while having enough to restore fully and doing it with the least amount of labor in the least amount of time. In my opinion there is nothing worse than losing everything, and not knowing how you could have done things differently to prevent it.Īt its core, backups are all about cost and risk management. With that you should be able to google more appropriate questions since much of what I mentioned is foundational which can be useful to a technical person who is at an intermediate level of skill.īy addressing those questions, you potentially don't have to address the various problems you'll encounter related to them and be able to handle most failures.
I do this for a living so most of this is what I'd normally ask a Junior Sysadmin putting this together.
No worries, feel free to refer back to it as your understanding progresses, or ask questions. Ideally once the server is set up you want to have the bare minimum amount of interactive time spent maintaining the system needed for it providing the benefit.Īlso, you may want to consider looking at the tried and true 3-2-1 backup strategy. Is the data a mix of static (unchanging files) and content you want to back up? How much backup space do you have in comparison to what's being backed up, how will you handle resource exhaustion, how long will it take to do the backup, how will you handle failures that come in unexpected ways? What about recovery? What happens when one or both are offline, or the connection fails midway, are they supposed to run the next time they are up? Getting it to work the way you want may be more difficult than just learning how to navigate via the terminal more easily.Īdditionally, have you considered how it will do those daily/weekly backups (pull|push) and how much data it will store? Are the backups a complete backup, differential, or some other strategy?ĭo you know what your RTO is, how do you intend to test those backups (backups fail all the time), and have you planned your data layout (to reduce duplication)?