Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Scheduling efficient backup policies

Managing storage  Top

The maximum number of Snapshot copies allowed per volume is 255, so it is necessary to create backup policies that optimize space on the volume, and avoid the 255 Snapshot copy limit.

Optimize Snapshot copy content  Top

You can conserve space by backing up distinct primary qtrees from multiple storage systems to the same secondary volume at the same time.

Example

Assume that multiple primary storage systems contain qtree1 through qtree5. A backup policy specifies a sequential back up schedule for each qtree, and these qtrees are backed up to qtrees of the same name on the same secondary volume. Five backups are taken of each qtree, which results in five Snapshot copies. Assume these Snapshot copies are named snapshot1 through snapshot5 respectively, and each contains a backup of qtree1, qtree2, qtree3, qtree4, and qtree5.

Snapshot copy*

Contains...

snapshot1

qtree1, qtree2, qtree3, qtree4, qtree5

snapshot2

qtree1, qtree2, qtree3, qtree4, qtree5

snapshot3

qtree1, qtree2, qtree3, qtree4, qtree5

snapshot4

qtree1, qtree2, qtree3, qtree4, qtree5

snapshot5

qtree1, qtree2, qtree3, qtree4, qtree5

This policy conserves space because multiple qtrees are backed up at the same time. It is less desirable to set policies that back up single qtrees multiple times because doing so results in more Snapshot copies than necessary.

Maximize the number of qtree backups  Top

You can increase Snapshot storage capacity by using FlexVol volumes. FlexVol volumes do not increase the amount of physical storage space, rather they share space within an aggregate with other FlexVol volumes, and each volume supports 255 Snapshot copies.

Example

Assume that qtree1, qtree2, qtree3, qtree4, qtree5, and qtree6 are backed up to the same volume. Qtree1, qtree2, and qtree3 are backed up twice a day, and qtree4, qtree5, and qtree6 are backed up once a day. After five days, there will be a total of ten Snapshot copies on the destination volume.

Interval

Snapshot copy*

Contains...

Day 1

snapshot1

snapshot2

qtree1, qtree2, qtree3, qtree4, qtree5, qtree6

qtree1, qtree2, qtree3

Day 2

snapshot3

snapshot4

qtree1, qtree2, qtree3, qtree4, qtree5, qtree6

qtree1, qtree2, qtree3

Day 3

snapshot5

snapshot6

qtree1, qtree2, qtree3, qtree4, qtree5, qtree6

qtree1, qtree2, qtree3

Day 4

snapshot7

snapshot8

qtree1, qtree2, qtree3, qtree4, qtree5, qtree6

qtree1, qtree2, qtree3

Day 5

snapshot9

snapshot10

qtree1, qtree2, qtree3, qtree4, qtree5, qtree6

qtree1, qtree2, qtree3

At the 255 maximum Snapshot copy threshold for the volume, the number of backups stored equals 250 that contain qtree1 through qtree3, and 125 that contain qtree4 through qtree6. While effective, this policy could be more efficient if the data was backed up to multiple FlexVol volumes.

FlexVol volumes are managed separately within the physical resources of your storage system. By increasing the number of volumes within a fixed aggregate, you increase Snapshot storage capacity because each volume maintains a 255 Snapshot copy limitation. FlexVol volumes are extremely efficient for grouping primary qtrees with similar backup schedules.

Example

Assume two FlexVol volumes totaling the same amount of disk space. Qtree1, qtree2, and qtree3 are backed up to one FlexVol volume, and qtree4, qtree5, and qtree6 are backed up to the second FlexVol volume. In this case, the number of backups stored on each FlexVol volume equals 250 with one volume containing qtree1 through qtree3, and the other containing qtree4 through qtree6. The amount of space consumed is the same, but Snapshot storage capacity is optimized.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments