Clearspace Server Syndication Feed

Let's remove dirts and scratches with StylePix (Image editor)

kansapa — Wed, 08 Jul 2009 12:40:08 GMT

StylePix have a remove scratch tool for remove dirts and scratches.

Load image to edit.
Select the Remove Scratch (shortcut: R) tool
If you could not find the tool select remove red eye tool and select remove scratch tool within that tool's tool bar.
Adjust brush size and opacity
Brush on scratches to erase
Save the result image

Before image

Determine brush size by size of the scratch. we recommand you select larger size of brush than size of the scratch.

image while removing scratches

comparing before and after

Image presented by: Free Stock Photos for websites - FreeDigitalPhotos.net

Veeam Backup 3.1 – puzzled by decrease in backup performance

VMSpotlight — Wed, 08 Jul 2009 12:15:53 GMT

On Sunday Eric Sloof wrote a blog post highlighing a potential issue with version 3.1 of Veeam Backup. The main focus of the discussion surrounds drastic reductions in back-up speed with servers upgraded to vSphere 4.

The people at Vizoncore and Veeam have posted on the subject in several online spaces also. One of Veeam’s product managers who runs a blog has posted on this topic here: http://www.vnotion.com/?p=38 explaining testing he has done on the issue.

View the VMTN discussion thread here: http://communities.vmware.com/message/1302322

Jason Mattox and Steve Philip also contributed to the discussion (excerpts below from Eric Sloof’s blog):

Jason Mattox :

Putting my differences aside, (I’m from vizioncore) and wanting to see this fixes for all VMware users, here is what it think is going on. I think this is due to the read speeds from VMFS on ESX 4 VS ESX 3. Give this test a try, create a 10 GB VM and run this command, how does it take on ESX 3 vs ESX 4? You have to remember that VCB over the network is using VMware API’s which are going to get more disk/read time. I think VMware has starved the COS reads again. I think this same thing happened from ESX 2.5.x to 3.0 and when 3.0.1 came out it was fixed, I’m not 100% on that ,but I think that’s what happened. time cat
JM_10GB_Test-flat.vmdk > /dev/null

Steve Philp :

As the person that posted the original question both on VMware’s forum and on Veeam’s forum, I can tell you that we’re all just waiting for VMware to acknowledge and fix the issue. We have been working with VMware tech support for a few weeks now, providing them with backup and file copy performance data involving the Service Console. We have no idea whether they’re seeing other reports of the issue, they haven’t been very forthcoming with info. I can confirm that the backup speed problem ONLY affects transfers using the Service Console. Using VCB / SAN mode in Veeam Backup allows full backup speed. Here’s the followup posting on my blog with our “lesson’s learned”.

VDI Connection Broker Overview – featuring Leostream

XtravirtPortal — Wed, 08 Jul 2009 11:37:27 GMT

Title: VDI Connection Broker Overview – featuring Leostream
Author(s): Xtravirt (Paul Buckle)
Target Audience: Technical - Novice
Current Revision: 1.0 July 2009
First Published: 6 July 2009
Products: Leostream Connection Broker
UID: XD10105

Overview: This white paper provides an overview of VDI and Connection Brokers. It explores Leostream's broker and provides a table of some of the products features.
Information

VDI (Virtual Desktop Infrastructure) was VMware’s original acronym for the hosting of desktop operating systems on their virtualization platform, but it is now acknowledged as an industry-wide term that describes a solution where users access their desktops remotely. This white paper provides an overview of VDI and Connection Brokers. It explores Leostream's broker and provides a table of some of the products features.
Key Concepts:

Overview of VDI and Connection Brokers
Leostream Connection Broker key features

Download the full article/paper here: http://xtravirt.com/xd10105

Upgrading to vSphere 4 - The Experience (Part 1)

that1guynick — Tue, 30 Jun 2009 03:49:59 GMT

The day had arrived.

After many marketing documents, press releases, and speculative forum posts, we were all waiting with baited breath to see just how VMware could make one of the most revolutionary products to ever hit the market even better.

I attended the vSphere 4 launch tour. I watched the powerpoint slides scroll through with all of the piles of new features. I was sold. I researched a bit, and couldn't find any articles negating the ability to upgrade. Asked all my questions beforehand...

"Can ESX 3.x and 4 hosts co-exist in the same cluster?"
"Is there anything retroactive about running a non-upgraded-VM on a ESX4 host?"
"Can I still join ESX4 hosts to VirtualCenter 2.5?"

This accurately defined my upgrade path, and this is basically a synopsis of how that process went down. There were some surprises, but none of them were bad.

Step 1. Upgrade VirtualCenter 2.5.x to vCenter 4.0

"Wait...what?" This shocked me a bit at first, because the answers I got from the launch tour told me that I could join ESX4 hosts to VirtualCenter 2.5! Why do I need to upgrade VC to vCenter4 first?

And then the golden nugget was dropped on me.

It just so happened that we had coincidentally just purchased an additional host to add to the cluster. I had waited to do the install so that I could truly test the whole "adding an ESX4 host to VC 2.5" thing.

