|
Beets me.
|
|
|
|
|
Someone should!
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Yes please.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Argh. I'm seeing red, although I should probably be green with envy.
/ravi
|
|
|
|
|
... weird ... can't seem to quote any signature words ...
(shoots self in foot with felt hat)
|
|
|
|
|
invented red to eat capt then blue to eat ration then should we eat orange? all you can
|
|
|
|
|
yes, because the word comes from the fruit.
|
|
|
|
|
|
That color would be called orange.
|
|
|
|
|
I've got an orange tree in the garden. It's more green and brown than orange.
veni bibi saltavi
|
|
|
|
|
Yes, we would call them #ffe033.
|
|
|
|
|
Orange is not called as "Orange" because of colour. The colour comes after the existence of the fruit Orange.
|
|
|
|
|
Wasn't the colour named after the fruit*?
I'm pretty sure that "orange" is a new colour, which used to be just a red.
* Or we may have taken it from the Dutch royals ("oranje"), who used it as their colour, but who wants to admit that?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The real existential question you should ponder:
Why is a carrot more orange than an orange?
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Yes - the colour gets its name from the fruit, and not the other way round. It came into English from Arabic via Spanish - it was Naranja which mutated into Norange in English, where a norange became an orange.
Therefore the fruit would still be an orange, but the colour would be different.
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
This will probably be long. But I'm gonna try to keep it brief nonetheless.
I have a system I essentially use as little more than a NAS, providing other systems on my LAN access to files via a share. Whenever I buy hard drives (eg, I've outgrown the storage capacity of what I currently have), I buy new drives in sets of 3:
a) One in the "live" system, powered on 24/7
b) One in an external USB3 enclosure, kept offline and physically disconnected unless I'm actively doing a backup and
c) One in a second external USB3 enclosure, that I keep off-site and swap with drive (b) above every month.
I'm a big believer in keeping things simple, so I just use robocopy in a batch file to sync changed files from the live disk to the backup drive. I only back up data files (nothing from the OS itself or executable files from running programs), so attempts to copy files while they may be in use and all that sort of crap is no concern. This has worked great for me for years.
A little while ago I found out I have a file that somehow got itself corrupted. The file is physically "ok", in the sense that it can be read and copied without any sort of file system error--it's the software that last wrote to it that managed to write bad data somehow and made it unusable--the content can no longer be parsed, and in fact the size went from a few hundred MBs down to a few dozen KBs. Clearly, something's gone horribly, horribly wrong and this file is simply no longer usable. There's nothing in it to recover--no need to even try.
Here's the real problem: I rather rarely need to use the file (which doesn't negate its importance), so the corruption happened a few months ago. During that time, I had plenty of time to back up that corrupt file over the last backup set, as well as the one from the disk I keep off-site. It's only when I happened to need the file that I realized the file was corrupt...along with the last two backups.
People always say you need to backup, but also verify everything can be restored. That's great and all, as it proves the content can be read back when you need it and the file system integrity has not been compromised. That does nothing, however, for the integrity of the content of a file. No backup/verify strategy can help address this - the bits in the file from the backup match the source and it can be read back. That's not the problem that "backup but verify" addresses.
My backup drives aren't large enough to keep complete copies of multiple backup sets "just in case" I need to go back to an older version. And I'm not going to keep buying additional hard drives every few months just so I have a few "snapshots in time". Again, how far back do I need to go?
What's the best strategy here? I guess what I really need is versioning applied in some fashion (and volume shadow copies kinda exist for that purpose), but because MS has still so far put so little effort into integrating this in the OS so it's actually usable, trying to use that goes against my attempts to keep my backup mechanism simple. I've had someone suggest running Git locally (ha!), but where do I draw the line as to what files to include? Essentially I'd want to include the entire drive--what would be the point of keeping multiple versions of only a subset of them?
So again...what's a good, simple, and cost-effective way to address this?
|
|
|
|
|
Windows Backup.
The workstation version afaik only addresses you libraries but server version will image everything even ms exchange back to a bare metal drive like nothing bad never happened. Continuous historical file by file restore too.
For complete and bare metal restore of windows workstations I like Acronis true image to usb drives.
|
|
|
|
|
Has Windows Backup evolved enough to let you browse the file system as it existed at a given point in time, and then let you restore the one file (or subset of files) you want?
That's really the problem with all backup systems I've encountered (and gave up on decades ago and haven't looked at since), where they produce a single huge binary blob you can't manipulate yourself but have to restore as an "all-or-nothing" deal...
|
|
|
|
|
How To Extract Individual Files From a Windows 7 System Image Backup[^]
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Oh, cool. I didn't realize Windows Backup was saving stuff in VHD files nowadays. I'm very much familiar with the process of mounting them "manually".
Looks like I have some thinking to do, to figure out how I want to use that to my advantage here...
|
|
|
|
|
Yes we do it all the time when our customers delete that one file. Or a whole folder.
Acronis can do that too. pull single files and / or folders from image archives.
|
|
|
|
|
Windows backup "needs" to reformat your backup drive with a format that won't display in explorer anymore - just in the backup / restore program and in disk management. Merely visually alarming. Otherwise it works a treat.
|
|
|
|
|
That's a little disconcerting. I'm ok with Windows Backup creating VHD files like any other; I handle those all the time. Either what you're saying runs contrary to this, or I'm confused.
|
|
|
|
|
I believe use the system you already have but add differential or incremental backup. In other words, do a full backup weekly or monthly and differential/incremental backups daily. I believe Windows Backup does this. A differential/incremental backup will backup only what has changed and will allow you to restore to a certain point in time. A google on "Versioning Backup" or "Differential Backup" will provide a wealth of info.
The difference between incremental and differential backups are explained here: Incremental vs differential backup – what is the difference?[^]
You could also use online backups like Carbonite and Crashplan that will backup a file anytime it is changed and keeps those versions around for a month or more.
In the end though, none of this will necessarily save you from software that corrupts your files. Unless you test critical software data periodically or you keep backups to the beginning of time.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
modified 3-Dec-16 12:34pm.
|
|
|
|
|
I do similar but 3x weekly, I run robocopy with /MAXAGE:8 to a directory like /evenmonths/2016/Dec/Week51, on a Samba server. Monthly gets the last 2 years and yearly gets it all. Small data share, only about 100GB so it is all manageable and can keep for the whole year and then shelf it. Weekly backups are about 200 meg. Monthly stuff is 4 servers (VM) via Veeam along everything needed to recreate all servers, then taken off site. Veeam will also restore individual files/folders. I run the free version with a script and back up (6) VM's twice a month. Like you, all are also copied to external drives. I use RDX that are ejected by the VBS script after the copy over.
We issue new tin foil hats monthly.
|
|
|
|