NAS vs File server?!

Droši vien daudzus nomoka šis jautājums 😀

Te nu ir daži domu asni:

1. This is a big statement… if you are going to add more space later its much easier done with a PC rather than a NAS… the other thing is performance wise the PC (with a gigabit network) would be far quicker than a NAS… its also more expensive though.
2. NAS usually refers to an appliance-style server — a box that is built to do one thing and do it well. Lately, everyone has piled into the space, tossing together some jumble of parts, installing Linux RAID, doubling the price, and calling it NAS

As more and more documents were created digitally using Personal Computers, and employees needed way to share the digital documents between them, different approaches started to appear in serving that need: file server and Network-Attached Storage (NAS). In essence, the main difference is:

  • file server is multi-purpose computer hardware designated for sharing files
  • NAS is single-purpose computer hardware which can only be used for sharing files

So, how do these 2 technologies compare? The following table summarises the comparison of the 2 technologies, especially on the high-end side. For low-end side, the comparison will tilt more favorably toward file server than the following

Aspects File server NAS
Initial configuration RIS+wizard None
Remote management Remote desktop Web-based
Vulnerability to malicious acts
Security compliant with centralised setting
Space quota
Folder/file security delegation
Centralised access address
Search document content Indexing Service Enterprise search
View older version of documents VSC Snap shots
Off-line access in branch offices FRS Replication
Off-line access at home
Server role change
Replace defective disc while operating
Recovery after non-disc hardware failure Restore to new H/W Restore to new H/W
Initial investment $ $$

Initial configuration

Here, NAS shines, because it is ready for sharing files as soon as it is taken out of its box. Good system administrators should be able to minimise the time needed to set up server according to standardised base-line configuration by using Remote Installation Service (RIS). After that running the server role wizard should get the file server ready to start sharing files

Remote management

The web-based administration screen of NAS can be used to manage the unit remotely over slower connection speed or even from mobile devices. Remote desktop management of file server requires faster connection speed

Vulnerability to malicious acts

Since the Operating System of NAS is written to flash memory, it is harder to modify than in the case of file server where its Operating System is written to hard discs

Search document content

Newer file servers like Microsoft Windows Server provides the ability to not only search by document name, but also search by document content. NAS don’t provide this. However, it’s possible to add this capability to sites using NAS via additional software called enterprise search

Off-line access at home

Off line access at homeSometimes it might be necessary to take some work home. Photo by len-k-a

From time to time, there will be company documents whose access need to be limited to  only one person, for example when it is still in draft stage. In this stage, it can be useful if that person can take the document on his mobile computer home, modify it at home, and have the changes automatically synchronised to the central storage when he comes to work the next day. Newer file servers like Microsoft Windows Server can provide such feature

Server role change

As business evolve and needs change, technological upgrade needs to be performed regularly every few years, including in the company data center. When such server consolidation activity is performed, a file server hardware can be redesignated to do other simpler tasks because its role is being taken over by better hardware. NAS, on the other hand, can only serve the same purpose for its life time, with increasingly outdated capabilities.

Initial investment

Make no mistake. To get the same service level from file server and NAS, you’ll end up spending more for NAS. That’s why good NAS comes with top-of-the-line CPU and customised UNIX Operating System. Please don’t compare a brand-new entry-level file server and brand-new entry-level NAS that comes with CPU designed for mobile devices tasked with doing all software RAID 5 calculation. In such case, the price difference will translate to performance difference

.

 

Advertisements

Aktīvā direktorija un Outlook Signature izplatīšana

Ko darīt, ja ir vajadzība lietojot aktīvo direktoriju uzņēmumā izplatīt parakstu atbilstoši darbinieka informācijai no AD. Ir risinājums! Šo izveidoojam ka VB skriptu un izplatām pie login.

On Error Resume Next

