
UNSOLVED
E
edn_migrator
32 Posts
0
2692
December 15th, 2008 11:00
Centera Proven Certification
This discussion thread has been imported from the Centera Developer Portal Forums.
The first message is shown here, and the complete thread is in the attached PDF file.
Please read the PDF and continue the discussion here.
From srxx@gmx.de
Posted: Fri Dec 28, 2007
Hi,
what exactly must my integration support, to get the centera proven logo?
Unfortunately the link
http://www.keylabs.com//emc-centera/files/remote_test_process.pdf
points to an empty PDF.
The program mentions:
# Basic Centera Capabilities: We verify the functionality of the Centera write, read, and delete capabilities that the tested application supports.
OK, the application writes, reads and deletes. What exactly is meant here?
# Centera Replication: We verify the application's support for Centera replication features.
This I do not understand. For me, replication is transparent, additionally some features can be controlled by SetGlobalOption or an env-var.
So what I have to do by programming here?
# Centera Disaster Recovery and Offsite Backup/Replication: We validate the application's support for Centera Multi-Cluster Failover to an Offsite Replica Cluster.
Must my application support disaster recovery?
Failover is transparent - isn't it?
What is an offsite replica cluster?
# Compliance Market and Retention: We verify the application's retention support and functionality.
The application calls clip.SetRentionPerid. Is this enough?
# Single Instance Storage: We verify the application's ability to offer single instance storage for identical objects.
Hm, this is transparent for me too - isn't it?
# Collision Avoidance: We verify the application's ability to support Collision Avoidance regardless of identical content.
What do I have to do here?
# Capacity Reporting: We verify application reporting of Centera capacity.
What do I have to do here?
Thank you
1 Attachment
Centera - Proven Certification.pdf
Centera - Proven Certification.pdf
Responses (0)
Solutions (0)
