The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
For personal stuff, I have no backup/recovery plan. When I get a new system every 5-6 years, the personal stuff gets copied to an external drive for transfer so a worst case scenario of an unrecoverable drive failure after the first year would be irritating but not devastating.
Perhaps this is being naïve, but I have a lot more faith in the hardware these days, specifically SSDs. The only spinners still in use here are external USB drives. I just recently replaced the first 64GB SSD I bought for a server back in 2011...not because it failed.
Professionally, I have a pretty simple backup system using a server and a laptop. All important work related files are kept in shared folders on the server. These shares are mapped on the laptop with the 'available offline' option. At least once a week, the laptop synchs up any changes. If I need to use the laptop away from the office, all my files/projects are there and will update the server on the next synch.
This method absolutely saved my bacon about 3 years ago when the server's data drive failed. Even though I was able to recover all my development files, docs, etc. I soon realized that most of the sql databases being hosted on that server were lost...the log files and backups were on the failed data drive. In all, I lost a few months of customer support tickets which had to be re-entered.
That experience led me to create a nice little sql backup utility that runs a nightly or weekly backup storing/rotating copies on two different local drives as well as sending a copy to a remote ftp location. I won't be fooled again! It also has the benefit that if I'm working remotely, I or my colleague can get last night's backup from anywhere. Disasters should always be a learning experience...best when learned from others!
Yes, I have backups, then the backup NAS is backed up (to a device on a timer, so it is only ON during the backups, and cannot be accessed/activated outside of that time).
I have a pretty exact spare (Cold Spare) computer system. Swap SSDs, and I can reboot to that machine.
I have a second timer device, but have not configured it, for holding the SSDs to backup to. That is a project for the next 2-3 weeks for me. The goal is to have my C: and D: SSDs backed up to Fresh SSDs once a week, and that device turned off.
FINALLY, I test this from time to time. (once a year). And the PAIN Point is that it takes so dang long to restore the images to the new SSDs, that if the failure is the destruction of the SSD, I lose basically an entire day. [I lose about 1hr to swap the HDs].
Is this overkill? NO!
Last Summer my motherboard gave up the ghost. I swapped the drives and was up and running in a couple of hours (initial debug time, and then software license issues, ughh). And then I ordered a new spare from a refurbisher. Tested with cloned hard drives.
So, I am running on a 7yr old Dell, with a cold spare.
The problem is that the new computers barely support Double SSDs.
And Frankly, they are NOT that much faster! Although the USB and I/O Improvements are almost there.
Upon Switching, I will NOT have a cold spare (too expensive), I will have 24hr service for 2-3yrs, and then I will buy the spare vs. extending the warranty.
FWIW I use an external CD/DVD because the internals died, and I use them so infrequently.
At home, I back up all the non-redownloadable stuff on my NAS. I have two PCs, the stationary main one and an auxiliary laptop. The laptop doesn't have the environment set up but thankfully, Visual Studio takes care of pretty much everything by itself.
On office, all my stuff is on OneDrive for business. The environment is easy to recover as well.
it is a new kind of market analyse for such big companies...
Depending on how many people start yelling at the missing XXX, they determine how much likely are they users to sell their souls to them for peanuts.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
As you know by now, if you're still playing PE, our lobby server had an issue where all the code base got deleted from its server. After trying to fix it for the last month, we've arrived at the unfortunate conclusion that it's a lost cause unless we completely rewrite the code from scratch. We used a software called U-link for PE, and that software is now defunct. Even if we had the original U-link code, we still don't have the configurations and additional code we wrote back in 2013. Under the circumstances, we just don't have the resources to rewrite the multiplayer code for PE. We're truly sorry for this.
...but the devops slideshow I flicked through from clickbait times while doing a number 2 said I didn't need to have a sysadmin, what could possibly have gone wrong.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
Holy crap, I'm amazed at the "we lost teh codez during an outage" story, but even more amazed at the community who gave it 204 likes and were all like "Too bad, but thanks for the great times!"
Where's the poison and the hate?
I'm not sure if this restores my faith in humanity or if they've let me down yet again
Our source code is hosted online, so if someone manages to hack MS and delete it it would be gone. But as part of a larger team we still have local copies and could piece things back together. If that fails we could decompile some of exe files, although it won't work that well for the web front end. Guess it wouldn't hurt to have another full source code backup stored somewhere else.
For each build, we create a ZIP of the workspace (minus temporary files) and store it on a separate network drive that replicates to the DR site. (different than the build server and source control server)
As long as you have a laptop or workstation with the correct IDE, you can unzip the workspace and perform a patch in minutes if needed.
Last Visit: 31-Dec-99 18:00 Last Update: 23-Jun-21 17:24