How to Make Money Online Learn Secrets for FREE from Experts

Many of you search for a way to make money online. Here is a Simple,EASY & FREE way to learn How to make Money Online.

You can make money online if you just have a service or a product which can be sold or you can have money because of some simple things like writing articles, creating content etc. With all those things you might make just few hundred dollars a month. But if you go through this link
"Search Engine Optimization" you can make a lot more money. Since using Search Engine Optimization you can get hundreds of visitors who are very much looking for the service or product you are selling.

This is FREE hence I am writing about it go here "FREE Secrets to Make Money Online"

This is not some cheap ebook they are going to send you a Video DVD along with lot more for almost FREE & this DVD has several Videos which explain how to make money online.

Go here Order for FREE watch this Video you will know this thing which they are giving away for FREE is worth a thousand dollar.

This product is from the industry leading team called Stompernet . Lots of people pay them to get the same secrets.

------
Subject: "Stomping the Search Engines 2" and "The Net Effect"
for HOW MUCH?

Hey

Andy Jenkins has finally given me the all-clear to spill the
beans on this insane offer that StomperNet has cooked up.

Tomorrow, Sept. 3rd at 3pm Eastern, you can get StomperNet's
big daddy expert SEO Video Course, "Stomping the Search Engines
2"... for FREE.

That's right. FREE.

All you need to do is just TRY their new monthly printed Action
Journal called "The Net Effect" - and guess what?...

You get the PREMIER ISSUE of "The Net Effect" for FREE TOO!

You don't pay one penny more than Shipping and Handling unless
you LOVE it and want to get issue 2 a month from now.

That's NUTS. They are betting the FARM that you will LOVE this
stuff and stick around for more. That takes GUTS, and and HUGE
confidence in the quality of their stuff.

But then again, it's StomperNet. I've SEEN the stuff, and can
vouch. It would be worth FULL PRICE.

But for FREE? You'd be FOOLISH not to check this out.

Don't believe it? Watch this video they've released to the
public. No fooling - this is a FOR-REAL DEAL.

https://member.stompernet.net/?r=1324&i=68

This MIGHT just change your online business fortunes...
forever.

P.S. There's no hint of scarcity here - they've got tons of
BOTH products ready to ship. But still - be there EARLY. If I
hadn't already gotten my "insider" review copy, I'd be the
FIRST one on this page tomorrow.

Citrix Interview Questions

Citrix Interview Questions

1. What is the requirement for Citrix server installation.

2. What is Data store

3. What is Data collector

4. What is LHC

5. What is Client Lock Down

6. What is Printer terminology in Citrix

7. How to use datastore for database

8. What is the difference between all citrix versions

9. What are different load evaluators are available in Citrix

10. How to implement Policies in Citrix

11. What you will check when any user is not able to launch citrix application.

12. What is IMA

 

Windows Sysadmin Interview Question

1.      What is Active Directory schema?

2.      What are the domain functional level in Windows Server 2003?

3.      What are the forest functional level in Windows Server 2003?

4.      What is global catalogue server?

5.      How we can raise domain functional & forest functional level in Windows Server 2003?

6.      Which is the default protocol used in directory services?

7.      What is IPv6?

8.      What is the default domain functional level in Windows Server 2003?

9.      What are the physical & logical components of ADS

10.  In which domain functional level, we can rename domain name?

11.  What is multimaster replication?

The Active Directory schema contains formal definitions of every object class that can be created in an Active Directory forest it also contains formal definitions of every attribute that can exist in an Active Directory object. Active Directory stores and retrieves information from a wide variety of applications and services. So that it can store and replicate data from a potentially infinite variety of sources, Active Directory standardizes how data is stored in the directory. By standardizing how data is stored, the directory service can retrieve, update, and replicate data while ensuring that the integrity of the data is maintained.

Schema master is a set of rules which is used to define the structure of active directory. It contains definitions of all the objects which are stored in AD. It maintains information and detail information of objects.

.What is global catalog server?

A global catalogue server is a domain controller it is a master searchable database that contains information about every object in every
domain in a forest. The global catalogue contains a complete replica of all
objects in Active Directory for its host domain, and contains a partial replica
of all objects in Active Directory for every other domain in the forest.
It have two important functions:
i)Provides group membership information during logon and authentication
ii)Helps users locate resources in Active Directory

1.      The two technologies in DFS are as follows:

DFS Replication. New state-based, multimaster replication engine that is optimized for WAN environments. DFS Replication supports replication scheduling, bandwidth throttling, and a new byte-level compression algorithm known as remote differential compression (RDC).

