Absolutely agree with this poster. I work in Academia in an Ivy League which purchases approx $10-15 million of Apple inventory a year. My main gripe is AppleCare. The Dell/HP/Lenovo systems bundle a 3 year warranty, Apple force you to license and purchase 3 year support separately and drive any price differential higher. On the other hand, xservers, xraid and xsan are definitely priced competitively with Dell/HP/Lenovo.
Furthermore, Apple Enterprise Software Licensing and Sales are outright incompetent. I purchased ARD2.5 one month before 3.0 shipped, Sales backflipped on my eligibility for a "free" upgrade and eventually i gave up chasing down their mandarins, almost as bad as IBM. Nutty scenarios like iLife only bundled with new machines and not with OS upgrades which are stuck with inferior iPhoto etc? Arrgh!
Apple should stick to the software business and not attempt to niche hardware costs attempting to compete with the marginally profitable Asian manufacturing. Apple cannot compete on the SMB tier.
* Desktop : workstations, laptops, pda's
* Servers : per server - NO centralised management
* DataCenter : dedicated console and bells/whistles
To support the above, there are many types of Recovery scenarios:
* Hot Restore : Replicate to a redundant/failover box/server/Cluster/Datacenter
* Warm Restore : Restore capability to same or supported (redundant) hardware
* Cold Restore : lights-out/bare-metal from scratch including alien hardware
And again to tie the two together there are many solutions:
- SAN/Storage replication/sync (typical dump data to tape)
- ILM or tiered storage with tiered retention (archive when necessary)
- Synthetic backups
The problem, IMO, is that the bulk of existing "dump it on tape" apps facilitate "operational" failures NOT disasters. Most shops concentrate on ensuring (sometimes regulatory) data integrity but the restoration capacity should be the focus. In an SMB scenario, you cannot always guarantee the same hardware to facilitate a complete bare-metal restore. Locking data in a box/tape is of fuck all use when the keys are 100ft under water/slag/Cheney etc.
Your question prompts further ones from me:
- Does your backup app support removing the hardware dependance?
- Is your storage virtualised?
- Can your storage snapshot/replicate?
- Are your servers virtual?
- Do you _really_ generate those deltas?
- Can you improve the delta or data-sync efficiency?
- Can you emulate a full?
What i'm getting at here, is that SMBs cannot afford to just backup and be done, SMBs encounter failure rates higher that the FortuneX guys, accommodate that first rather than a straight performance/media benchmark.
I've never had much luck with otto. I have used Icecast to relay ogg files which were streamed from Ices or mp3s from Muse. I'd simply replace "stream" with a dedicated client. You can also broadcast/mix "live audio" (station ids) into the stream using Darkice. I've can also recommend Shoutcast.
I've used the above and am confident you can build a solution around them. Freshmeat shows tons more.
I have problems digesting theRegisters style of self-important braggart journalism. Its more than just juvenile sensationalism, its downright irresponsible reporting. Stick to the fucking facts and shove the opinion.
[TheRegister Article Summary]
Rampant KPMG/PWC cronyism blames spreadsheets for mangerial incompetence rather than the managers. Shock Horror!
Note: i sat in on a roundtable with Charlie Ciarcarlo (the Cisco CTO) a few weeks ago. Cisco intend to virtualise bloody everything. Their stated intention is to move intelligence from the edge/periphery back into the network. This will break the (to paraphrase) "Network of Stupid Networks" model for the free market explosive growth of the internet. I have doubts that it will do anything other than drive revenue into Cisco networks but am interested in the GRID computing as stepping stone model. Ciscos roadblock is adoption of the facilitating technologies on the Windows desktop. The primary administration benefit was the hoary old policy based network model - i've been listening to people tell me policy management is going to make my life easier for 10 years. I'm still using SNMP for monitoring and expect scripts for changes. I have built networks around 4500's, the only benefit is an ability to skimp on DS SupeModules.
As we regress to the Network is the Computer model (aka the network is a mainframe with intelligent terminals and completely virtualized services), the distribution layer becomes more and more important.
Aside from the benefit of building the physical layout to represent (as much as possible) the hierarchical virtual topography in aiding troubleshooting, the Cisco Campus/DS layered design allows for the layering of services without having to swap out switches e.g. bringing routing to the switch port isn't going to help with efficiently positioning a Storage Virtualization Controller, VoIP, IPTV, Meta-Identity servers etc.
Well....kinda. Death here, being a relative term: BSD growth/spread is stagnant in comparison to the competing platforms. Another take would be that its on permanent life support!
I agree that we are definitely seeing some sort of internal Tipping point in evidence. Dirty laundry is everywhere not just in the code! MS is so bloody huge that i don't foresee the implosion typical of a smaller org without the proper management checks.
Considering the major Internet engineering right now is machines talking to machines, i don't see much play for MS middleware. The standards are laying the groundwork for the next steps in user interactivity. MS are sitting on the fence and waiting for someone to tell them what they need to do to own this. The minions are headless and their leaders are fat and clueless.
I don't think thats what MS are doing. I think we're seeing genuine confusion over the company direction. There is no true enemy any more except the end users. Internal to MS, i think it plays out like this:
1) On one hand you've got the the internet geeks: "the always-online and pervasive computing model will benefit the standards based, trim orgs" guys. Unless MS can set that standard or reduce the bloat, they're the Mainframe in the 80s.
2) On the other hand, you've got the party-faithful, invested in the bloat and cross-licensing who cannot envision losing the unprecedented market dominance. Again, the Mainframe in the 80s.
From what i've seen of the MS press, the push inside MS is on the standardisation and convincing the marketplace to side with the heavy hitters. What can you say about an organisation who's older products are stalling upgrades to its own new revisions? IMHO Its a slow realization for MS that the OS bloat is self defeating and that the platform tie in has as many cons as pros.
No, they reversed that faux pas. Heres a randomly googled report which confirms they're fixing any retail models with the problem and the US (and newer Japanese) PSP-1000K models don't ship with it.
It is slightly more expensive but maybe we can blame that on the weak dollar or the trade deficit. The bundle doesn't appeal to me and neither do the launch titles. I'm going to wait for a truely interesting use of the units capabilities. Four player FPS/racer pickup sounds boring.
The US is getting a rev2 PSP with the current problems (X button and UMD ejection) resolved. The release price is slightly more expensive than the Asian one. I'd hate to think the US consumer is paying for Sony's hardware fixes...
I did quit, on principle, at the height of the dot-bomb. I have to admit, it was less a last straw motive and more a slow slide into disgust and repulsion. Also a liberal amount of stupidity.
I went from making the industry average for the northeast US to nothing. Nothing. Elective unemployed cannot receive any assistance. I walked out the door with my holiday pay and what i had in the bank. I faced the worst employment market in decades. It took me 2 months to line up a contract position and another 2 months before i received any pay (coincident with starting another full time job). That next position (same one i'm in now) was a significant chunk lower than my previous salary. Thankfully i did not have to dip into my 401k. I was lucky. i know a number of geeks who simply gave up looking for a decent job and went back to college or changed careers. I did switch from corporate to academic climes
Do i regret quitting? Sometimes. I have guilty thoughts akin to the Wheaton "Prove to Everyone that quitting Star Trek was a good idea" monkey. Most of the time, no, i don't. I DO miss the money. Then again, i can work 2 jobs for the same hours and for more money.
Do i feel better for quitting? Absolutely. I do not have to deal with the previous bad karma. I IM former colleagues and am shocked by their vitriol. The measures i took to tighten my finances are still worthwhile. My reasons for leaving (a lack of Downward Loyalty) have only compounded in the last 2.5 years and i can honestly state i am better for being out of that cesspit.
This is an entire category of Operations Management and can encompass everything. Don't take it lightly and don't be afraid to start small. The first thing you need to do is categorize what you want to monitor into individual sections and work on the easiest stuff first. By the time you work up to the tough stuff, you'll have an idea of whats available, what your capabilities are and hopefully the easy stuff can be quickly rewritten/integrated into a netter solution. Don't miss the critical stuff in a morass of junk alerts. Sample consideration (everything that moves in the data center):
Hardware: --------- 1) Server 2) Storage 3) Network 4) Power 5) Environment 6) Security
Software: --------- 1) OS 2) Applications 3) Security
Once you're done building it, start over. The last tier is the most visible e.g. delegating a raid rebuild page to the opcenter flunky without proper documentation is a Career Limiting Move (CLM), building the best monitoring system is a fucking waste unless you pay attention to it. The most apt cliches for monitor normalisation are all military: Warrooms, Bridges, Weapons Hot, Communications channels etc. View everything as SNAFU and work from there.
I've done similar. Round about Y2k, we had this user who was "kansulting" on an SAP implementation. This guy was a complete ADHD meets Tourettes victim. He'd come running into the office ranting about the "SAP GUI FIREWALL" problem. Basically, SAP would spontaneously blow up on his box. I sat down and read the product specs and discovered SAP required a minimum of W95 OSR2. The company had standardised on 95 RTM/OSR1. One fresh build later and he was just peachy.
End of year performance reviewtime. My PHB's conference with his direct report. This was to my benefit - they were discussing end of year bonuses, they came to mine with a non subtle line item - the office injoke "Project SAP GUI FIREWALL" with suitable trite BS bingo. Somehow my PHB kept a straight face and i got a nice bonus (the last they gave out for next lean 4 years). After that i just used to fill my self-evaluations with "Web Economy Bullshit" generator quotes. Ah the good ole' days of leveraging synergistic bricks and morter.
OpenFirmware is a hell of a lot more featureladen than the PC's BIOS. While attempts to update BIOS are ongoing (see LinuxBIOS), a more effective shortterm solution is to emulate part of the functionality: boot off a livecd/floppy and network/fileshare over tcpip (nic or firewire). I'd advise u to look towards the always excellent Bart Lagerweij site
Before i rtfa, i thought this had links to the MS UndeadTAPI "PASSPORT for the beyond" i.e. a triggered email discloses your passwords in order to circumvent your family having to sue for disclosure. Next up in UndeadTAPI is auto-distruct pr0n (in XML).
I was gonna post questioning this very coincidence. Googling was fruitless, I would never have thought to look in wikipedia for it. Thanks for the link!
Slashdot Mirror
It sounds to me like the OP is complaining that his hammer won't work with every nail.
No tool is perfect and each has limitations.
Use each tool as appropriate and do not prescribe to purism over functionality.
Absolutely agree with this poster. I work in Academia in an Ivy League which purchases approx $10-15 million of Apple inventory a year. My main gripe is AppleCare. The Dell/HP/Lenovo systems bundle a 3 year warranty, Apple force you to license and purchase 3 year support separately and drive any price differential higher. On the other hand, xservers, xraid and xsan are definitely priced competitively with Dell/HP/Lenovo.
Furthermore, Apple Enterprise Software Licensing and Sales are outright incompetent. I purchased ARD2.5 one month before 3.0 shipped, Sales backflipped on my eligibility for a "free" upgrade and eventually i gave up chasing down their mandarins, almost as bad as IBM. Nutty scenarios like iLife only bundled with new machines and not with OS upgrades which are stuck with inferior iPhoto etc? Arrgh!
Apple should stick to the software business and not attempt to niche hardware costs attempting to compete with the marginally profitable Asian manufacturing. Apple cannot compete on the SMB tier.
The combover is ALIVE i tell you, ALIVE! Hooray for Patrick Jordan!
This has got to be marketeering.
Real must be in negotiations with MS and this is just a negotiation tactic.
Interesting thing is that the free domain registration at the live.com beta will drive this up even more!
Backup falls across many platforms:
* Desktop : workstations, laptops, pda's
* Servers : per server - NO centralised management
* DataCenter : dedicated console and bells/whistles
To support the above, there are many types of Recovery scenarios:
* Hot Restore : Replicate to a redundant/failover box/server/Cluster/Datacenter
* Warm Restore : Restore capability to same or supported (redundant) hardware
* Cold Restore : lights-out/bare-metal from scratch including alien hardware
And again to tie the two together there are many solutions:
- SAN/Storage replication/sync (typical dump data to tape)
- ILM or tiered storage with tiered retention (archive when necessary)
- Synthetic backups
The problem, IMO, is that the bulk of existing "dump it on tape" apps facilitate "operational" failures NOT disasters. Most shops concentrate on ensuring (sometimes regulatory) data integrity but the restoration capacity should be the focus. In an SMB scenario, you cannot always guarantee the same hardware to facilitate a complete bare-metal restore. Locking data in a box/tape is of fuck all use when the keys are 100ft under water/slag/Cheney etc.
Your question prompts further ones from me:
- Does your backup app support removing the hardware dependance?
- Is your storage virtualised?
- Can your storage snapshot/replicate?
- Are your servers virtual?
- Do you _really_ generate those deltas?
- Can you improve the delta or data-sync efficiency?
- Can you emulate a full?
What i'm getting at here, is that SMBs cannot afford to just backup and be done, SMBs encounter failure rates higher that the FortuneX guys, accommodate that first rather than a straight performance/media benchmark.
This exact same issue (MSOffice looking for source media) is caused when you patch a badly installed office. Suck it down:
1) Build an administrative install point
2) Install/Deploy from it
Check out MeetingMaker. Runs on Linux on the server and clientside.
I've never had much luck with otto. I have used Icecast to relay ogg files which were streamed from Ices or mp3s from Muse. I'd simply replace "stream" with a dedicated client. You can also broadcast/mix "live audio" (station ids) into the stream using Darkice. I've can also recommend Shoutcast.
I've used the above and am confident you can build a solution around them. Freshmeat shows tons more.
I have problems digesting theRegisters style of self-important braggart journalism. Its more than just juvenile sensationalism, its downright irresponsible reporting. Stick to the fucking facts and shove the opinion.
[TheRegister Article Summary]
Rampant KPMG/PWC cronyism blames spreadsheets for mangerial incompetence rather than the managers. Shock Horror!
[/TheRegister Article Summary]
Note: i sat in on a roundtable with Charlie Ciarcarlo (the Cisco CTO) a few weeks ago. Cisco intend to virtualise bloody everything. Their stated intention is to move intelligence from the edge/periphery back into the network. This will break the (to paraphrase) "Network of Stupid Networks" model for the free market explosive growth of the internet. I have doubts that it will do anything other than drive revenue into Cisco networks but am interested in the GRID computing as stepping stone model. Ciscos roadblock is adoption of the facilitating technologies on the Windows desktop. The primary administration benefit was the hoary old policy based network model - i've been listening to people tell me policy management is going to make my life easier for 10 years. I'm still using SNMP for monitoring and expect scripts for changes. I have built networks around 4500's, the only benefit is an ability to skimp on DS SupeModules.
As we regress to the Network is the Computer model (aka the network is a mainframe with intelligent terminals and completely virtualized services), the distribution layer becomes more and more important.
Aside from the benefit of building the physical layout to represent (as much as possible) the hierarchical virtual topography in aiding troubleshooting, the Cisco Campus/DS layered design allows for the layering of services without having to swap out switches e.g. bringing routing to the switch port isn't going to help with efficiently positioning a Storage Virtualization Controller, VoIP, IPTV, Meta-Identity servers etc.
Perhaps it was an attempt to "embrace and extend" citizens of both north and south america after having assimilated the available USAians.
Aha but i've got the Edison derived UNDeadTAPI just waiting for the VC guys!
Well....kinda. Death here, being a relative term: BSD growth/spread is stagnant in comparison to the competing platforms. Another take would be that its on permanent life support!
I agree that we are definitely seeing some sort of internal Tipping point in evidence. Dirty laundry is everywhere not just in the code! MS is so bloody huge that i don't foresee the implosion typical of a smaller org without the proper management checks.
Considering the major Internet engineering right now is machines talking to machines, i don't see much play for MS middleware. The standards are laying the groundwork for the next steps in user interactivity. MS are sitting on the fence and waiting for someone to tell them what they need to do to own this. The minions are headless and their leaders are fat and clueless.
I don't think thats what MS are doing. I think we're seeing genuine confusion over the company direction. There is no true enemy any more except the end users. Internal to MS, i think it plays out like this:
1) On one hand you've got the the internet geeks: "the always-online and pervasive computing model will benefit the standards based, trim orgs" guys. Unless MS can set that standard or reduce the bloat, they're the Mainframe in the 80s.
2) On the other hand, you've got the party-faithful, invested in the bloat and cross-licensing who cannot envision losing the unprecedented market dominance. Again, the Mainframe in the 80s.
From what i've seen of the MS press, the push inside MS is on the standardisation and convincing the marketplace to side with the heavy hitters. What can you say about an organisation who's older products are stalling upgrades to its own new revisions? IMHO Its a slow realization for MS that the OS bloat is self defeating and that the platform tie in has as many cons as pros.
No, they reversed that faux pas. Heres a randomly googled report which confirms they're fixing any retail models with the problem and the US (and newer Japanese) PSP-1000K models don't ship with it.
It is slightly more expensive but maybe we can blame that on the weak dollar or the trade deficit. The bundle doesn't appeal to me and neither do the launch titles. I'm going to wait for a truely interesting use of the units capabilities. Four player FPS/racer pickup sounds boring.
The US is getting a rev2 PSP with the current problems (X button and UMD ejection) resolved. The release price is slightly more expensive than the Asian one. I'd hate to think the US consumer is paying for Sony's hardware fixes...
I did quit, on principle, at the height of the dot-bomb. I have to admit, it was less a last straw motive and more a slow slide into disgust and repulsion. Also a liberal amount of stupidity.
I went from making the industry average for the northeast US to nothing. Nothing. Elective unemployed cannot receive any assistance. I walked out the door with my holiday pay and what i had in the bank. I faced the worst employment market in decades. It took me 2 months to line up a contract position and another 2 months before i received any pay (coincident with starting another full time job). That next position (same one i'm in now) was a significant chunk lower than my previous salary. Thankfully i did not have to dip into my 401k. I was lucky. i know a number of geeks who simply gave up looking for a decent job and went back to college or changed careers. I did switch from corporate to academic climes
Do i regret quitting? Sometimes. I have guilty thoughts akin to the Wheaton "Prove to Everyone that quitting Star Trek was a good idea" monkey. Most of the time, no, i don't. I DO miss the money. Then again, i can work 2 jobs for the same hours and for more money.
Do i feel better for quitting? Absolutely. I do not have to deal with the previous bad karma. I IM former colleagues and am shocked by their vitriol. The measures i took to tighten my finances are still worthwhile. My reasons for leaving (a lack of Downward Loyalty) have only compounded in the last 2.5 years and i can honestly state i am better for being out of that cesspit.
Did i say i missed the money? I miss the money.
Rule #1: Do not add to the problem.
This is an entire category of Operations Management and can encompass everything. Don't take it lightly and don't be afraid to start small. The first thing you need to do is categorize what you want to monitor into individual sections and work on the easiest stuff first. By the time you work up to the tough stuff, you'll have an idea of whats available, what your capabilities are and hopefully the easy stuff can be quickly rewritten/integrated into a netter solution. Don't miss the critical stuff in a morass of junk alerts. Sample consideration (everything that moves in the data center):
Hardware:
---------
1) Server
2) Storage
3) Network
4) Power
5) Environment
6) Security
Software:
---------
1) OS
2) Applications
3) Security
Events:
-------
1) Failures
2) Alerts
3) Misfires
4) Security
Triggers:
---------
1) Notification/False positives
2) Action plans/Event handling
3) Documentation, Documentation, Doumentation
4) Reporting aka analysis and cya
5) Security
Once you're done building it, start over. The last tier is the most visible e.g. delegating a raid rebuild page to the opcenter flunky without proper documentation is a Career Limiting Move (CLM), building the best monitoring system is a fucking waste unless you pay attention to it. The most apt cliches for monitor normalisation are all military: Warrooms, Bridges, Weapons Hot, Communications channels etc. View everything as SNAFU and work from there.
Rule #1: Do not add to the problem.
I've done similar. Round about Y2k, we had this user who was "kansulting" on an SAP implementation. This guy was a complete ADHD meets Tourettes victim. He'd come running into the office ranting about the "SAP GUI FIREWALL" problem. Basically, SAP would spontaneously blow up on his box. I sat down and read the product specs and discovered SAP required a minimum of W95 OSR2. The company had standardised on 95 RTM/OSR1. One fresh build later and he was just peachy.
End of year performance reviewtime. My PHB's conference with his direct report. This was to my benefit - they were discussing end of year bonuses, they came to mine with a non subtle line item - the office injoke "Project SAP GUI FIREWALL" with suitable trite BS bingo. Somehow my PHB kept a straight face and i got a nice bonus (the last they gave out for next lean 4 years). After that i just used to fill my self-evaluations with "Web Economy Bullshit" generator quotes. Ah the good ole' days of leveraging synergistic bricks and morter.
OpenFirmware is a hell of a lot more featureladen than the PC's BIOS. While attempts to update BIOS are ongoing (see LinuxBIOS), a more effective shortterm solution is to emulate part of the functionality: boot off a livecd/floppy and network/fileshare over tcpip (nic or firewire). I'd advise u to look towards the always excellent Bart Lagerweij site
Before i rtfa, i thought this had links to the MS UndeadTAPI "PASSPORT for the beyond" i.e. a triggered email discloses your passwords in order to circumvent your family having to sue for disclosure. Next up in UndeadTAPI is auto-distruct pr0n (in XML).
I was gonna post questioning this very coincidence. Googling was fruitless, I would never have thought to look in wikipedia for it. Thanks for the link!