Sun ZFS Storage 7420
 
Sun Storage 7310 Unified Storage System
 
Sun Storage 7720 Unified Storage System
 
Oracle ZFS Storage ZS3-BA
 
Oracle ZFS Storage ZS4-4
 
Oracle ZFS Storage ZS3-4
 
Sun ZFS Storage 7120
 
Sun ZFS Storage 7320
 
Sun Storage 7210 Unified Storage System
 
Sun Storage 7410 Unified Storage System
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
 

After having deleted a project or share inadvertently on the appliance, customers need to take very quick action in order to lose as little data as possible.

In this Document

Purpose

Scope

Details

Applies to:

Purpose

The BUI allows the administrator to destroy a project or a share.  Sometimes this is done inadvertently. 

Scope

 This document is intended to provide the only and unique method which allows immediate action to be taken - such that not too much data is being lost, as destruction is going on.

Details

If a share or a project has been destroyed inadvertently, customer needs to immediately shut down the system - both heads, if a cluster system.

And raise a call to Oracle support to ask for recovery.

Destroying data is the customer's responsibility and no action will be taken unless a special agreement has been reached for support to handle as much data recovery as possible.

None of the cluster heads should be booted unless it is known that the pool where the destroyed share resides, will not be imported at boot.

As an internal recommendation, TSC should remove the ZFS cachefile in the stash directory, and reboot. That would allow to boot without importing the pool.

        https://stbeehive.oracle.com/teamcollab/wiki/AmberRoadSupport:Data+recovery+-+how+to+boot+without+importing+a+data+pool

NOTE: If the link above is inaccessible (because you do not have the appropriate privileges), please contact the TSC Engineer involved with the case and he will provide details of the procedure.

This solution has no attachment