Smart Scan failed due to shared filesystem

[georged]

Hello,

I am receiving a notification:

ZeXtras ZxBackup Notification, Smart Scan failed. From server <server name>
Operation Id: 0f291c68-28ce-4c3f-8dc0-2de2a26f31d9
Operation Host: <server name>
Scheduled operation

ZeXtras Version: 1.10.1
ZeXtras commit: 3441446ac7c333aeab45c74246f32a43ef022530
ZAL Version: 1.5.1
ZAL commit: 3441446ac7c333aeab45c74246f32a43ef022530
Zimbra version: 8.5.1_GA_3056 20141103151510 20141103-1530 FOSS


-- exceptions --
- Backup path: /opt/zimbra/backup/zextras/ is already used by another server, please don't use shared filesystem for backup
Last progress info:
--
Account scanned: 0/??
Account updated/new: 0/0
Item scanned: 0
Item updated/new/unique: 0/0/0

My /opt/zimbra/backup/zextras/ is not used by any other server so I don't really understand why this is happening. I looked around the forum but did not find a similar posting. Have I configured something wrong?


FWIW, there is no problem saving the Customizations in the same path.

This is an automated notification from ZxBackup about Backup Server Customizations.

Operation Backup Server Customizations Completed.

Operation Id: c9142b5b-07a2-4bd3-ab23-f4915a050d00
Operation Host: <server name>
Operation Start Time: 08/01/2015 04:01:00
Operation Duration: 1 second
Scheduled operation

ZeXtras Version: 1.10.1
ZeXtras commit: 3441446ac7c333aeab45c74246f32a43ef022530
ZAL Version: 1.5.1
ZAL commit: 3441446ac7c333aeab45c74246f32a43ef022530
Zimbra version: 8.5.1_GA_3056 20141103151510 20141103-1530 FOSS

Server Customizations backup path: /opt/zimbra/backup/zextras//server/customizations_08_01_15#04_01_00.tar.gz

Attached also my configuration setup.

Thanks,
George

[Cine]

Hello georded!

The error you report is displayed when the Backup Path you are using contains a lockfile from another server: did you recently migrate to this server using /opt/zimbra/backup/zextras/ as the import path or re-installed Zimbra on this very server?

If not, could you please post the output of the following commands (run as the "zimbra" user):

ls /opt/zimbra/backup/zextras/lock_*

zmprov gs `zmhostname` zimbraId

Have a nice day,
Cine
the ZeXtras Team

[georged]

Hi Cine,
That is exactly what I did! So I do have actually two files under the directory:

# ls -al /opt/zimbra/backup/zextras/lock_*
-rw-r----- 1 zimbra zimbra 0 Dec 10 19:10 /opt/zimbra/backup/zextras/lock_035d60e4-88ce-44c6-9371-424de6799246
-rw-r----- 1 zimbra zimbra 0 Dec 7 23:30 /opt/zimbra/backup/zextras/lock_c2892a30-b98e-4679-85ae-aa0c26fd0774

What shall I do? Is it safe for me to remove these files?

Thank you!
George

[Cine]

Hello George!

It shouldn't be possible to have 2 lockfiles on a single path, did you copy an Export path over an active backup path?
In order to preserve backup consistency please change your backup path to a dedicated empty directory and reinitialize ZeXtras Backup...

Have a nice day,
Cine
the ZeXtras Team

[fs.schmidt]

Hi Cine,

We have migrated from a server with OSE 8.0.7 to OSE 8.6.0 and we have kept the backup path and its content. Assuming that I do not have enough space to create another backup directory, is there any way to remove the lock file and run the SmartScan on the new server?

My best regards.

[Cine]

Hello fs.shmidt!

My official answer would be to scrap the old path entirely once the migration is over. It's not possible to "recycle" another server's backup path, as during an External Restore domains/Classes of Service/mailboxes and items are created with new IDs which are different than those in the old server - so the metadata of the old backup is inconsistent with the new server.

BUT

There's something more

Item BLOBs' contents are not based on any kind of changing ID: this means that you can salvage the vast majority of old BLOBs to speed up the initialization process and avoid disk usage overhead.

In order to do so you need to:
- Delete every file in the backup path used as the migration's import path except for the "items" directory.
- Make sure that the RealTime Scanner is disabled (it should be, I'm just overzealous)

zxsuite backup getProperty ZxBackup_RealTimeScanner

- Set what's left of the old backup as the Backup Path through the ZeXtras CLI

zxsuite backup setProperty ZxBackup_DestPath /path/to/your/backup

- Start a SmartScan in order to initialize the Backup Path

zxsuite backup doSmartScan

- Once the SmartScan is completed, run a Coherency Check with the "fixBackup" option to move broken and unreferenced BLOBs out of the backup

zxsuite backup doCoherencyCheck /path/to/your/backup fixBackup true

- You can now delete the BLOBs moved out by the Coherency Check (check the path in the "Operation Completed" notification) and enjoy ZeXtras Suite!

Make sure to use the CLI commands I mentioned, the ZeXtras Administration Zimlet has additional safety checks that won't allow you to follow some of the steps.


Have a nice day,
Cine
the ZeXtras Team

[fs.schmidt]

Hi Cine,

Thank you very much for the answer, it solves my query sufficiently.