API information for archival

Hi Susana,

welcome to the forum.

Yes, this is possible and there are two ways to do this.

The first is to use the Celerra builtin FileMover (DHSM) functionality.
There the Celerra file system understand a stub file type that contains the attributes of a file plus information about where the file data is actually located.

If you "archive store" is accessible over NFS or CIFS the Celerra actually has a client builtin in so that it can do the recall internally without bothering your "policy engine"
That has the adavantage that the policy engine only has to do the scheduling, migrate-out and management, but isnt in the data-path for actual client access.
Which improves performanace and scalability - also if your "policy engine" is down it wouldnt have an impact on client access to archived files

If the archive store is accessible through other means we for example "post" html events to the "policy engine" and ask it to recall the data.

see the attached FileMover manuals for the full concepts.

The other way would be to use the Celerra Event Enable API (CEPA/CEE).
This allows you to specify a third party to be notified on access or meta-data changes certain files in a file system.
It can be used blocking or non-blocking - like for on-access anti-virus application or quota management or content filtering.
It requires the EMC CEE framework to be installed on a Windows server.

I believe in order to get access to the actual API's you need to become a member of the EMC partner program.

As far as API's go I think it depends on what option you are implementing - some have their own API's, some use the XML API
Even if you can use the CLI through an ssh to the control station its preferable to use an API that talks directly to the data movers for scalability and security reasons.

regards
Rainer

attachments

For Celerra Simulator you can find some step-by-step guides here
http://virtualgeek.typepad.com/virtual_geek/2008/06/get-yer-celerra.html

Hi Rainer,

Thanks a lot for the reply. The documents helped me a lot to understand. I have few more queries on the replies.
1. I learnt from the CEE document that it is providing the support only on CIFS protocol. Is there any new enhancements from EMC in feature to provide support on NFS also?

2. In case it provides the support only for CIFS protocol, my HSM work will only be based on Windows but not on linux or Mac. Am I right? Or can I install the CEE package on linux and configure the linux to use CIFS instead of NFS?

3. If I install CEE on my machine after downloading, will it be sufficient to start the development or will it requires and SDK for it? Please can you list me the required tools also for it?

4. Can I have the path for CEE and CEPA installer on the EMC site as I have the EMC partner program.

Hi Susanna,

yes CEE is CIFS only. I cant say what's planned for the future - you would have to discuss that with product management.

The CEE framework is Windows based so you cant run it on a Linux server.
Not just that but it will only raise "events" based on CIFS traffic on the Celerra and not for NFS or ftp.

I dont know about the programming side.
If you dont mind I can forward your name and EMail to the product manager.

CAVA/CEE is on Powerlink in
Home > Support > Software Downloads and Licensing > Downloads C > Celerra Anti Virus Agent ( CAVA )
but I'm not sure if its available on your Powerlink view.

For HSM type applications we really recommend using the FileMover (DHSM) API on the Celerra.
I was built for that use case whereas CEE is for quota or auditing.

regards
Rainer

Hi Susana,

Unfortunately, this is the wrong forum for addressing questions about details of how to use or integrate with the APIs.

Since Atempo is part of Celerra API program you already have the partner API support contact details for the APIs. I believe you already have an email in to the partner program office as well. Those are the correct avenues to get support with integrating to the APIs.

Thanks,
Chris