Elevated Task Manager Shortcut on Windows 7

Sunday, November 9, 2014

Received a replacement laptop so now I have to perform some software installs and configure it the way I had my old laptop.  To get Task Manager to display All Processes without having to select this option every time, it must run as Administrator.  Searched Google and found this link which describes how to setup an elevated task manager shortcut which you can then pin to the taskbar.


Where are the Folder Options in Windows 2008?

Wednesday, October 16, 2013

For whatever reason, I can never remember where the Folder Options tabs are located in Windows 2008.  Adding a note here for future reference.  The same applies for Windows 7.

Go to Control Panel / Folder Options


iPod Classic Adventures

Tuesday, October 15, 2013

Every couple of months, my daughter comes home with some new challenge for me to resolve with her iPod Classic.  I thought resetting the iPod would solve just about anything she could possibly do to inhibit the normal function of the device.  That is until she decided to set a passcode and promptly forgot what she set it to.  I quickly discovered there is no relying on the old “Reset” method.

Fortunately, a quick search of “ipod classic forgot passcode” on Google yields a YouTube video to solve the problem. The instructions are simple to follow and gave me a little insight on how Apple went about locking the device.

This post is a little out of the norm from my prior postings, but  I am sure I will reference this again in due time.  I am thankful for Google, YouTube, and the person responsible for posting “Unlocking Ipod Classic (Without Having to Restore To Factory Settings)”.


RTO and RPO

Monday, October 14, 2013

What is the difference between Recovery Time Objective (RTO) and Recovery Point Objective (RPO)?  That was a question that came up recently in a disaster recovery discussion.  Good explanation provided by Dejan Kosutic’s Blog entry.

In summary:

  • Recovery Time Objective (RTO) is “target time set for resumption of product, service or activity delivery after an incident”.
  • Recovery Point Objective (RPO) is “the maximum tolerable period in which data might be lost”.

PowerPoint Presentations

Monday, March 25, 2013

Began researching some information regarding PowerPoint Presentations.  Listing a few important summary items that stood out for me to keep focused with future presentations.  Sometimes I get so caught up in the moment and briefly lose sight of the main objective.

  • Know your audience
  • Audience needs to know:
    • Where we are now
    • Where we want to end up
    • How we are going to get there
  • Slide content:
    • Problem
    • Solution or options including costs
    • Timeline
    • Summarize call to action

Always looking for ways to improve, especially with presentation material, found information helpful on microsoft at work.  One point that resonates with me:

“A well-chosen chart or diagram can often convey much more to your audience than can boring bulleted text.”

Additional References

Books


NetApp Crash-Consistent Snapshots

Monday, February 27, 2012

We performed a disaster recovery (DR) test at our DR site in October 2011 which involved recovering Oracle database VMs with storage on a  SAN.  Once the database VM was recovered from a NetApp volume snapshot, it was started and we discovered Oracle went through its usual crash recovery and the database was running as expected.  No need for me to recover using the online (hot) backup files.

This prompted me to investigate whether this is a valid way to recover the Oracle database VMs for disaster recovery. I found a NetApp Technical Report called “Using Crash-Consistent Snapshot Copies as Valid Oracle Backups” which appears to support my discovery during the disaster recovery test.  I highly recommend reading the report as it contains valuable information on Oracle backup and recovery functionality.

Just a little background on our environment.  The Oracle databases are used for development so some data discard is acceptable.  The database VMs are backed up (snapshot/volume) nightly using VSC/SMVI.  The NetApp volume snapshots are copied to tape which are used to restore the data at DR.

The document describes a crash-consistent image in section 6.

“Some customers would like to have the ability to capture a backup of an online database without requiring the database to be in backup mode. In such a circumstance, the backup copy (if implemented correctly) will be technically equivalent to an image of a crashed database. That is, it is in a state similar to an image of an Oracle Database that has experienced an abrupt power loss, a server crash, or a shutdown abort. Such images are described as crash consistent.

When an instance fails or crashes, the data in the buffers of the SGA are not written to the data files, and a special flag in the control file is not set to indicate that it was a normal shutdown. Therefore, when a crash image is started, it triggers an automatic crash recovery to be performed by Oracle where the necessary redo contents are applied. This process brings the data files to a transaction-consistent state by rolling back uncommitted transactions and preserving all committed changes up to the point when the instance failed. A crash-consistent image without physical corruption can be reliably started and recovered by Oracle’s automatic crash recovery operation.”

Section 6.1 references My Oracle Support Note ID 604683.1 regarding Oracle’s guidelines for supporting third-party snapshot technology as a backup/restore solution.  Oracle will officially support backup, restore and recovery operations using third-party snapshot technologies assuming that the third party snapshot technology can meet the prerequisites.  Oracle states:

“The third party vendor needs to guarantee and held accountable that their snapshots conform to all the following requirements:

  • Integrated with Oracle’s recommended restore and recovery operations
  • Database crash consistent at the point of the snapshot
  • Write ordering is preserved for each file within a snapshot”

Our NetApp snapshot covers the last two bullet points above for our disaster recovery purposes.  Those points are supported in section 6.4 of the report shown below.   Our database files all reside on the same volume thereby preserving write ordering.

“A crash-consistent image is equivalent to or consistent with a copy of a database image after the database instance, server, or storage system has crashed.

When a checkpoint or snapshot is created by the storage system, OS utility, or user without any coordination with the source application (such as when a snapshot is created of an active database without it being in hot backup mode), the resulting snapshot is usually not crash consistent unless the copy utility has the capability to capture a consistent image across multiple volumes or storage systems.

If a database has all of its files (control files, data files, online redo logs, and archived logs) contained within a single NetApp volume, then the task is straightforward. A Snapshot copy of that single volume will provide a crash-consistent copy.”

We will continue to perform the traditional online backup mode (ALTER TABLESPACE BEGIN BACKUP/END BACKUP) which may be necessary in some situations, however for disaster recovery the volume snapshot restore will provide a more efficient restoration of the Oracle database VM.

Additional References
Using Crash-Consistent Snapshot Copies as Valid Oracle Backups

My Oracle Support – Supported Backup, Restore and Recovery Operations using Third Party Snapshot Technologies [ID 604683.1]


Memory Limits for Windows Releases

Saturday, December 10, 2011

When I need to reference the physical memory limits for Windows Operating Systems, I seem to waste time trying to locate my notes or searching the Internet.  I am posting here so I can remember.  Found the information on Microsoft’s site and will use it for future reference.

Below are the Operating Systems and Editions I reference most frequently.

Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

Version

Limit on X64

Windows Server 2008 R2 Datacenter

2 TB

Windows Server 2008 R2 Enterprise

2 TB

Windows Server 2008 R2 Foundation

8 GB

Windows Server 2008 R2 Standard

32 GB

Windows Server 2003 R2

The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version

Limit on X86

Limit on X64

Windows Server 2003 R2 Datacenter Edition

64 GB

1 TB

Windows Server 2003 R2 Enterprise Edition

64 GB

1 TB

Windows Server 2003 R2 Standard Edition

4 GB

32 GB


Follow

Get every new post delivered to your Inbox.