Clean install went flawlessly. Things to note: You can now preload custom drivers DURING the install. Got a weird NIC or HBA? Oddball SCSI card? Here's your chance. No need to go in post-install and do your configuring there. You can do it before the installer launches into loading packages. COOL! Other than that, it was just like installing any of the other versions, aside from a few graphics changes.

First host install complete. Once it's loaded, I connect to it directly via the VIC, to do some simple configuring.

ROADBLOCK!

New client install time! The first time you connect to ESX4 or vCenter4, you're prompted to install the new client. Schnazzy new dashboard, and I see the potential here for lots of vCenter plugins. (more on that in another post)

Client updated, onward! Connect to the host, configure my storage and networking to be identical to the other hosts in the cluster. Easy-peezy, no problems there. Right-click on the cluster, add host, go through the motions, and in a matter of minutes, I now have an HA/DRS-activated ESX4 host in my VC 2.5/ESX3.5.x cluster. Flawless.

WOW! This is great! So I kick one of the 3.5 hosts in Maintenance Mode, go to lunch while the VM's migrate off, come back and pop in the ESX cd. Boot up....

"Existing ESX hosts can no longer be upgraded via this method. Please upgrade through vCenter."

Hmm...a bit of a quick digging made me realize that there was not a choice in upgrade paths anymore. So I read back over the upgrade documentation once again. AHHHHH! So THIS is why they want you to upgrade VC to vCenter4 first!

Apparently, one of the big changes in vCenter4 was making Update Manager NOT USELESS! "Alright....let's give this thing a shot."

So, ditching the idea of upgrading hosts for the moment, I switched gears over to VC. Downloaded the .zip pack and copied them to my existing VC server (which is also a VM). Ran the executable, it found my existing VC installation. Great! Then the prompts about the database come up. So I put in my db user/pass, and the name of the database, ERROR! Ut oh. It prompts me that the vc user must have full 'sa' rights to the MSDB database. I was confused for a bit because I didn't read the fine print closely enough. I thought it was referring to my actual VC database. So, I double-checked that the vc user had owner privs to the VC database, went back and tried again. ERROR! It took me a couple of tries to realize I wasn't paying enough attention, and that it said 'MSDB' database, and not my actual 'VC' database.

Problem solved, moving on. Upgraders, just make sure you're doing the MSDB when you upgrade to vCenter, not your actual VC database.

Licked that, install finished fine, and IIRC, it prompted me to remove the old model licensing server. Note, if you're upgrading all of your vCenter and hosts to v4, there's no need to keep it, but it will not interfere with anything. v4 doesn't even reference it, and it's good to have around in case you need to do something in 3.5 (i.e. test/dev environments, perhaps?)

Restarted the VC VM (sorry, "vCenter" now. Did Steve Jobs start working for VMware under the table? vCenter/vSphere...) and connected to it. Nice dashboard! I like it! Love the new licensing model as well. I went straight to the licensing site (licensing.vmware.com) and consolidated all of my individual licenses into ONE KEY! This was amazing! Gone are the days of managing dozens of license keys! And it actually WORKS now! Also, little did I know, but VMware had also already upgraded my license keys to be vSphere4 keys.

So, VC is upgraded to vCenter 4. Licenses have been properly allocated across all hosts with ONE key, and we're ready to rock.

In my next writeup, I'll go over upgrading your individual hosts.

-Nick

mein blog

sahrageile — Tue, 07 Jul 2009 11:00:55 GMT

mein block mein bezirk ich brauche porno videos zum ficken der geilen fotze

diese sachen habe ich beim download von porno gefunden

download von porno

Developer Center Blog is moving to a new platform..

heyitspablo — Mon, 06 Jul 2009 20:25:10 GMT

Folks, we are going to be moving over to a new platform in the next few days.

Please bookmark

http://blogs.vmware.com/developer

Hyper-V Security Guide

VMSpotlight — Mon, 06 Jul 2009 13:52:40 GMT

This info came from a recent post on the Microsoft Virtualization User Group UK blog.

It’s about the Hyper-V Security Guide at TechNet. The document is 41 pages long covering all security problems you should consider when deploying Hyper-V in your environment.

This is a must-read for every system administrator who is considering deploying Hyper-V, so check out the direct download Hyper-V Security Guide from Techet.

The Hyper-V Security Guide provides IT professionals with guidance, instructions, and recommendations to address key security concerns about server virtualization.

Microsoft Hyper-V technology allows consolidation of workloads that are currently spread across multiple underutilized servers onto a smaller number of servers. This capability provides a way to reduce costs through lower hardware, energy, and management overhead while creating a more dynamic IT infrastructure.

The Hyper-V Security Guide can help you elevate the security of virtualized Windows Server environments to address your business-critical needs.

Read the full post here: http://virtualization-spotlight.com/hyper-v-security-guide/

Glossary of VMware Virtualization Terms

XtravirtPortal — Mon, 06 Jul 2009 10:44:06 GMT

Title: Glossary of VMware Virtualization Terms
Author(s): Xtravirt (Paul Buckle)
Target Audience: Technical - All
Current Revision: 1.0 July 2009
First Published: 3 July 2009
Products: VMware

Overview

This article covers a number of terms and acronyms used in VMware virtualization products. A handy reference for those encountering these technologies and concepts.

To read the full article go here: http://xtravirt.com/xd10093