Microsoft Azure Administrator

How to become Microsoft Azure Administrator:

Azure Administrators manage the cloud services that span storage, networking, and compute cloud capabilities, with a deep understanding of each service across the full IT lifecycle. They take end-user requests for new cloud applications and make recommendations on services to use for optimal performance and scale, as well as provision, size, monitor and adjust as appropriate. This role requires communicating and coordinating with vendors. Azure Administrators use the Azure Portal and as they become more proficient they use PowerShell and the Command Line Interface.

Below Some Prerequisites to quick cover Azure Administrators role:

Azure Administrators start this role with experience on operating systems, virtualization, cloud infrastructure, storage structures, and networking.

Also you can starts from scratch those does not having any experience.

• Understanding of on-premises virtualization technologies, including: VMs, virtual networking, and virtual hard disks.
• Understanding of network configuration, including TCP/IP, Domain Name System (DNS), virtual private networks (VPNs), firewalls, and encryption technologies.
• Understanding of Active Directory concepts, including domains, forests, domain controllers, replication, Kerberos protocol, and Lightweight Directory Access Protocol (LDAP).
• Understanding of resilience and disaster recovery, including backup and restore operations.

Find below are the topics you should cover and do hands-on exercise Azure portal access:

For practice you can use the free subscriptions.

• Administer Azure using the Azure portal, Cloud Shell, Azure PowerShell, CLI, and ARM templates.
• Plan for, create, and scale virtual machines.
• Implement Azure storage accounts, blob storage, Azure files, and shared access keys.
• Configure virtual networks including planning, IP addressing, Azure DNS, and network security groups.
• Configure data replication and backup files, folders, and virtual machines.
• Configure intersite connectivity solutions like VNet Peering, VNet-to-VNet connections, Site-to-Site connections, and ExpressRoute.
• Manage network traffic using service endpoints, network routing choices, Azure load balancer, Azure Traffic Manager, and Content Delivery Network.
• Manage subscriptions, accounts, users, groups, and billing. Implement Azure policies.
• Implement Azure Active Directory and Azure Active Directory Connect.
• Secure identities with MFA, Azure AD Identity Protection, AD Join, and Self-Service Password Reset.
• Share data using the Import and Export service, Data Box, and File Sync.
• Monitor Azure infrastructure with Azure Monitor, Azure alerts, Log Analytics, and Network Watcher.

 

***************************Happy Learning*****************************

Move physical Logs to other dbspace:

Overview:

When the database server initializes disk space, it places the physical log in the root dbspace. The initial size of the physical log is set by the PHYSFILE configuration parameter.

After initialize the database server for the first time, you can change the size or location of the physical log with the onparams utility.

To improve performance (specifically, to reduce the number of writes to the root dbspace and minimize disk contention), you can move the physical log out of the root dbspace to another dbspace, preferably to a disk that does not contain active tables or the logical-log files. For best performance, create the plogspace to store the physical log and allow the database server to expand the size of the physical log as needed to improve performance.

 

Run below commands to find out Physical log space:

$onstat –c |grep ^PHYS

Or

$ oncheck -pe physdbs

 

First create a chunk for new dbspace:

$cd /Informix/storage/IDS

$touch physdbs

$chmod 660 physdbs

 

Create a new dbspace and move the physical logs:

$onspaces -c -d physdbs -o -s 512000 -p <path_to_chunks>/physdbs

 

$ onparams -p -s 400000 -d physdbs

$ ontape -s -L 0

 

Note: Size is in kb.It is advisable to use the values from the online.log to set the size of the physical log or increase this a little bit more. Different values in the online.log are due to the differing loads at the time the log is written.

 

Confirm the changes have been applied but running the following and checking the results:

$oncheck -pe physdbs

 

 or

$onstat –c |grep ^PHYS

Find below difference between Plogspace and dbspace:

 

dbspace (vs) plogspace: When the physical log is in plogspace, the DB server increases the size of the physical log as needed to improve performance.

When the physical log is in dbspace, you must manually increase the size of the physical log.

To move the physical log to a dbspace, run the onparams -p -s command or the SQL administration API admin() or task() function with the create dbspace argument.

The following example changes the size and location of the physical log. The new physical-log size is 500 KB, and the log is in the dbspace11 dbspace:

onparams -p -s 500 -d dbspace11

*********Happy Learning*************

Informix DBA

Best Practices for Informix Database Administrator

This Course will focus on best practices for Informix DBA:

• Informix Products Overview
• Informix Architecture – Memory, CPU, Disk Requirements
• Planning an Informix Install
• Installing Informix
• Software Directory Structure
• Using Informix SQL
• Monitoring tools
• Monitoring configuration
• Monitoring Instance activity
• Monitoring database activity
• Monitoring session activity
• Monitoring performance
• Backup and Recovery
• High availability
• Migration
• Upgradetion

.................

.................

.................

...........Etc.

Email to:thedbaportfolio@gmail.com