Policies and Procedures exist for a reason. I support this and will always try to work within 'the system', whatever that may be. If you find 'the system' isn't working. Take the steps necessary to improve it, and carry on. Wash rinse repeat.
To that end, my recommendation is to have the doctors get involved. Absolutely, beef up their security, have good intrusion detection, prevention and reporting. Get security to advise the doctors ahead of time about the planned 'attack', and report back the findings. Be the blue team defending, let them be the red team. Make sure you've done your job right.
I would consider this to be no different than regularly restoring your backup data. You do that right?
Well then the option should be explored to know what its outcome will be. Sure if "the nice government" says no, then no is the answer. But, and here's where an imagination comes in, what if they are swayed by logical arguments and understand that it could be beneficial to reuse resources that would otherwise have to be destroyed. New contracts can cause amendments to old contracts really easily.
I don't understand why you are discouraging the OP from exploring this option, and I don't really care either. You use terms like "was probably". Depending on the amount of effort it would take to find a definitive answer, it is normally worth while to turn that "was probably" into a known fact. Then action can be taken based on those facts.
The business solution is the have the original contract revised to not force you to destroy something you want to keep. You get the next contract, get them to keep the parts to save time, money, efforts, energy. If it works then your employer will see you as a multi-faceted resource with solutions from more than one discipline. If nobody agrees then stop working for someone who makes stupid decisions.
That's how I operate and I've never been fired, been promoted 4-5 times though.
Will it outrun a human on the open savannah or through an urban city? I know the TFA mentioned tight turns and immediate stop & go, but what about in a building, over a fence, through the neighbor's back yard, up the stairs, from one roof to the next? I'd really like to watch something like this outrun an urban freerunner.
Not because it's against any policy but as good internet citizens, if they cut my connection I'm going to ask why, I find out it's because I'm infected, I just have to clean the infection and I'm back online. Whose rights, freedoms, expressions are being affected in any way from this?
Most internet users (don't just think/. crowd) would appreciate this type of action. One ISP where I live had this policy in place 4-5 years ago and I helped my cousin get rid of virii that he didn't know he had until this happened. Some advanced uses might be upset, just like pirateers are upset when TPB goes down, but those people will find ways around and still be able to do what they want to do.
Most of the open access points I come across are proxied to some pay per MB or pay per minute credit card log in page. Not so open but still connected to the internet.
You don't have backup needs, you have recovery needs. Backup enables you to fulfill those needs. As has been mentioned many times above, there's no one fit answer - but I don't think you're even asking the right questions. Under what circumstances will you be recovering data? There are two main types of recovery: day to day recoveries where users want older versions of files or to replace a corrupt or deleted file; and disaster recovery in case of hardware, system or site failure.
Will you support both recovery needs? If so then for day-to-day recoveries you need backups every day kept for any length of time deemed appropriate. Proper tape based backup is still the industry standard here just based on the volume. 12TB at 75% used, running full backups every week kept for 4 weeks, and daily cumulative incremental backups with 5% changes every day kept for 10 days means 51.3TB of data. Plus, you don't want all your copies on a single media, imagine if that thing failed?
For disaster recovery you need to know your RPO and RTO? Your Recovery Point Objective is basically how much data can you stand to loose while your Recovery Time Objective is how long after the disaster you can take to get back up and running. Answering these will tell you how often you need to run a backup and what storage technologies and methods are appropriate, or at least which ones are inappropriate. How are you going to protect your data from the disaster - how far away is far enough? I wouldn't consider the same campus as far enough away.
There are a number of products out there. I personally work with NetBackup from Symantec and it's pretty much an industry standard, but that's my employer's choice. I've looked at amanda (http://www.zmanda.com/) a few times, but haven't done any real testing with it. There's data protector, BackupExec and many listed at http://en.wikipedia.org/wiki/List_of_backup_software
The briefness of the article and lack of actual functional analysis make me think this should have been a comment on the original/. article rather than a whole new article of its own.
With all the comments like "Predictably, Gears of War seems to get it right.", it seems to be more of a GoW praise article stating that this game has no flaws, but all the others do.
Also, the summary has a small error, article talks of games from 2007, namely GoW, not GoW2.
More crashes occur on the ground than in the air. In fact, according to http://www.planecrashinfo.com/cause.htm 62% of crashes occur on the ground, they're just usually the least fatal.
There's not a lot of risk in straight and level flight...
Someone from the Avalanche probably put in their old address when signing up for some online service and set the whole range to QC. As for fixing it, sorry, can't help you.
I offer to do my part and offer a backup copy of all the content I provide. If every content provider did these we'd be set./me takes tongue out of cheek.
For something that's only a year or so old (production wise), I don't trust it worth shit. We run Netbackup Enterprise on Solaris 10 - during our last round of upgrades we installed ZFS on our disk staging storage units. It replaced VxFS. The way disk staging storage units (DSSUs) work in Netbackup, the disk is always near 100% full form a unix perspective. Basically, any time more disk is needed, the oldest image that has been copied to tape is expired from disk, thus freeing up more room. However, ZFS's most prominent bug from our perspective is that during periods of high activity, if all blocks become allocated, it becomes impossible to unlink(2) a file. This causes the application to no longer be able to make space for new backup images.
Going down the shell, try to rm a file and it comes back: rm failed, disk is full.
Well, if the disk is full, and you can't rm because the disk is full, how do you free up space?
Sun's response, truncate an unnecessary file using 'cat/dev/null >/path/to/file', then, once you have some blocks free, rm works (so does unlink).
Ok - so how do you tell a compiled application to truncate an unnecessary file before unlinking it? You can't! How can you determine what an unnecessary file is? If you delete the image before expiring it from the catalog you get errors when you try to expire, so you end up with catalog corruption.
All in all, this is a problem that should never have been introduced, let alone still exist after months of sending trace outputs and reproducing it in multiple environments. ZFS isn't ready for the real world.
Not particularily. Processors already had drivers, an OS. So, who do you trust more to write for that processor, your OS provider or your processor provider?
But, M$ is making a loss on the sale of its console expecting to make up for the loss in the huge gain in the sale of the software. So they manufacture and lose more money on the consoles without selling any more software, it's a lose lose situation for them. Marketshare doesnt help if they don't get any more money from it.
I don't give two hoots for a backup policy. What you need is a data recovery policy. When will I need to recover data, and how will it that be attained.
I've been working with Symantec (formerly Veritas) Netbackup in my workplace for the past 6 years. About 6 months ago I became one of the backup admins, and the biggest barrier I have to break with our clients is the backup mentality - I must backup everything all the time...
Generally your data recovery will happen from two triggers:
1. A user broke his own stuff and needs a file restored. 2. Disaster Recovery.
Each has different requirements, user wants the backup copy to be onsite, DR wants it to be offsite. User PC's typically can be rebuilt/imaged in a disaster, you're not going to have a hot-site contract for PC's. If your DR plan is to install an OS, install a backup/restore client software then recover databases/applications, then why fret about backing up the OS?
Our policy is as follows
NT/Unix OS and flat files Monthly full backups retained for 13 months Weekly full backups retained for 6 weeks Daily cumulative incremental (everything changed since the last full) retained for 15 days
Oracle Datafiles Weekly cold for 13 months Daily hot for 6 weeks 1-6 hour archive logs for 15 days
Exchange Datastores Daily full for 6 weeks Weekly full for 13 months
Every day any full backups that are more than 10 days old (not copy 0) are sent offsite.
Any customer that has a DRP contract (banks etc) with a 4 hour recovery policy (we have 3 days to get the system back to how it was 4 hours before the disaster) we either run inline tape copies, one for onsite and one for offsite, or else we backup overnight and duplicate during the day.
Your most important backup (for Netbackup) is your catalog. If you go to DR and all you have is a box of tapes, good luck. You need to know what data is on what tape, and the only thing that knows that is the Netbackup catalog. I don't know much about other backup products (HP OpenView and BackupExec are the only others I've touched), but I'm sure they'll have something similar.
I've got lots more to say, but I don't have time to put it all down now. Send me a/. message if you want more info.
Slashdot Mirror
Policies and Procedures exist for a reason. I support this and will always try to work within 'the system', whatever that may be. If you find 'the system' isn't working. Take the steps necessary to improve it, and carry on. Wash rinse repeat.
To that end, my recommendation is to have the doctors get involved. Absolutely, beef up their security, have good intrusion detection, prevention and reporting. Get security to advise the doctors ahead of time about the planned 'attack', and report back the findings. Be the blue team defending, let them be the red team. Make sure you've done your job right.
I would consider this to be no different than regularly restoring your backup data. You do that right?
When you'll trust Bender to watch your jewels, beer and cigars - I'll trust robots.
Besides the obvious 'don't leave equipment in the car' solution, what else are people doing?
Nothing - that's all that I do. Easy and only breaks down when I'm being an idiot.
Well then the option should be explored to know what its outcome will be. Sure if "the nice government" says no, then no is the answer. But, and here's where an imagination comes in, what if they are swayed by logical arguments and understand that it could be beneficial to reuse resources that would otherwise have to be destroyed. New contracts can cause amendments to old contracts really easily.
I don't understand why you are discouraging the OP from exploring this option, and I don't really care either. You use terms like "was probably". Depending on the amount of effort it would take to find a definitive answer, it is normally worth while to turn that "was probably" into a known fact. Then action can be taken based on those facts.
The business solution is the have the original contract revised to not force you to destroy something you want to keep. You get the next contract, get them to keep the parts to save time, money, efforts, energy. If it works then your employer will see you as a multi-faceted resource with solutions from more than one discipline. If nobody agrees then stop working for someone who makes stupid decisions.
That's how I operate and I've never been fired, been promoted 4-5 times though.
Will it outrun a human on the open savannah or through an urban city? I know the TFA mentioned tight turns and immediate stop & go, but what about in a building, over a fence, through the neighbor's back yard, up the stairs, from one roof to the next? I'd really like to watch something like this outrun an urban freerunner.
Not because it's against any policy but as good internet citizens, if they cut my connection I'm going to ask why, I find out it's because I'm infected, I just have to clean the infection and I'm back online. Whose rights, freedoms, expressions are being affected in any way from this?
Most internet users (don't just think /. crowd) would appreciate this type of action. One ISP where I live had this policy in place 4-5 years ago and I helped my cousin get rid of virii that he didn't know he had until this happened. Some advanced uses might be upset, just like pirateers are upset when TPB goes down, but those people will find ways around and still be able to do what they want to do.
Perhaps the GP planned to unzip his skin down the back, peel it forward, and present his entire "surface area" to the sun?
I got the point a few posts back, but this comment actually made me laugh. Thank you.
Most of the open access points I come across are proxied to some pay per MB or pay per minute credit card log in page. Not so open but still connected to the internet.
You don't have backup needs, you have recovery needs. Backup enables you to fulfill those needs.
As has been mentioned many times above, there's no one fit answer - but I don't think you're even asking the right questions.
Under what circumstances will you be recovering data? There are two main types of recovery:
day to day recoveries where users want older versions of files or to replace a corrupt or deleted file; and
disaster recovery in case of hardware, system or site failure.
Will you support both recovery needs? If so then for day-to-day recoveries you need backups every day kept for any length of time deemed appropriate. Proper tape based backup is still the industry standard here just based on the volume. 12TB at 75% used, running full backups every week kept for 4 weeks, and daily cumulative incremental backups with 5% changes every day kept for 10 days means 51.3TB of data. Plus, you don't want all your copies on a single media, imagine if that thing failed?
For disaster recovery you need to know your RPO and RTO? Your Recovery Point Objective is basically how much data can you stand to loose while your Recovery Time Objective is how long after the disaster you can take to get back up and running. Answering these will tell you how often you need to run a backup and what storage technologies and methods are appropriate, or at least which ones are inappropriate. How are you going to protect your data from the disaster - how far away is far enough? I wouldn't consider the same campus as far enough away.
There are a number of products out there. I personally work with NetBackup from Symantec and it's pretty much an industry standard, but that's my employer's choice. I've looked at amanda (http://www.zmanda.com/) a few times, but haven't done any real testing with it. There's data protector, BackupExec and many listed at http://en.wikipedia.org/wiki/List_of_backup_software
The third frame of that comic should read ~on't Pani~
The briefness of the article and lack of actual functional analysis make me think this should have been a comment on the original /. article rather than a whole new article of its own.
Slow news day?
> Nothing at the airline is stopping you from flying first class.
There, fixed it for you. My income and the people paying for my seat do stop me from flying first class.
With all the comments like "Predictably, Gears of War seems to get it right.", it seems to be more of a GoW praise article stating that this game has no flaws, but all the others do.
Also, the summary has a small error, article talks of games from 2007, namely GoW, not GoW2.
More crashes occur on the ground than in the air. In fact, according to http://www.planecrashinfo.com/cause.htm 62% of crashes occur on the ground, they're just usually the least fatal.
There's not a lot of risk in straight and level flight...
Someone from the Avalanche probably put in their old address when signing up for some online service and set the whole range to QC.
As for fixing it, sorry, can't help you.
I offer to do my part and offer a backup copy of all the content I provide. If every content provider did these we'd be set. /me takes tongue out of cheek.
What about the Wii 1024 (W1K) or the Wii HoloCube
GTA3, never finished the game, played easily 300 hours, too much fun flipping cars.
I found it interesting to note that MS was backing a complaint against Dreamworks, you think they could sort that one out in-house.
For something that's only a year or so old (production wise), I don't trust it worth shit.
/dev/null > /path/to/file', then, once you have some blocks free, rm works (so does unlink).
We run Netbackup Enterprise on Solaris 10 - during our last round of upgrades we installed ZFS on our disk staging storage units. It replaced VxFS. The way disk staging storage units (DSSUs) work in Netbackup, the disk is always near 100% full form a unix perspective. Basically, any time more disk is needed, the oldest image that has been copied to tape is expired from disk, thus freeing up more room. However, ZFS's most prominent bug from our perspective is that during periods of high activity, if all blocks become allocated, it becomes impossible to unlink(2) a file. This causes the application to no longer be able to make space for new backup images.
Going down the shell, try to rm a file and it comes back: rm failed, disk is full.
Well, if the disk is full, and you can't rm because the disk is full, how do you free up space?
Sun's response, truncate an unnecessary file using 'cat
Ok - so how do you tell a compiled application to truncate an unnecessary file before unlinking it? You can't! How can you determine what an unnecessary file is? If you delete the image before expiring it from the catalog you get errors when you try to expire, so you end up with catalog corruption.
All in all, this is a problem that should never have been introduced, let alone still exist after months of sending trace outputs and reproducing it in multiple environments. ZFS isn't ready for the real world.
Not particularily. Processors already had drivers, an OS. So, who do you trust more to write for that processor, your OS provider or your processor provider?
But, M$ is making a loss on the sale of its console expecting to make up for the loss in the huge gain in the sale of the software.
So they manufacture and lose more money on the consoles without selling any more software, it's a lose lose situation for them.
Marketshare doesnt help if they don't get any more money from it.
I don't give two hoots for a backup policy. What you need is a data recovery policy. When will I need to recover data, and how will it that be attained.
/. message if you want more info.
I've been working with Symantec (formerly Veritas) Netbackup in my workplace for the past 6 years. About 6 months ago I became one of the backup admins, and the biggest barrier I have to break with our clients is the backup mentality - I must backup everything all the time...
Generally your data recovery will happen from two triggers:
1. A user broke his own stuff and needs a file restored.
2. Disaster Recovery.
Each has different requirements, user wants the backup copy to be onsite, DR wants it to be offsite.
User PC's typically can be rebuilt/imaged in a disaster, you're not going to have a hot-site contract for PC's. If your DR plan is to install an OS, install a backup/restore client software then recover databases/applications, then why fret about backing up the OS?
Our policy is as follows
NT/Unix OS and flat files
Monthly full backups retained for 13 months
Weekly full backups retained for 6 weeks
Daily cumulative incremental (everything changed since the last full) retained for 15 days
Oracle Datafiles
Weekly cold for 13 months
Daily hot for 6 weeks
1-6 hour archive logs for 15 days
Exchange Datastores
Daily full for 6 weeks
Weekly full for 13 months
Every day any full backups that are more than 10 days old (not copy 0) are sent offsite.
Any customer that has a DRP contract (banks etc) with a 4 hour recovery policy (we have 3 days to get the system back to how it was 4 hours before the disaster) we either run inline tape copies, one for onsite and one for offsite, or else we backup overnight and duplicate during the day.
Your most important backup (for Netbackup) is your catalog. If you go to DR and all you have is a box of tapes, good luck. You need to know what data is on what tape, and the only thing that knows that is the Netbackup catalog.
I don't know much about other backup products (HP OpenView and BackupExec are the only others I've touched), but I'm sure they'll have something similar.
I've got lots more to say, but I don't have time to put it all down now. Send me a
Until I read the "Microsoft's not evil" part. This must be a hoax.