Sun ZFS Storage 7320
 
Sun Storage 7210 Unified Storage System
 
Oracle ZFS Storage ZS3-BA
 
Oracle ZFS Storage Appliance Racked System ZS4-4
 
Oracle ZFS Storage ZS3-2
 
Oracle ZFS Storage ZS3-4
 
Sun Storage 7410 Unified Storage System
 
Sun ZFS Storage 7420
 
Sun Storage 7310 Unified Storage System
 
Oracle ZFS Storage ZS4-4
 
Sun ZFS Storage 7120
 
Sun Storage 7110 Unified Storage System
 

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

In this Document

Goal

Solution

References

Created from <SR 3-10652102903>

Applies to:

Goal

It have been seen that the scheduled snapshots at the project level of a Project are not being populated when the said project has been replicated to a target - and the replication is then reversed.

This is only seen for auto snaps - all manual ones are seen at the reversed project level back on the source system.

Any scheduled snapshots will still run and they will then populate at the Project level.

At the Share level, these auto snaps are seen - so data is safe and they can be rolled back to, as required.

Solution

If required, this issue can be overcome using the following procedure:

    1.  Replicate the project from source A to target B

    2.  To simulate a DR situation, sever the replication from the target B and while doing so, create a new project name

    3.  Delete the project on source A

    4.  On target B, replicate 'newproject' to source A

    5.  sever replication on the source A and rename the project

This workaround has been tested in the lab - autosnaps are visible both at the project level and at the share level and can roll back as required.

Obviously if the customer is OK with rebuilding the schedules manually then you do not need to do the above solution.

References

This solution has no attachment