DFS Namespaces. Technology that helps administrators group shared folders located on different servers and present them to users as a virtual tree of folders known as a namespace. DFS Namespaces was formerly known as Distributed File System in Windows 2000 Server and Windows Server 2003.

1.      1. DNS(Domain Name Service):
—————————-
It’s mainly used to resolve from host name(FQDN-Fully Qualified Domain Name) to IP address and IP address to host name.DNS mainly used in Internet. DNS divide in form of hierarchical.

2. DHCP(Dynamic Host Configuration Protocol):
———————————————
DHCP use for provide IP address dynamically to client machine. If that client not able to find DHCP server then client machine will go for APIPA(We have range for APIPA which is 169.254.0.1-169.254.255.254).

3. HUB and SWITCH:
——————
Switch is expensive than hub. If more then one user try to send packet at a time collision will occure but in switch we can send. Switch is full duplex. Maximum bandwidth is 100 Mhz and that bandwidth is shared by all of the PC’s connected to the hub. Data can be sent in both directions simultaneously, the maximum available bandwidth is 200 Mbps, 100 Mbps each way, and there are no other PC’s with which the bandwidth must be shared.

 

 

 

 

 

 

Know more about extension of the snia shared storage model to tape functions logical and physical structure of tapes and Extension of the model

Know more about extension of the snia shared storage model to tape functions logical and physical structure of tapes and Extension of the model

The SNIA Shared Storage Model described previously concentrates upon the modelling of disk-based storage architectures. In a supplement to the original model, the SNIA Technical Council defines the necessary extensions for the description of tape functions and back-up architectures.

The SNIA restricts itself to the description of tape functions in the Open Systems environment, since the use of tapes in the mainframe environment is very difficult to model and differs fundamentally from the Open Systems environment. In the Open Systems field, tapes are used almost exclusively for back-up purposes, whereas in the field of mainframes tapes are used much more diversely. Therefore, the extension of the SNIA model concerns

itself solely with the use of tape in back-up architectures. Only the general use of tapes in shared storage environments is described in the model.

The SNIA does not go into more depth regarding the back-up applications themselves. We have already discussed network back-up in Chapter 7. More detailed information on tapes can be found in Section 9.2.1. First of all, we want to look at the logical and physical structure of tapes from the

point of view of the SNIA Shared Storage Model (10.3.1). Then we will consider the differences between disk and tape storage (10.3.2) and how the model is extended for the description of the tape functions (10.3.3).

 Logical and physical structure of tapes

Information is stored on tapes in so-called tape images, which are made up of the following

logical components (Figure 10.20):

• Tape extent A tape extent is a sequence of blocks upon the tape. A tape extent is comparable with a volume in disk storage. The IEEE Standard 1244 (Section 9.5) also uses the term volume but it only allows volumes to reside exactly on one tape and not span multiple tapes.

• Tape extent separator The tape extent separator is a mark for the division of individual tape extents.

• Tape header The tape header is an optional component that marks the start of a tape.

• Tape trailer The tape trailer is similar to the tape header and marks the end of a tape. This, too, is an optional component. In the same way as logical volumes of a volume manager extend over several physical disks, tape images can also be distributed over several physical tapes. Thus, there may be precisely one logical tape image on a physical tape, several logical tape images on a physical tape, or a logical tape image can be distributed over several physical tapes. So- called tape image separators are used for the subdivision of the tape images (Figure 10.21). 10.3.2 Differences between disk and tape At first glance, disks and tapes are both made up of blocks, which are put together to form long sequences. In the case of disks these are called volumes, whilst in tapes they are called extents. The difference lies in the way in which they are accessed, with disks being designed for random access, whereas tapes can only be accessed sequentially. Consequently, disks and tapes are also used for different purposes. In the Open Sys- tems environment, tapes are used primarily for back-up or archiving purposes. This is completely in contrast to their use in the mainframe environment, where file structures – so-called tape files – are found that are comparable to a file on a disk. There is no definition of a tape file in the Open systems environment, since several files are generally bundled to form a package, and processed in this form, during back-up and archiving.

This concept is, therefore, not required here.

 Extension of the model

The SNIA Shared Storage Model must take into account the differences in structure and application between disk and tape and also the different purposes for which they are used. To this end, the file/record layer is expanded horizontally. The block layer, which produces the random access to the storage devices in the disk model, is exchanged for a sequential access block layer for the sequential access to tapes. The model is further supplemented by the following components (Figure 10.22):

• Tape media and tape devices Tape media are the storage media upon which tape images are stored. A tape devices is a special physical storage resource, which can process removable tape media. This differentiation between media and devices is particularly important in the context