Set objSysInfo = CreateObject(“ADSystemInfo”)
strUser = objSysInfo.UserName
Set objUser = GetObject(“LDAP://” & strUser)

strName = objUser.FullName
strTitle = objUser.Title
‘strDepartment = objUser.Department
‘strCompany = objUser.Company
‘strPhone = objUser.telephoneNumber

Set objWord = CreateObject(“Word.Application”)
Set objDoc = objWord.Documents.Add()
Set objSelection = objWord.Selection
objSelection.Style = “No Spacing”
Set objEmailOptions = objWord.EmailOptions
Set objSignatureObject = objEmailOptions.EmailSignature
Set objSignatureEntries = objSignatureObject.EmailSignatureEntries

‘Name of Staff
objSelection.Font.Name = “Calibri”
objSelection.Font.Bold = True
objSelection.Font.Size = “12″
objSelection.Font.Color = RGB(15,36,62)
objSelection.TypeText strName
objSelection.TypeText(Chr(11))

‘Role of Staff
objSelection.Font.Name = “Calibri”
objSelection.Font.Bold = False
objSelection.Font.Size = “11″
objSelection.Font.Color = 0
objSelection.TypeText strTitle
objSelection.TypeText(Chr(11))

‘Company Logo (stored in network share accessed by everyone)
objSelection.InlineShapes.AddPicture(“\\servername\netlogon\signature.jpg”)
objSelection.TypeParagraph()

‘Company Contact details
objSelection.Font.Color = RGB(38,38,38)
objSelection.TypeText “Tel +44 (0) 744 525 5214″
objSelection.TypeText(Chr(11))
objSelection.TypeText “Fax +44 (0) 744 524 2244″
objSelection.TypeText(Chr(11))
objSelection.Font.Color = RGB(23,54,93)
objLink = objSelection.Hyperlinks.Add(objSelection.Range,“http://www.sujeeth.net/”,,“Sujeeth Home Page”,“www.sujeeth.net”)
objSelection.TypeParagraph()
objSelection.TypeParagraph()

‘environment message
objSelection.Font.Name = “Webdings”
objSelection.Font.Size = “14″
objSelection.Font.Color = RGB(115,155,63)
objSelection.TypeText “P “
objSelection.Font.Name = “Calibri”
objSelection.Font.Size = “9″
objSelection.TypeText “Please consider the environment before printing this e-mail.”

Set objSelection = objDoc.Range()

objSignatureEntries.Add “Standard Signature”, objSelection
objSignatureObject.NewMessageSignature = “Standard Signature”
objSignatureObject.ReplyMessageSignature = “Standard Signature”

objDoc.Saved = True
objWord.Quit

vSphere 5.0 ir klāt!

Hmmmm…. kas gan tur varētu būt jauns? Tad un lūk, īsa informācija.

  • Convergence. vSphere 5.0 is the first vSphere release built exclusively on the vSphere ESXi 5.0 hypervisor architecture as the host platform. VMware will not include ESX hypervisor architecture-based releases in this vSphere release or later releases. The vSphere 5.0 management platform, vCenter Server 5.0, provides support for ESXi 5.0 hosts as well as ESX/ESXi 4.x and ESX/ESXi 3.5 hosts.
  • VMware vSphere Auto Deploy. Combining the features of host profiles, Image Builder, and PXE, VMware vSphere Auto Deploy simplifies the task of managing ESXi installation and upgrade for hundreds of machines. New hosts are automatically provisioned based on rules defined by the user. Rebuilding a server to a clean slate is as simple as a reboot. To move between ESXi versions, you update a rule using the Auto Deploy PowerCLI and perform a test compliance and repair operation.
  • Unified CLI Framework. An expanded and enhanced esxcli framework offers a rich set of consistent and extensible commands, including new commands to facilitate on-host troubleshooting and maintenance. The framework allows consistency of authentication, roles, and auditing, using the same methods as other management frameworks such as vCenter Server and PowerCLI. You can use the esxcli framework both remotely as part of vSphere CLI and locally on the ESXi Shell (formerly Tech Support Mode).
  • New Virtual machine capabilities. ESXi 5.0 introduces a new generation of virtual hardware with virtual machine hardware version 8, which includes the following new features:

o    32-way virtual SMP. ESXi 5.0 supports virtual machines with up to 32 virtual CPUs, which lets you run larger CPU-intensive workloads on the VMware ESXi platform.

o    1TB virtual machine RAM. You can assign up to 1TB of RAM to ESXi 5.0 virtual machines.

o    Nonhardware accelerated 3D graphics for Windows Aero support. ESXi 5.0 supports 3D graphics to run Windows Aero and Basic 3D applications in virtual machines.

o    USB 3.0 device support. ESXi 5.0 features support for USB 3.0 devices in virtual machines with Linux guest operating systems. USB 3.0 devices attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to a virtual machine and accessed within it. USB 3.0 devices connected to the ESXi host are not supported at this time.

o    UEFI virtual BIOS. Virtual machines running on ESXi 5.0 can boot from and use the Unified Extended Firmware Interface (UEFI).

  • Graphical User Interface to configure multicore virtual CPUs. You can now configure the number of virtual CPU cores per socket in the Virtual Machine Properties view in the vSphere Web Client and the vSphere client. Previously this feature was only configurable through advanced settings.
  • Client-connected USB devices. USB devices attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to a virtual machine and accessed within it.
  • Smart card reader support for virtual machines. Smart card readers attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to one or more virtual machines and accessed within them. The virtual machine remote console, available in the vSphere Web Client and the vSphere Client, supports connecting smart card readers to multiple virtual machines, which can then be used for smart card authentication to virtual machines.
  • Expanded support for VMware Tools versions. VMware Tools from vSphere 4.x is supported in virtual machines running on vSphere 5.0 hosts. Additionally, the version of VMware Tools supplied with vSphere 5.0 is also compatible with ESX/ESXi 4.x.
  • Apple Mac OS X Server guest operating system support. VMware vSphere 5.0 adds support for the Apple Mac OS X Server 10.6 (“Snow Leopard”) as a guest operating system. Support is restricted to Apple Xserve model Xserve3,1 systems. For additional information, see the vSphere 5.0 RC Release notes.
  • Host UEFI boot support.vSphere 5.0 supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With UEFI you can boot systems from hard drives, CD-ROM drives, or USB media. Booting over the network requires the legacy BIOS firmware and is not available with UEFI.
  • Support for up to 512 virtual machines. vSphere 5.0 supports up to 512 virtual machines totaling a maximum of 2048 virtual CPUs per host.
  • Support for larger systems. vSphere 5.0 supports systems with up to 160 logical CPUs and up to 2TB RAM.
  • Improved SNMP support. vSphere 5.0 adds the capability to convert CIM indications to SNMP traps. Check with your hardware vendor to see whether their CIM provider supports this functionality. In addition, vSphere 5.0 now supports the Host Resources MIB (RFC 2790) and allows for finer control over the types of traps sent by the SNMP agent.
  • Storage DRS. This feature delivers the DRS benefits of resource aggregation, automated initial placement, and bottleneck avoidance to storage. You can group and manage similar datastores as a single load-balanced storage resource called a datastore cluster. Storage DRS makes VMDK placement and migration recommendations to avoid I/O and space utilization bottlenecks on the datastores in the cluster.
  • Policy-driven storage delivery. This solution allows you to have greater control and insight into characteristics of your storage resources. It also enables virtual machine storage provisioning to become independent of specific storage available in the environment. You can define virtual machine placement rules in terms of storage characteristics and monitor a virtual machine’s storage placement based on these administrator-defined rules. The solution delivers these benefits by taking advantage of the following items:

Storage

o    Integrating with Storage APIs – Storage Awareness to deliver storage characterization supplied by storage vendors.

o    Enabling the vSphere administrator to tag storage based on customer-specific descriptions.

o    Using storage characterizations to create virtual machine placement rules in the form of storage profiles.

o    Providing easy means to check a virtual machine’s compliance against these rules.

As a result, managing storage usage and choice in vSphere deployments has become more efficient and user-friendly.

  • VMFS5. VMFS5 is a new version of vSphere Virtual Machine File System that offers improved scalability and performance.
  • Accelerator. An accelerator has been delivered for specific use with View (VDI) workloads. With this option configured in ESXi, a read cache is constructed in memory that is optimized for recognizing, handling, and deduplicating VDI client images. The cache is managed from within the View Composer and delivers a significant reduction, as high as 90% by early estimates, in IOPS from each ESXi host to the storage platform holding client images. This reduction in IOPS enables large scaling of the number of clients in case multiple I/O storms, typical in large VDI deployments, occur.
  • iSCSI UI support. Usability improvements in this release include the ability to configure dependent hardware iSCSI and software iSCSI adapters along with the network configurations and port binding in a single dialog box using the vSphere Client. Full SDK access is also available for these configurations.
  • Storage I/O Control NFS support. vSphere 5.0 extends Storage I/O Control (SIOC) to provide cluster-wide I/O shares and limits for NFS datastores.
  • Storage APIs – Array Integration: Thin Provisioning. Offers an ability to reclaim blocks of a thin provisioned LUN on the array when a virtual disk is deleted.
  • Swap to SSD. vSphere 5.0 provides new forms of SSD handling and optimization. The VMkernel automatically recognizes and tags SSD devices that are local to ESXi or are on the network. In addition, the VMkernel scheduler is modified to allow ESXi swap to extend to local or network SSD devices, which enables memory overcommitment and minimizes performance impact.
  • 2TB+ LUN support. vSphere 5.0 provides support for 2TB+ VMFS datastores.
  • Storage vMotion snapshot support. Allows Storage vMotion of a virtual machine in snapshot mode with associated snapshots. You can better manage storage capacity and performance by leveraging flexibility of migrating a virtual machine along with its snapshots to a different datastore.
  • Enhanced Network I/O Control. vSphere 5.0 builds on network I/O control to allow user-defined network resource pools, enabling multi-tenancy deployment, and to bridge virtual and physical infrastructure QoS with per resource pool 802.1 tagging.
  • vNetwork Distributed Switch Improvements. vSphere 5.0 provides improved visibility into virtual machine traffic through Netflow and enhances monitoring and troubleshooting capabilities through SPAN and LLDP.
  • ESXi Firewall. The ESXi 5.0 management interface is protected by a service-oriented and stateless firewall, which you can configure using the vSphere Client or at the command line with esxcli interfaces. A new firewall engine eliminates the use of iptables and rule sets define port rules for each service. For remote hosts, you can specify the IP addresses or range of IP addresses that are allowed to access each service.
  • Next-generation browser-based vSphere Client. A browser-based, fully-extensible, platform-independent implementation of the vSphere Client based on Adobe Flex. The vSphere 5.0 release includes both the new browser-based client and the Windows-based client available in prior releases. In this release, the browser-based client includes a subset of the functionality available in the Windows-based client, primarily related to inventory display and virtual machine deployment and configuration.
  • vCenter Server Appliance. A vCenter Server implementation running on a pre-configured Linux-based virtual appliance. This appliance significantly reduces the time required to deploy vCenter Server and associated services and provides a low-cost alternative to the traditional Windows-based vCenter Server.
  • Inventory Extensibility. VMware customers and partners can extend vCenter Server in multiple ways, including the inventory, graphical user interface, and agents. vCenter Server includes a manager to monitor the extensions. By deploying extensions created by VMware partners, you can use vCenter Server as a unified console to manage your virtualized datacenter.
  • Solution Installation and Management. The vCenter Solutions Manager provides a consistent interface to configure and monitor vCenter-integrated solutions developed by VMware and third parties. It provides a simpler installation, configuration, and monitoring interface for managing solutions. Using the new vSphere ESX Agent Manager, you can deploy, update, and monitor vSphere agents on ESXi hosts. vSphere agents inter-operate efficiently with other vSphere features such as maintenance mode and distributed power management.
  • Enhanced logging support. vSphere 5.0 adds several enhancements to system message logging. All log messages are now generated by syslog, and messages can now be logged on either local and/or one or more remote log servers. A given server can log messages from more than one host. Log messages can be remotely logged using either the Secure Sockets Layer (SSL) or TCP connections. The vSphere syslog listener is available as an optional plug-in to vCenter on Windows; in the vCenter Virtual Appliance (VCVA), logging is accomplished using the native syslog-ng facility. With vSphere 5.0, log messages from different sources can be configured to go into different logs for more convenience. Configuration of message logging can also be accomplished using ESXCLI in addition to the vSphere client.
  • Fault Domain Manager — VMware High Availability has been transformed into a cloud-optimized availability platform. With Fault Domain Manager, VMware HA is more reliable in operation, more scalable in its ability to protect virtual machines, and can provide better uptime than before. All hosts in the cluster can now be primary nodes while the cluster also uses shared storage as a channel for host heartbeat detection. This enables VMware HA to react accurately and efficiently to host failures, allowing customers to grow their vSphere cluster.

Networking

  • Enhanced Network I/O Control. vSphere 5.0 builds on network I/O control to allow user-defined network resource pools, enabling multi-tenancy deployment, and to bridge virtual and physical infrastructure QoS with per resource pool 802.1 tagging.
  • vNetwork Distributed Switch Improvements. vSphere 5.0 provides improved visibility into virtual machine traffic through Netflow and enhances monitoring and troubleshooting capabilities through SPAN and LLDP.
  • ESXi Firewall. The ESXi 5.0 management interface is protected by a service-oriented and stateless firewall, which you can configure using the vSphere Client or at the command line with esxcli interfaces. A new firewall engine eliminates the use of iptables and rule sets define port rules for each service. For remote hosts, you can specify the IP addresses or range of IP addresses that are allowed to access each service.

VMware vCenter Server

  • Next-generation browser-based vSphere Client. A browser-based, fully-extensible, platform-independent implementation of the vSphere Client based on Adobe Flex. The vSphere 5.0 release includes both the new browser-based client and the Windows-based client available in prior releases. In this release, the browser-based client includes a subset of the functionality available in the Windows-based client, primarily related to inventory display and virtual machine deployment and configuration.
  • vCenter Server Appliance. A vCenter Server implementation running on a pre-configured Linux-based virtual appliance. This appliance significantly reduces the time required to deploy vCenter Server and associated services and provides a low-cost alternative to the traditional Windows-based vCenter Server.
  • Inventory Extensibility. VMware customers and partners can extend vCenter Server in multiple ways, including the inventory, graphical user interface, and agents. vCenter Server includes a manager to monitor the extensions. By deploying extensions created by VMware partners, you can use vCenter Server as a unified console to manage your virtualized datacenter.
  • Solution Installation and Management. The vCenter Solutions Manager provides a consistent interface to configure and monitor vCenter-integrated solutions developed by VMware and third parties. It provides a simpler installation, configuration, and monitoring interface for managing solutions. Using the new vSphere ESX Agent Manager, you can deploy, update, and monitor vSphere agents on ESXi hosts. vSphere agents inter-operate efficiently with other vSphere features such as maintenance mode and distributed power management.
  • Enhanced logging support. vSphere 5.0 adds several enhancements to system message logging. All log messages are now generated by syslog, and messages can now be logged on either local and/or one or more remote log servers. A given server can log messages from more than one host. Log messages can be remotely logged using either the Secure Sockets Layer (SSL) or TCP connections. The vSphere syslog listener is available as an optional plug-in to vCenter on Windows; in the vCenter Virtual Appliance (VCVA), logging is accomplished using the native syslog-ng facility. With vSphere 5.0, log messages from different sources can be configured to go into different logs for more convenience. Configuration of message logging can also be accomplished using ESXCLI in addition to the vSphere client.

Availability

  • Fault Domain Manager — VMware High Availability has been transformed into a cloud-optimized availability platform. With Fault Domain Manager, VMware HA is more reliable in operation, more scalable in its ability to protect virtual machines, and can provide better uptime than before. All hosts in the cluster can now be primary nodes while the cluster also uses shared storage as a channel for host heartbeat detection. This enables VMware HA to react accurately and efficiently to host failures, allowing customers to grow their vSphere cluster.

Avots: http://www.virtualizetips.com/2011/07/whats-new-in-vmware-vsphere-esxi-5/