6
December

AWS – Cloud Practitioner

This was a nice get. The exam was interesting. While I was a confirmed pass at the end there was no printout or results until the following day.

AWS Certified Cloud Practitioner

The AWS Cloud Practitioner exam enables individuals with an overall understanding of the AWS Cloud to validate their knowledge with an industry-recognized credential. It provides individuals in a larger variety of cloud and technology roles with a way to validate their AWS Cloud knowledge and enhance their professional credibility.

No comments yet

4
December

AWS – Sysops – creating a VPC with ELB

Previously, we had created a VPC using a lot of the defaults and embedded tools. This is VPC creation from scratch, enjoy.

No comments yet

6
November

AWS – Introduction to Glacier

no comments

1
November

AWS – Introduction to VPCs

no comments

27
October

AWS – Introduction to EBS

no comments

25
October

AWS – Introduction to EC2

no comments

24
October

AWS – Introduction to S3

no comments

13
June

A new start

I started this blog in 2012 when I was assigned to a new client and had to get up to speed with NetWorker. The purpose was to capture any and all learning’s here. Four years and close to 80 posts later, it has been an invaluable tool to capture and share knowledge. It’s not unusual for me to look up past issues here or to google them, only to be redirected to my own blog. I never considered an issue resolved, until it was captured here. Not unusual for others to find their way here also. Stats for the last month show 656 hits, mostly from India and the U.S. Its good to know I’m not here alone screaming in the dark.

 

 

Today I find myself at the start of a new opportunity with many great challenges and things to learn. So, expect this blog to not only be a great place for capturing knowledge for NetWorker and Avamar. It will now be a repository for new learning’s related to my old friend NetBackup, as well as storage and virtualization.

no comments

13
June

Getting familiar with cmode

Had a request from my client to upload some logs. These logs were required for some c-mode systems and required access to the systemshell. Having completed some troubleshooting recently for 7-mode, the process was not altogether unfamiliar but was slightly different

The diag user is required. So lets check the status. Is it locked? Do we know the password? Lets hope.

blob0::> security login show -username diag

Username Application method Role Name Acct locked
diag            console        passwd  admin           no

Enter priv mode
set -privilege advanced

After confirming the password we can access the systemshell

blob0::>system node systemshell -node blob0n01

Fascinating, I know

no comments

29
November

Avamar – expiring snapups

 

 

il_fullxfull.329221825

In a perfect world, you should never need this command. As my friend Ian Anderson wrote in a great Ask the experts session  where he spoke of achieving  “Avamar Zen”.

Avamar Zen is a state of harmony, where you have achieved a steady state of data ingestion vs data expiration. Where hopefully, you have more data expiring and being cleaned by the garbage collection than you have new data coming in.  However, zen can be hard to achieve. Avamar is an amazing product. If the SE’s have done their job and sized it properly, you should realize steady state. What does happen sometimes is, the client is so impressed they begin adding more systems and workloads that were outside of the initial sizing scope.

Years ago, when I was embedded onsite we ran into such an issue. It wasn’t so much about adding to many systems, but one in particular.  We had some groups, one configured to cross mount points and another to only protect local data. A co-worker spun up a new system and instead of checking with me, added the system himself to Avamar, and the wrong group.

The next day I arrive and find my Avamar grid is filled, also this was replicated over to the secondary. Quite the mess. So just roll the system back to a previous checkpoint? You may think, unfortunately when an Avamar system has reached capacity there is not enough space for the required overhead to engage the checkpoint roll-back. Now, lets meet our friend expire-snapshots.

What does it do? What do you think it does? It expires snaps! Awesome, right? What is really cool is how it does this. The command runs with switches where you can granulary target specific data to remove. For example, if you wanted to remove all data from Nov 30, 2015 and the previous 25 days, you would run the following

expire-snapups –before=’2015-11-30′ –days=25 –domain=/ > do-expire.sh

This will create a script in tmp you can then run and wipe out the offending data.

There are other switches available to target specific data and clients. When complete, settle in for a long garbage collect to run and turf the offending client.

When complete, I hope you can achieve “Avamar Zen” as I did. I also changed the admin password, so my helpful co-worker could not again repeat the same mistake.

 

no comments

Back to top