# Backup Linux web server onto windows web server or DPM server/owner and also civil liberties in NTFS?

We are making use of a rsync based backup for our Lonux web servers which is superb. We rsync all our Linux web server onto our huge Linux base samba fileserver. However that web server is entirely obsoleted and also moved over to Active Directory.

Currently I'm stuck to the trouble to make step-by-step back-ups from the Linux web server. I specifically suched as just how rsync can replicate away changed or removed documents.

Currently I intend to do Linux back-ups onto Windows web server.

I considered backup remedy, yet mostly all were based upon rsync. I sought rsync for Windows (Cygwin or Microsofts SFU (solutions for Unix) ). Yet it feels like it will not suffice.

In order to appropriately rsync proprietor and also civil liberties one actually requires 2 integers and also some flags in the filesystem. While NTFS in theory gives that, SFU and also Cygwin actually attempt to map it to existng customers.

Additionally rsync for SFU appears to be unstable etc

On our existing web servers we simply uncommitted concerning any kind of mapping: As you recognize Linux web servers simply store 2 integers in the filesystem (in straightforward instances), no equipment details lengthy SIDs like Windows. What they suggest is specified by/ etc/passwd. And also if that is missing out on, it is simply integers. Yet if it comes back on the web server, it functions once more.

Has any person located an excellent soluton for this?

I also sought out UMSDOS, where Linux made use of to be able to be saved on FAT16!!! It made use of textfiles with lengthy filename mappings and also unix civil liberties and also features. However it has actually been gotten rid of create the kernel. Or else I can have placed a share on the new windows fileserver making use of CIFS - place and also layer umsdos in addition to it. However something like that does not exist.

Why do not I intend to make use of tar? Due to the fact that I actually like just how our DPM - web server would incementally backup our windows submit web server and also I do not intend to entirely backup an entire tar - documents of enverything!

0
2019-05-18 22:54:36
Source Share

So it seems like your actual concern is you intend to maintain proprietor and also team setups, yet have the information moved to a system that intends to map the setups to its very own. You additionally intend to maintain the marginal - information - transfer arrangement that you get with rsync, yet obtaining from "below" to "there" might take even more effort and time than what you intend to buy. Tar would certainly address this trouble yet it takes the whole photo of each documents as opposed to the deltas.

To sum up: You desire something that makes deltas of transformed information, yet maintains the features like tar, overlooking the location system is customer mappings (due to the fact that there are no common accounts).

The first (and also possibly unrealistic) alternative is to see if there is a backup customer for the system you are making use of in Windows. As an example, Retrospect consists of OS X and also Linux customers that permit a Windows equipment to support the documents with features affixed. My job has actually utilized this setup for a number of years, and also with the exemption of some I/O increases customer - side, it has actually functioned as marketed. See if there patronizes you can install on the Linux box that would certainly permit you to "link the void" in between both, and also you will not need to bother with this. Keep in mind: I saw you really did not upload what sort of backup remedy you are making use of, which suggests if you are making use of indigenous Windows Backup (ick) you run out good luck.

Open - Source Solution

Here is something entirely insane: start a Samba web server on the Linux side, produced a share for management usage (concealed, set up for admins just, etc), map the share or make use of a UNC course on the Windows backup web server, and afterwards do a backup from the share. Yeah, your SIDs will not match, etc (due to the fact that there is no mapping in between ADVERTISEMENT < - > passwd) yet that will not matter due to the fact that Samba will certainly do the translation for you , both throughout backup and also recover. The disadvantage is that you'll intend to make normal back-ups of the Samba.tdb documents to guarantee you do not shed any kind of setups, in addition to your customer maps in/ etc/passwd, etc You'll additionally intend to set up this share really meticulously , as the incorrect setups will certainly create the documents to re - map to various values. The principle below is that we are transforming Samba right into an unrefined estimate of a "backup customer" that can be accessed in a fashion that follows Windows. It additionally thinks that your backup software program will certainly care for any kind of delta/compression includes you desire ...

Unlike the business remedy, this has actually the included advantage of having the ability to collaborate with the constructed - in Windows Backup, as the share seems simply an additional Windows web server UNC.

The 2nd remedy has actually currently been stated by @Brent, and also deserves checking into. This would certainly be numerous actions up from the method I offered. As opposed to plagiarise his blog post, go and read it rather.

Homegrown Solution

One remedy would certainly be to divide the metadata (possession features) from the information, and also send both to the web server. Do to this, store the setups in a different dot documents, after that send the dot documents in addition to the materials. This would certainly permit you to make use of rsync (if you so pick) while maintaining the setups. As an included incentive, rsync will use the very same delta - transfer device to the dotfile too. Throughout a recover, you would certainly turn around the procedure by removing the setups from your dot documents and also using them to the directory site materials. This is time - consuming, and also throws away some disk room, yet it is straightforward (you have presence of what is taking place) and also sturdy (it is simply message documents, so it is conveniently dealt with), and also simpleness occasionally is the most convenient means, also if it appears "strength". I would certainly pick this as your last alternative. Not just will you have race problems (if you try to start the backup while the manuscript is running, will the dotfiles be upgraded in time prior to they are supported?) yet you additionally require to craft every little thing by hand.

You would just require 3 manuscripts - one to restore the dotfiles in each directory site for the setups, one to recover them, and also one to clean dotfiles when they are not desired.

On generate/create: Store a dotfile in each directory site that the dotfile comes from. The dotfile basically has an ls -la to make sure that the features are recorded. Set the proprietor of the dotfile as origin to maintain mischievousness to a minimum. After refining that directory site, have it return and also extract each directory site from the dotfile (a straightforward grep will certainly be adequate) and afterwards recursively enter into each subdirectory by having the manuscript call itself. When finished, the whole branch of the directory site you began in will certainly have every one of the dotfiles in position for each and every directory site. Run this manuscript before the backup to "restore" and also "rejuvenate" your setups, or when possible, run it sequentially in - line with the backup manuscript itself, to make certain that it finishes prior to the backup begins.

On recover: The recover manuscript would certainly reset all dotfiles to deal with possession (once more to shut out mischievousness), after that recursively refine the dotfiles in each directory site, recovering your setups for each and every documents. Each dotfile will certainly call for 3 passes, a masquerade proprietor - team - globe, a masquerade calling the proprietor, and also a masquerade calling the team. Submit ops are generally excusable so this need to be really fast, exposing large directory sites with waaay - to - several documents.

On cleaning: Simple, recurse each directory site getting rid of the dotfile.

Yes, it is a hideous hack. If I can locate a far better solution quickly, I'll re - edit. Till after that, it addresses the trouble.

0
2019-05-23 00:33:42
Source

Not certain if you are actually intending to remain with rsync, or simply maintain the advantages of step-by-step back-ups.

If you simply desire the advantages, a multi - system backup system (like bacula) could be an excellent remedy. It will just make step-by-step back-ups - if that is what you desire - yet it will certainly store every little thing in one (or a couple of) large documents (not a mirror of the initial). Once more, not exactly sure if that is what you desire or otherwise.

0
2019-05-21 07:47:42
Source