of removable media management (Chapter 9). The applicable standard, IEEE 1244, denotes tape media as cartridge and tape device as drive.

• Tape applications The SNIA model concentrates upon the use of tapes for back-up and archiving. Special tape applications, for example, back-up software, are used for back-up. This software can deal with the special properties of tapes.

• Tape format system In the tape format system, files or records are compressed into tape extents and tape images. Specifically in the Open Systems environment, the host generally takes over this task. However, access to physical tape devices does not always have to go through the tape format system. It can also run directly via the extent aggregation layer described below or directly on the device.

• Extent aggregation layer The extent aggregation layer works in the same way as the block aggregation layer (Section 10.1.7), but with extents instead of blocks. However, in contrast to the random access of the block aggregation layer, access to the physical devices takes place

sequentially. Like the access paths, the data flows between the individual components are shown as arrows.

Know more on Asymmetric file services: NAS/file server metadata manager Object-based storage device (OSD)

Know more on  Asymmetric file services: NAS/file server metadata manager Object-based storage device (OSD)

A file server metadata manager (Figure 10.18) works in the same way as asymmetric storage virtualization on file level (Section 5.7.2):

• Hosts and storage devices are connected via a storage network.

• A metadata manager positioned outside the data path stores all file position data, i.e. metadata, and makes this available to the hosts upon request.

• Hosts and metadata manager communicate over an expanded file-oriented protocol.

• The actual user data then flows directly between hosts and storage devices by means of a block-oriented protocol. This approach offers the advantages of fast, direct communication between host and storage devices, whilst at the same time offering the advantages of data sharing on

file level. In addition, in this solution the classic file sharing services can be offere

in a LAN over the metadata manager.

 Object-based storage device (OSD)

The SNIA Shared Storage Model defines the so-called object-based storage device (OSD) The idea behind this architecture is to move the position data of the files and the access rights to a separate OSD. OSD offers the same advantages as a file sharing solution,combined with increased performance due to direct access to the storage by the hosts, and central metadata management of the files. The OSD approach functions as follows

(Figure 10.19):

• An OSD device exports a large number of byte vectors instead of the LUNs used in block-oriented storage devices. Generally, a byte vector corresponds to a single file.

• A separate OSD metadata manager authenticates the hosts and manages and checks the access rights to the byte vectors. It also provides appropriate interfaces for the hosts.

• After authentication and clearance for access by the OSD metadata manager, the hosts access the OSD device directly via a file-oriented protocol. This generally takes place via a LAN, i.e. a network that is not specialized for storage traffic.

 

Free tutors on Storage network attached block storage Block storage aggregation in a storage device: Network attached block storage with metadata and File server controller: NAS heads

Free tutors on Storage network attached block storage Block storage aggregation in a storage device: Network attached block storage with metadata and File server controller: NAS heads

 Multi-site block storage file servers File server controller: NAS heads

The connection from storage to host via a storage network can be represented in the Shared Storage Model as shown in Figure 10.12. In this case:

• Several hosts share several storage devices.

• Block-oriented protocols are generally used.

• Block aggregation can be used in the host, in the network and in the storage device.

 Block storage aggregation in a storage device:

SAN appliance Block aggregation can also be implemented in a specialized device or server of the storage network in the data path between hosts and storage devices, as in the symmetric storage virtualization (Figure 10.13, Section 5.7.1). In this approach:

• Several hosts and storage devices are connected via a storage network.

• A device or a dedicated server – a so-called SAN appliance – is placed in the data path between hosts and storage devices to perform block aggregation, and data and metadata traffic flows through this.

 Network attached block storage with metadata

server: asymmetric block services The asymmetric block services architecture is identical to the asymmetric storage virtualization approach (Figure 10.14, Section 5.7.2):

• Several hosts and storage devices are connected over a storage network.

• Host and storage devices communicate with each other over a protocol on block level.

• The data flows directly between hosts and storage devices.

• A metadata server outside the data path holds the information regarding the position of the data on the storage devices and maps between logical and physical blocks.

 Multi-site block storage

Figure 10.15 shows how data replication between two locations can be implemented  means of WAN techniques. The data can be replicated on different layers of the mo using different protocols:

• between volume managers on the host;

• between specialized devices in the storage network; or

• between storage systems, for example disk subsystems.

If the two locations use different network types or protocols, additional converters can be installed for translation.

 File server

A file server (Section 4.2) can be represented as shown in Figure 10.16. The following points are characteristic of a file server:

• the combination of server and normally local, dedicated storage;

