Follow

About this topic

When restoring a thick dataset from one of its snapshots, we need to consider the pool physical capacity. The dataset accepts writes as long as the pool physical capacity is not depleted.

Instructions

Step 1: Creating a thick dataset and taking a snapshot

  1. A thick dataset is created. 
  2. The dataset accepts writes. 
  3. A snapshot is taken. 

Step 2: Accepting writes after the snapshot was created

As the dataset keeps accepting writes, that snapshot consumes capacity. 

Step 3: Restoring the dataset from the snapshot

At the time of restore, for a brief moment, the snapshot is restored to a copy of the dataset, while the original dataset is not deleted yet.

At this point, the dataset and snapshot both consume capacity. This capacity may exceed the pool physical capacity.

In this case, you may either:

  • Increase the pool physical capacity
  • Change the dataset provisioning type to thin

These changes can be reverted after the successful completion of the restore operation.

Applicability to replication change role

When the source and target of the replication change roles, the target dataset is restored from its snapshot. The mechanism that was discussed above also applies to target dataset.

If there is not enough room for restoring the target, the replication change role operation will not take place.
In this case, you may either:

  • Increase the target pool physical capacity
  • Change the dataset provisioning type to thin

 

Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Comments