IntelliSnap - LSI – Best Practices
Ensure that sufficient disk space is available for snapshot operations and the disk space used by snapshots is monitored frequently.
The space requirement for snapshots created during IntelliSnap backup can vary based on your environment. The space utilization is dependent on the number of snapshots created and the retention period defined for the snapshots.
- While Volume Copy operation is in progress, read-write to the source volume should be frozen until volume copy operation completes.
- Ensure that the LSI SMIS server has access to the LSI array to perform the IntelliSnap operations.
- If there are existing PiT copies on a source volume or if you manually create a PiT copy on the source volume that is part of a IntelliSnap subclient, the existing or the manually created PiT copies are not accessible nor can be indexed by Commvault.
Warning: When selecting the content for the subclient, select source volumes that do not contain existing PiT (Point-in-Time) copies. If there are existing PiT copies, then the Commvault Data Aging feature cannot physically delete the PiT copies created by Commvault jobs.
Warning: Do not manually create PiT copies outside of Commvault on volumes that are part of IntelliSnap subclient content. Commvault deletes those user created PiT copies because of the Data Aging deletion logic.
- Avoid using source volumes that have PiT groups as subclient content of IntelliSnap subclients. Commvault, can create a maximum of 4 consistency groups, provided that the source volume does not have any PiT group already created because the PiT group uses one consistency group. If you must select a source volume with PiT groups, then delete the PiT groups from the source volume before running snap jobs.