Welcome to the latest review of our TechKrunch sessions, which are also known as the Randy and Glenn Show. I love the casual conversation, the morning coffee. Is there a better way to start your day than hanging out with these guys and digging into how to intelligently migrate, archive, manage, and optimize your enterprise unstructured data in the cloud?
Here are reviews of two recent sessions:
- TechKrunch: Using Komprise Data Analytics and Data Modeling
- TechKrunch: How to Find Hot Data for Migrations
This week’s focus is on how to access archived data in the cloud. Customers are always impressed with how we archive data in the cloud – they often ask us if they can access their data in its native format using other tools? The good news is that with Komprise, it’s easy.
So, let’s get to the demo.
- First, you create a target.
- In the Advanced section, select Native format. Unlike other tools that migrate or archive data in a proprietary format that cannot be read outside of the solution itself, Komprise uses open standards so your data is always available in the native format.
- So, now that you’ve run your analytics and you want to get your cold data to the S3 target, you go to Plan and start to build out your cloud strategy to archive that data with symbolic links and leave those behind.
- As you edit your Plan, select which type of data you want to tier off. If users haven’t accessed their data in two years, how much data would that be? You quickly see that it’s 10% of your data. Drop it to one year and you see that 19% of your data hasn’t been accessed.
- Now we’ll archive that data to S3.
- In addition to archiving data in the native format, you can also make a replicated copy in the native format. This would copy the data but not change the primary storage itself, giving you a readable copy of your data outside of Komprise for reporting, data protection, or some other reason.
- Activate the plan and your symbolic links get left behind. Archived data goes to AWS S3 and copied data goes to IBM Cloud Object Storage.
- Once the data has been moved, Komprise uses symbolic links (read about the difference between Stubs vs. Symbolic links), which looks like a shortcut to the end user.
So now you know how easy it is to archive data to the cloud transparently with Komprise, let’s dive into how to access the data.
Of course, the best way to access the data will be through the Komprise interface. But what about accessing the data using other tools?
- In this demonstration, Glenn uses S3 Browser and he points to an AWS lab.
- It’s easy to get to your file server data. Just login to Komprise type /diag into your Director url. This will give you several different diagnostics that you can use for troubleshooting.
- In this case Glenn is looking for the ID Map to see which file servers correspond to which IDs, so you know where you’re actually pointing.
- Back on the file server, we strip out metadata when we write out to S3 so we can put it back in when we do an actual read.
- In the data folder, I see my data with all of the properties. I can download to my local machine. I’m completely outside of Komprise. I can mount a drive and point to an S3 bucket, which means I can mount a drive with all of the trace files and log files from another server and do some data mining on it.
So, the beauty of what we demonstrated here is that with Komprise you aren’t locked in. Your data is always available to you. Of course, you can also write to NAS.
Pretty cool. Here’s the 15-minute session. Check it out and let us know if you have questions or feedback.
Next topic, you ask? It’s going to be about how to use the Komprise Confine functionality.
Thanks for sharing, guys. Be wise, Komprise!