• file sharing protocols for the host access;

• normally the use of a network, for example, a LAN, that is not specialized to the storage traffic;

• optionally, a private storage network can also be used for the control of the dedicated storage.

 File server controller: NAS heads

In contrast to file servers, NAS heads (Figure 10.17, Section 4.2.2) have the following properties:

• They separate storage devices from the controller on the file/record layer, via which the hosts access.

• Hosts and NAS heads communicate over a file-oriented protocol.

• The hosts use a network for this that is generally not designed for pure storage traffic, for example a LAN.

• When communicating downwards to the storage devices, the NAS head uses a block-oriented protocol.

NAS heads have the advantage over file servers that they can share the storage systems with other hosts that access them directly. This makes it possible for both file and block services to be offered by the same physical resources at the same time. In this manner, IT architectures can be designed more flexibly, which in turn has a positive effect upon scalability.

Free tutors on Clustering Storage, data and information The service subsystem examples of disk-based storage architectures

Free tutors on  Clustering Storage, data and information The service subsystem examples of disk-based storage architectures

A cluster is defined in the SNIA Shared Storage Model as a combination of resources with the objective of increasing scalability, availability and management within the shared storage environment (Section 6.4.1). The individual nodes of the cluster can share their resources via distributed volume managers (multi-node LVM) and cluster file systems (Figure 10.8, Section 4.3).

 Storage, data and information

The SNIA Shared Storage Model differentiates strictly between storage, data and information. Storage is space – so-called containers – provided by storage units, on which the data is stored. The bytes stored in containers on the storage units are called data. Information is the meaning – the semantics – of the data. The SNIA Shared Storage Model names the following examples in which data–container relationships arise (Table 10.1).

10.1.14 Resource and data sharing In a shared storage environment, in which the storage devices are connected to the host via a storage network, every host can access every storage device and the data stored upon it (Section 1.2). This sharing is called resource sharing or data sharing in the SNIA model, depending upon the level at which the sharing takes place (Figure 10.9). If exclusively the storage systems – and not their data content – are shared, then we talk of resource sharing. This is found in the physical resources, such as disk subsystems and tape libraries, but also within the network. Data sharing denotes the sharing of data between different hosts. Data sharing is significantly more difficult to implement, since the shared data must always be kept consistent, particularly when distributed caching is used. Heterogeneous environments also require additional conversion steps in order to convert the data into a format that the host can understand. Protocols such as NFS or CIFS are used in the more frequently used data sharing within the file/record layers

. For data sharing in the block layer, server clusters with shared disk file systems or parallel databases are used

 The service subsystem

Up to now we have concerned ourselves with the concepts within the layers of the SNIA Shared Storage Model. Let us now consider the service subsystem (Figure 10.10). Within the service subsystem we find the management tasks which occur in a shared storage environment and which we have, for the most part, already discussed in Chapter 8. In this connection, the SNIA Technical Council mention:

• discovery and monitoring

• resource management

• configuration

• security

• billing (charge-back)

• redundancy management, for example, by network back-up

• high availability

• capacity planning.

The individual subjects are not yet dealt with in more detail in the SNIA Shared Storage Model, since the required definitions, specifications and interfaces are still being developed (Section 8.7.3). At this point we expressly refer once again to the check list in the

Appendix B, which reflects a cross-section of the questions that crop up here.

EXAMPLES OF DISK-BASED STORAGE ARCHITECTURES

In this section we will present a few examples of typical storage architectures and their properties, advantages and disadvantages, as they are represented by the SNIA in the Shared Storage Model. First of all, we will discuss block-based architectures, such as the direct connection of storage to the host (Section 10.2.1), connection via a storage network (Section 10.2.2), symmetric and asymmetric storage virtualization in the network

(Section 10.2.3 and Section 10.2.4) and a multi-site architecture such as is used for data replication between several locations (Section 10.2.5). We then move on to the file/record layer and consider the graphical representation of a file server (Section 10.2.6), a NAS head (Section 10.2.7), the use of metadata controllers for asymmetric file level virtualization (Section 10.2.8) and an object-based storage device (OSD), in which the position

data of the files and their access rights is moved to a separate device, a solution that combines file sharing with increased performance due to direct file access and central metadata management of the files (Section 10.2.9). 10.2.1 Direct attached block storage Figure 10.11 shows the direct connection from storage to the host in a server-centric architecture. The following properties are characteristic of this structure:

• No connection devices, such as switches or hubs, are needed.

• The host generally communicates with the storage device via a protocol on block level.

• Block aggregation functions are possible both in the disk subsystem and on the host.