Data Protection Troubleshooting

Applies to: QSM 4 and XEVO 3 #

Pool and volume unavailable after firmware downgrade on a QMetro node #

Downgrading the firmware on one node in an established QMetro configuration may cause the associated pool and volume to become unavailable. XInsight may also indicate that the affected node has left the Metro.

Before attempting a firmware downgrade in a QMetro environment, contact QSAN Support to confirm version compatibility and the appropriate procedure. If this issue has already occurred, contact QSAN Support for further assistance.

Applies to: QSM 4 #

Can I use rsync between QSM 4 and QSM 3? #

Yes. In the tested configuration, rsync transfers were successful in both directions between devices running QSM 4 and QSM 3.

Why were the files deleted from the recycle bin, but the space wasn’t freed up? #

The user has snapshots on the mentioned folders, which means these snapshots still contain the already deleted data. This allows for the possibility of data rollback upon request. If the user wants to truly free up space, they will need to delete the snapshots as well. It is important to note that once the snapshots are deleted, the option to roll back the data will no longer be available.

Rsync incremental backup behavior with compressed files #

  1. Generate a 100G compressed file and write it to share A.
  2. Back up from A to B via rsync.
  3. Add a 1G file to the original 100G compressed file to generate a new compressed file.
  4. Back up from A to B via rsync again, and observe whether the backup traffic performs an incremental backup. → Because even a slight change to the internal content of a compressed file can cause the compression algorithm to alter the entire file’s contents, rsync detects a new 101G file and will not perform an incremental backup.