f our projects after moving servers will be to clean up permissions and remove the full control.
I used robocopy a year or so ago to do just this. There is an option in robocopy that allows robocopy to run as the backup service to copy the data to the new location. This solve any issues I had with my admin account not having access to files on the volume I was moving.
robocopy /b = backup mode (if you don't have permissions, restart the copy of that file using the backup account)
The backup mode parameter worked like a champ. Thanks again for the help.
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.
If the only goal is an open source file server (we call this a SAM-SD, there is a section of the forum just for that) then the most likely recommendations for an OS will be openSuse Tumbleweed or Fedora. CentOS and Ubuntu are fine choices too. FreeBSD is excellent, but less well known.
You make it sound as though the wise choice here would be to install OpenSuse etc direct to the hardware.
@scottalanmiller let's assume that we get direct application access from Word/Writer into SP or NC, how do you send a link to someone else so they know they have access? How do you register that 'link' in some way so that the correct application launches when trying to open the link?
How do you do it today? Why would it need to change at all?
Paying particular attention to Gene's wording, there would be no more files, only data in a DB. In that case, to send the information via email would mean extracting that data into some kind of usable format then emailing it.
So the contents of the file are simply sent as a file.... that's all a file normally is, a database holding text directly on it with a label on it with the filename. So.... literally nothing changes here under the hood. There is no more or less extraction than before.
You were weren't talking about getting rid of docx files and xlsx files, etc?
Yup, and still am. No files, but that doesn't mean that you can't have a file "view".
But OneDrive, etc still store those things as objects, I don't think you can edit the 'Word.doc' file directly inside the DB, you need to send that object of data to Word to edit it.
As objects, not as files. I don't need to pull the files from OneDrive to edit them. I can talk to the database directly with MS Office 2013 or later, even the online version.
Yeah Office is a bad example because of the massive integration.
Or a good example because it shows how easily it can be done and how well people can't even tell.
LOL - yeah, but you are limited to only MS based files, All other files are just stored as objects in the DB.
Are they? I'm not sure of that. But that's always going to be the case. File systems are for ad hoc, unplanned files. The real question should be... why do such files exist in your environment? When do you actually want ad hoc file types that you didn't expect?
Actually Sharepoint does not natively interface .doc files either. It only uses the new format .docx files in the manner you are saying.
Don't I know it.. I was playing with SharePoint and damn if I didn't have all kinds of problems with DOC files.
It is not uncommon to only have servers approved to access the storage listed. So many shops will go in and add a server one by one to enable access. If your servers almost never change, this works pretty well and is extremely secure. You can do this in the firewall too, for even more security. But if you are using DevOps and creating and destroying VMs regularly you will want to automate this in some fashion.
@DustinB3403 Thanks for your help! NFS is case sententive, it is mounted now! :D
Everything outside of the Windows and DOS worlds is case sensitive. SMB, NFS, URLs, file names, passwords, usernames, everything.
Thats what bugs me about Linux ... I hate case sensitive things.
I'm the opposite, I can't stand that DOS can't tell two characters apart and has "close enough" syntax so that people become sloppy and begin to lose the concept of congruency. I remember dealing with a bunch of students and getting them to understand things like "This", "this" and "t h I s" were not congruent was a real problem. Windows teachers users that exact doesn't mean exact, not always.
I think that is why I like cisco's ios software... i don't have to type the full command... just enough to distinguish it from the other commands available.... I see the benefits of case sensitive, it just will take me a bit to get used to using it as I learn Linux.
Looping back to this, in the past month I've worked with three different companies that all experienced significant data loss or downtime because of their choice of FreeNAS. Two suffered from not having front loaded their engineering and had an inability to support their servers during routine operations and caused major outages because of it along with significant cost for repairs, and one company that lost its data because of unnecessary bugs in the FreeNAS GUI code that would have been avoided has they been simply on FreeBSD.
Additionally this past week FreeNAS 10 "Coral" was demonstrated to be so incredibly unstable a month after being released that they had to recall the release and revert to a "beta" status indefinitely. For a trivial end user application this would be bad, for a critical storage infrastructure component on which companies need to have rock solid faith, it's unthinkable.
Those little Atom processors that they tend to use (I miss the Sparc32 days, it was just more interesting) use very little electrical power and produce very little heat and tend to last for forever. Pretty much unbeatable.
Let's talk about the actual storage you choose for these machines.
Can be a lot of things: local drives, OEM drives, non-OEM drives, FusionIO cards, Winchester drives, SSD, hybrid arrays, DAS attached chassis... because it is an approach and not a product it is very flexible.