How does Oracle Storage Cloud Software Appliance – Clou…

How does Oracle Storage Cloud Software Appliance – Cloud Distribution work?

How does Oracle Storage Cloud Software Appliance – Cloud Distribution work?

A.
It copies data from specified storage volumes in Oracle Compute Cloud Service to Oracle Storage Cloud
Service on demand.

B.
It stores all data in storage volumes attached to the Oracle Compute Cloud Service VM that hosts the
appliance and uploads only infrequently accessed data to Oracle Storage Cloud Service.

C.
It immediately writes data to containers in Oracle Storage Cloud Service as soon as applications write files
to the appliance.

D.
It uploads data to Oracle Storage Cloud Service according to the synchronization schedule defined by the
user.

E.
It caches data written by applications in storage volumes attached to the Oracle Compute Cloud Service
virtual machine (VM) that hosts the appliance and copies all the data asynchronously to Oracle Storage
Cloud Service.



Leave a Reply 10

Your email address will not be published. Required fields are marked *


Muk

Muk

B is correct answer . I think its a repeat question from before. Please read the wording of the E. You do not copy all data – only infrequently used data and cache the frequently used data. B says so. What is trick here is it is not saying only caches the frequently accessed data locally. So if it sends infrequent data to Cloud by upload and store all data locally then what is left?

nobody

nobody

E
Read the data sheet above link

German

German

Right “When applications running on the client instances write data to the mount points on
the instance, the data is cached on the appliance instance and then uploaded
asynchronously to your storage service instance in the cloud. Frequently accessed
data is cached on the appliance. You can configure the appliance cache size.”

babykeveen

babykeveen

A is wrong – doesnt copy
B is wrong – it does not upload ‘only infrequently’
C is wrong – it does not write to containers
D is wrong – no sync schedule
E is right – it caches data locally for speed and writes all up