Debian File Server File Recovery
-
@coliver said in Debian File Server File Recovery:
@JaredBusch said in Debian File Server File Recovery:
@Romo said in Debian File Server File Recovery:
@DustinB3403 said in Debian File Server File Recovery:
I've played with Turnkey linux, and its scary how easy of a process those guys have made those systems.
Sooooo EASY! You miss everything that you really need to know about the system in every case.
@scottalanmiller How would this be any different than using something like NETHSERVER? Aren't the use cases the same, people who want a simple web interface to setup linux servers without having the knowledge of how things are really set up?
I've not looked at turnkey but n i've not looked at turnkey bye nest server nethserver is for managing applications on the operating system not for managing the operating system
Normally I can understand your point... but damn this is difficult this morning.
I'm lost.
-
Having not used turn key, just reading this thread, it sounded like turn key was a full management layer on top of a base install for managing a server, something like webmin.
I was stating that nethserver is basically just a management interface for the individual services.
-
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
-
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
-
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
-
@dafyre said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
Ya it just annoys me ha. Everything else is named by purpose.
-
@stacksofplates said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
Ya it just annoys me ha. Everything else is named by purpose.
Our one server... it got names Zues. Of course we knew it was going to be just the 1 server for the foreseeable future.
-
@travisdh1 said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
Ya it just annoys me ha. Everything else is named by purpose.
Our one server... it got names Zues. Of course we knew it was going to be just the 1 server for the foreseeable future.
If you must use Planets, Greek gods, Mythical creatures, et al... Please make sure they are pselled correctly to avoid further confusion.
-
If you think that failing to map hostname to VM name is bad. At the bank we once had a server named something like 192.168.5.34. And no, that was NOT it's IP address.
-
@dafyre said in Debian File Server File Recovery:
@travisdh1 said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
Ya it just annoys me ha. Everything else is named by purpose.
Our one server... it got names Zues. Of course we knew it was going to be just the 1 server for the foreseeable future.
If you must use Planets, Greek gods, Mythical creatures, et al... Please make sure they are pselled correctly to avoid further confusion.
I don't understand the reason to do that over function. I'd much rather name a server WDS01 then Ptah01.
-
@coliver said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@travisdh1 said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
Ya it just annoys me ha. Everything else is named by purpose.
Our one server... it got names Zues. Of course we knew it was going to be just the 1 server for the foreseeable future.
If you must use Planets, Greek gods, Mythical creatures, et al... Please make sure they are pselled correctly to avoid further confusion.
I don't understand the reason to do that over function. I'd much rather name a server WDS01 then Ptah01.
Potato01
Cauliflower7
Aubergine4 -
@scottalanmiller said in Debian File Server File Recovery:
If you think that failing to map hostname to VM name is bad. At the bank we once had a server named something like 192.168.5.34. And no, that was NOT it's IP address.
O.o I didn't even know you could do that... I also can't imagine the number of problems that caused...
-
@scottalanmiller said in Debian File Server File Recovery:
@coliver said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@travisdh1 said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
Ya it just annoys me ha. Everything else is named by purpose.
Our one server... it got names Zues. Of course we knew it was going to be just the 1 server for the foreseeable future.
If you must use Planets, Greek gods, Mythical creatures, et al... Please make sure they are pselled correctly to avoid further confusion.
I don't understand the reason to do that over function. I'd much rather name a server WDS01 then Ptah01.
Potato01
Cauliflower7
Aubergine4Antidisestablishmentarianism1.375
-
@scottalanmiller said in Debian File Server File Recovery:
If you think that failing to map hostname to VM name is bad. At the bank we once had a server named something like 192.168.5.34. And no, that was NOT it's IP address.
LOL. wow.
-
@JaredBusch said in Debian File Server File Recovery:
Having not used turn key, just reading this thread, it sounded like turn key was a full management layer on top of a base install for managing a server, something like webmin.
I was stating that nethserver is basically just a management interface for the individual services.
Webmin is actually a part of whatever he used
-
@wirestyle22 said in Debian File Server File Recovery:
@scottalanmiller said in Debian File Server File Recovery:
If you think that failing to map hostname to VM name is bad. At the bank we once had a server named something like 192.168.5.34. And no, that was NOT it's IP address.
LOL. wow.
Oh, it was bad.
-
@wirestyle22 said in Debian File Server File Recovery:
@travisdh1 said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
@travisdh1 nope
![😕](https://mangolassi.it/assets/plugins/nodebb-plugin-emoji/emoji/android/1f615.png?v=3hrg7a1ige4 ":\")
Uck. Do you know the type of file system (xfs, ext3, ext4, zfs)?
ext4
I prefer xfs, that can be growth online. Always use LVM.
It's trivial to expand a volume with LVM: just add another virtual disk to the machine, pvadd, lvexend, xfs_growfs and you're done.
-
@Francesco-Provino said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
@travisdh1 said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
@travisdh1 nope
Uck. Do you know the type of file system (xfs, ext3, ext4, zfs)?
ext4
I prefer xfs, that can be growth online. Always use LVM.
It's trivial to expand a volume with LVM: just add another virtual disk to the machine, pvadd, lvexend, xfs_growfs and you're done.
Same here, XFS is our go to filesystem.
-
@dafyre said in Debian File Server File Recovery:
@travisdh1 said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@dafyre said in Debian File Server File Recovery:
@stacksofplates said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.
We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....
That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.
Ya it just annoys me ha. Everything else is named by purpose.
Our one server... it got names Zues. Of course we knew it was going to be just the 1 server for the foreseeable future.
If you must use Planets, Greek gods, Mythical creatures, et al... Please make sure they are pselled correctly to avoid further confusion.
That was taken into account.
-
@scottalanmiller said in Debian File Server File Recovery:
@Francesco-Provino said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
@travisdh1 said in Debian File Server File Recovery:
@wirestyle22 said in Debian File Server File Recovery:
@travisdh1 nope
Uck. Do you know the type of file system (xfs, ext3, ext4, zfs)?
ext4
I prefer xfs, that can be growth online. Always use LVM.
It's trivial to expand a volume with LVM: just add another virtual disk to the machine, pvadd, lvexend, xfs_growfs and you're done.
Same here, XFS is our go to filesystem.
It's the fastest, no-frills, fully-enterprise, best supported alternative.
I had issues with the latest BTRFS, till yesterday (unnecessary rebalance, cpu 100% etc). The ext family is good, but it was not designed for massive scaling or enterprise workloads.
ZFS on linux… no thanks.
JFS and others: not well supported.
