500 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
Many operating systems and applications provide mechanism to stop I/O operations and 
ensure that all data is flushed from host cache. If these mechanisms are available, they can 
be used with snapshot operations. When these mechanisms are not available, it might be 
necessary to flush the cache manually by quiescing the application and unmounting the file 
system or logical drives.
When choosing cloud object storage as a backup solution, be aware that the object storage 
must be managed as a whole. Backup and restore of individual files, folders, and partitions, 
are not possible.
To interact with cloud service providers or a private cloud, the IBM Spectrum Virtualize 
requires interaction with the correct architecture and specific properties. Conversely, cloud 
service providers offered attractive prices per object storage in cloud and deliver an 
easy-to-use interface. Normally, cloud providers offer low-cost prices for object storage space, 
and charges are applied for the cloud outbound traffic only.
11.3.3  Restore using Transparent Cloud Tiering
Transparent Cloud Tiering can also be used to restore data from any snapshot that is stored 
in cloud providers. When the cloud accounts’ technical and security requirements are met, 
the storage objects in the cloud can be used as a data recovery solution. The recovery 
method is similar to backup, except that the reverse direction is applied. Transparent Cloud 
Tiering running on IBM Spectrum Virtualize queries for object storage stored in a cloud 
infrastructure. It enables users to restore the objects into a new volume or set of volumes.
This approach can be used for various applications, such as recovering your production 
database application after an errant batch process that caused extensive damage. 
The restore of individual files using Transparent Cloud Tiering is not possible. As mentioned, 
object storage is unlike a file or a block so object storage must be managed as a whole unit 
piece of storage, and not partially. Cloud object storage is accessible by using an 
HTTP-based REST API.
11.3.4  Transparent Cloud Tiering restrictions
This section describes the following restrictions that must be considered before using 
Transparent Cloud Tiering:
/SM590000Because the object storage is normally accessed by using the HTTP protocol on top of a 
TPC/IP stack, all traffic that is associated with cloud service flows through the node 
management ports.
/SM590000The size of cloud-enabled volumes cannot change. If the size of the volume changes, a 
snapshot must be created so that a new Object Storage is constructed.
/SM590000Transparent Cloud Tiering cannot be applied to volumes that are part of traditional copy 
services, such as FlashCopy, Metro Mirror, Global Mirror, and HyperSwap.
/SM590000Volume containing two physical copies in two different storage pools cannot be part of 
Transparent Cloud Tiering.
/SM590000Cloud Tiering snapshots cannot be taken from a volume that is part of migration activity 
across storage pools.
Note: You should always consider the bandwidth characteristics and network capabilities 
when choosing to use Transparent Cloud Tiering.