OneFS: "error: Multi-schedule collision" alert after running a scheduled snapshot

Summary: When a scheduled snapshot is supposed to be taken, Multi-schedule collision events are logged. One or more scheduled snapshots may not be created.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

Issue

After a scheduled snapshot is supposed to be taken, alerts similar to the following occur:

The snapshot daemon failed to create snapshot '<Schedule-Name>' in schedule '<Schedule Name>': error: Multi-schedule collision

The snapshot daemon failed to create snapshot 'ScheduleName_duration_2024-07-30_11:45' in schedule 'Admin': error: Multi-schedule collision
The snapshot daemon failed to create snapshot 'ScheduleName_duration_2024-07-30_11:45' in schedule 'Finance': error: Multi-schedule collision
The snapshot daemon failed to create snapshot 'ScheduleName_duration_2024-07-30_11:45' in schedule 'Marketing': error: Multi-schedule collision

Symptoms

Errors similar to the following appear in the var/log/messages file on one or more nodes:

isi_snapshot_d[2790]: create_schedule_snapshot: snapshot schedule Finance encountered a collision with snapshot schedule id 3; schedule create failed.
isi_snapshot_d[2790]: create_schedule_snapshot: snapshot schedule Marketing encountered a collision with snapshot schedule id 3; schedule create failed.
isi_snapshot_d[2790]: create_schedule_snapshot: snapshot schedule Finance encountered a collision with snapshot schedule id 3; schedule create failed.
isi_snapshot_d[2790]: create_schedule_snapshot: snapshot schedule Admin encountered a collision with snapshot schedule id 2; schedule create failed.

These messages indicate that SnapshotIQ is trying to create snapshots with names that already exist (name collision).

Cause

Cause

This issue can occur if multiple snapshot schedules have a snapshot naming pattern that is not unique enough to prevent a name collision. By default, the Naming pattern for generated snapshots is ScheduleName_duration_%Y-%m-%d_%H:%M. If multiple snapshots are scheduled to run simultaneously and the snapshot naming pattern is left at default, a snapshot name collision can occur.

Resolution

Solution

Ensure that every snapshot schedule has a unique snapshot naming pattern.

NOTE : The snapshot Schedule name field is not used in determining the snapshot naming pattern.

OneFS 8.x, OneFS 9.x and beyond 

  1. In the OneFS web administration interface, click Data Protection > SnapshotIQ, then click Snapshot Schedules.

  2. For the snapshot schedule to modify, click the corresponding View / Edit button then click Edit.

  3. In the Naming Pattern for Generated Snapshots entry, the default name pattern is ScheduleName_duration_%Y-%m-%d_%H:%M.

  4. Change the default name pattern and provide a unique naming pattern for the generated snapshots. For example, to create a weekly snapshot of data belonging to your organization's marketing department, create a snapshot pattern formatted similar to the following:

    marketing_weekly_%Y-%m-%d_%H:%M
    

    This would result in a snapshot named marketing_weekly_2024-07-30_11:45.

  5. Click Save changes and then click Close.

Affected Products

PowerScale OneFS

Products

Isilon
Article Properties
Article Number: 000097565
Article Type: Solution
Last Modified: 06 Mar 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.