Tag Info

Hot answers tagged

19

Using -t (preserve timestamps) and --size-only will only compare files on size. If the size matches, rsync will not copy the file but since -t is specified, it will update the timestamp on the destination file without recopying it. Make sure to not use -u (update) as this will skip files that already exist and completely skip updating the timestamp. I had ...


15

Connecting your ntpd to NTP servers outside your LAN to time sync can lead to the inconsistencies you are seeing, because every connection will have to go thru several routers, each one with unpredictable latencies depending on traffic. If each server connects by itself, the time between all the servers will drift a little. To avoid the inconsistency, the ...


10

The reason people would run sync; sync before a halt is because the halt command wouldn't shutdown the system cleanly on older linuxes. The correct way to do this on SYSVr4 systems has always be to tell init to move to a different run level. BSD and SunOS 4 aren't SYSVr4 operating systems which is why they differ. Solaris (SunOS 5) is SYSVr4 and Linux picks ...


7

If you can trust the filesystem last-modified timestamps, you can speed things up by combining Rsync with the UNIX/Linux 'find' utility. 'find' can assemble a list of all files that show last-modified times within the past day, and then pipe ONLY that shortened list of files/directories to Rsync. This is much faster than having Rsync compare the metadata of ...


6

Put rsync in, coach. It was made for this game. It should do pretty much exactly what you need; big files will only transfer changed pieces, hash comparisons are done to avoid transferring unchanged files at all. You'll need some scripting around punching it through an ssh tunnel, but that should be trivial. It should be installed on most sane linux ...


5

Try unison, it was specifically designed to solve this problem by keeping the change lists (building file list), locally to each server, speeding up the time to calculate the delta, and the reduce amount that is sent across the wire afterwards.


5

DropBox.com ftw. Love it. PS - Be sure to get the optional Packrat feature turned on. Saves every version of every file FOREVER.


5

This link sums it up pretty well -- One call to sync should suffice. Doing it more than once is definitely a holdover (and one I stick to myself), but if you're doing it programmatically you aren't gaining anything - it's the delay it takes you to type out those 5 keystrokes that you were really going for. Of course the real answer is to officially ...


5

DRBD in Dual-primary mode with a Proxy is an option.


5

You can simply use rsync such as: $ rsync -au src dest Any of the src and dest can be written as user@host:src if it is not on the local machine. This uses ssh by default. You don't need root access if the provided user has enough permissions on both servers to read and write the files/folders.


5

You can use something like rsync with cron to mirror the files at regular intervals. The downside to this is that the synchronization is not realtime, but rather at whatever interval you set. If you need immediate syncing to all nodes in the group, you should look at something like DRDB. If you don't have root access, you'll need someone with root to set ...


4

The use of multiple sync calls was to allow the OS and disks time to flush the write queues. "sync; sync; sync" wasn't considered that useful; one did "sync<cr> sync<cr> sync<cr" and the delay while your ASR-33 did the carriage return/newline provided enough delay. Halt always did call sync; the question was whether there would be enough ...


4

I think I solved my problem. The trick was to execute: trac-admin /path/to/projenv repository resync '*' With that instruction, I could resync all my repos :-). Thanks for your help!


4

Keep in mind that DNS clients cache negative responses as well as positve ones. Maybe this accounts for some of the time you spend waiting on newly added records? You can configure the negative caching time on your clients: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNSCache\Parameters NegativeCacheTime value (DWORD). The default data is 300 ...


4

The simple answer is "set the date manually", which you need to do, but to prevent this occurring again, there is more that you should do. Ensure that the system timezone configuration is in a sane state. Unless there is a very strong reason not to do so (such as software compatibility issues), server clocks should always run on UTC time. If you decide ...


3

Have a look at SyncBack as a solution, there are three versions ranging between Free (as in no cost) and everything except the kitchen sink. Should cover most use cases. Trial versions are available for the paid for versions, and if you decide you need a feature in the "Pro" version it is $50.


3

Depending on the version of the server.. Could you use Distributed File System (DFS)? I think it requires Windows 2k3 server or later, and you'd probably have to have a forest set up encompassing both domains, home and office..


3

What you describe sounds like a very general solution, which might be impossible (e.g. you cannot have both offline access and completely avoid manual merging, e.g. for multimedia files). In addition to the other solutions, you might want to look at Unison. It will sync multiple directory trees to keep them identical after changes (particularly offline ...


3

You could roll your own using Net::FTP but helping you with that would require code from you. You could compile sitecopy using Cygwin. It works. But, I would first go ask at ServerFault before committing to either course of action.


3

You want to do database mirroring/log shipping : http://msdn.microsoft.com/en-us/library/ms187016.aspx. Here's an article by Paul Randal you might want to look at as well : http://msdn.microsoft.com/en-us/library/ee523927.aspx. That guy knows his stuff.


3

In my answer to this question, I suggested incron. It's easy to set up system-wide and user-specific config files in a manner similar to cron. You can specify scripts that will be run when filesystem events are triggered. It uses the Linux kernel inotify API. You might take a look at it and see if it works for you.


3

Set up a local Ubuntu repository and update your systems from that. Then you can only update the repository when you want to, and you'll know your production boxes will get the same code as development. Check out tools such as apt-mirror, and apt-cacher.


3

some dude from data center accidentally modify one of the web server date/time This is your first problem. It is most likely caused by a combination of: 'dude[s] from [the] data center' with insufficient training and Overly high privileges Changing system time requires administrative privileges. Changing the time manually on a system that not ...


3

Replication works quite good, and it's not hard to configure. The official doc (for 5.1) it's easy to follow.


3

install something like homebrew or macports to install rsync on the mac.. and use rsync rsync -av /path/to/folder/ username@IP_ADDRESS:/path/to/sync/with


3

This is difficult to answer because it's entirely dependent on your application. It sounds like you have some core application architecture issues that won't be resolved in a ServerFault question. With that said, there are some steps you can take to resolve the issue you described. The most appropriate course of action in a situation like this is to break ...


3

One approach would be to use Perdition for POP/IMAP connection handling and then just setup your Postfix to route SMTP to an old or new server, depending on where the user mailbox is located. This way you can migrate your server live one mailbox at a time without any downtime. Of course you can setup a scheduled maintenance break, and then just rsync the ...


3

If you really want to do this correctly you should deploy a domain controller in your datacenter and have your Linux systems authenticate against it (add the POSIX extensions to AD, and extend each AD account that needs Unix access to be a POSIXAccount). Trying to make AD subservient to another authentication/authorization store is exceedingly difficult and ...


3

Short answer: No Longer answer: you can use "svnadmin dump-transfer dump- delete repo -recreate repo - svnadmin load" path, but it's nightmare PS: DVCS seems as more natural solution in your case


3

You shouldn't back up SQL Server databases from the filesystem level, it should be done by taking SQL backups and then backing up the SQL backup files. To remove the locks from the files you either have to stop SQL Server, take the database offline, or detach the database. If you want to replicate SQL Server databases you really should investigate one of ...



Only top voted, non community-wiki answers of a minimum length are eligible