#bacula — Public Fediverse posts

SSD death ☠️💀

I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

I always monitor SMART output of SSD drives & mechanical spinners (HDD)

I've not seen any smart output indicating imminante dead

This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

The drive itself is fairly small.

The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

No ZFS on my backup machines

• I want to run ZFS native
• that means running a BSD OS on those machines
• that also means I will need to backup / restore all data on those drives meaning
• I will need 200% of the used HDD / SSD space on those machines
• I need patience for that backup
• I need expensive extra HDD's for that project
• I won't pay USD 300 for a USD 120 HDD

NO ZFS under these global SSD / HDD market prices

Sources:

• Moi
• man ls(1)
• man lsd(1)
• man cp(1)
• man smartctl(8)
• man zfs(8)

#HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

SSD death ☠️💀

I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

I always monitor SMART output of SSD drives & mechanical spinners (HDD)

I've not seen any smart output indicating imminante dead

This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

The drive itself is fairly small.

The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

No ZFS on my backup machines

• I want to run ZFS native
• that means running a BSD OS on those machines
• that also means I will need to backup / restore all data on those drives meaning
• I will need 200% of the used HDD / SSD space on those machines
• I need patience for that backup
• I need expensive extra HDD's for that project
• I won't pay USD 300 for a USD 120 HDD

NO ZFS under these global SSD / HDD market prices

Sources:

• Moi
• man ls(1)
• man lsd(1)
• man cp(1)
• man smartctl(8)
• man zfs(8)

#HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

SSD death ☠️💀

I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

I always monitor SMART output of SSD drives & mechanical spinners (HDD)

I've not seen any smart output indicating imminante dead

This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

The drive itself is fairly small.

The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

No ZFS on my backup machines

• I want to run ZFS native
• that means running a BSD OS on those machines
• that also means I will need to backup / restore all data on those drives meaning
• I will need 200% of the used HDD / SSD space on those machines
• I need patience for that backup
• I need expensive extra HDD's for that project
• I won't pay USD 300 for a USD 120 HDD

NO ZFS under these global SSD / HDD market prices

Sources:

• Moi
• man ls(1)
• man lsd(1)
• man cp(1)
• man smartctl(8)
• man zfs(8)

#HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

SSD death ☠️💀

I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

I always monitor SMART output of SSD drives & mechanical spinners (HDD)

I've not seen any smart output indicating imminante dead

This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

The drive itself is fairly small.

The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

No ZFS on my backup machines

• I want to run ZFS native
• that means running a BSD OS on those machines
• that also means I will need to backup / restore all data on those drives meaning
• I will need 200% of the used HDD / SSD space on those machines
• I need patience for that backup
• I need expensive extra HDD's for that project
• I won't pay USD 300 for a USD 120 HDD

NO ZFS under these global SSD / HDD market prices

Sources:

• Moi
• man ls(1)
• man lsd(1)
• man cp(1)
• man smartctl(8)
• man zfs(8)

#HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

SSD death ☠️💀

I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

I always monitor SMART output of SSD drives & mechanical spinners (HDD)

I've not seen any smart output indicating imminante dead

This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

The drive itself is fairly small.

The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

No ZFS on my backup machines

• I want to run ZFS native
• that means running a BSD OS on those machines
• that also means I will need to backup / restore all data on those drives meaning
• I will need 200% of the used HDD / SSD space on those machines
• I need patience for that backup
• I need expensive extra HDD's for that project
• I won't pay USD 300 for a USD 120 HDD

NO ZFS under these global SSD / HDD market prices

Sources:

• Moi
• man ls(1)
• man lsd(1)
• man cp(1)
• man smartctl(8)
• man zfs(8)

#HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

Ripping Out Three Backup Systems and Replacing Them with One (Part 4: Layering What I Have)

https://rant.mvh.dev/ripping-out-three-backup-systems-part-4-layering/

#selfhosted #selfhosting #backups #bacula

Ripping Out Three Backup Systems and Replacing Them with One (Part 4: Layering What I Have)

https://rant.mvh.dev/ripping-out-three-backup-systems-part-4-layering/

#selfhosted #selfhosting #backups #bacula

Ripping Out Three Backup Systems and Replacing Them with One (Part 4: Layering What I Have)

https://rant.mvh.dev/ripping-out-three-backup-systems-part-4-layering/

#selfhosted #selfhosting #backups #bacula

Ripping Out Three Backup Systems and Replacing Them with One (Part 4: Layering What I Have)

https://rant.mvh.dev/ripping-out-three-backup-systems-part-4-layering/

#selfhosted #selfhosting #backups #bacula

Ripping Out Three Backup Systems and Replacing Them with One (Part 4: Layering What I Have)

https://rant.mvh.dev/ripping-out-three-backup-systems-part-4-layering/

#selfhosted #selfhosting #backups #bacula

Ripping Out Three Backup Systems and Replacing Them with One (Part 2: Building Bacula)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-2-building-bacula/

#selfhosted #selfhosting #backups #docker #bacula #homelab

Ripping Out Three Backup Systems and Replacing Them with One (Part 2: Building Bacula)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-2-building-bacula/

#selfhosted #selfhosting #backups #docker #bacula #homelab

Ripping Out Three Backup Systems and Replacing Them with One (Part 2: Building Bacula)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-2-building-bacula/

#selfhosted #selfhosting #backups #docker #bacula #homelab

Ripping Out Three Backup Systems and Replacing Them with One (Part 2: Building Bacula)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-2-building-bacula/

#selfhosted #selfhosting #backups #docker #bacula #homelab

Ripping Out Three Backup Systems and Replacing Them with One (Part 2: Building Bacula)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-2-building-bacula/

#selfhosted #selfhosting #backups #docker #bacula #homelab

Adding Logical Database Backups to a Homelab That Only Had File-Level Ones

https://rant.mvh.dev/adding-logical-database-backups-to-a-homelab-that-only-had-file-level-ones/

#selfhosted #selfhosting #databases #docker #bacula #homelab #postgresql #mariadb

Adding Logical Database Backups to a Homelab That Only Had File-Level Ones

https://rant.mvh.dev/adding-logical-database-backups-to-a-homelab-that-only-had-file-level-ones/

#selfhosted #selfhosting #databases #docker #bacula #homelab #postgresql #mariadb

Adding Logical Database Backups to a Homelab That Only Had File-Level Ones

https://rant.mvh.dev/adding-logical-database-backups-to-a-homelab-that-only-had-file-level-ones/

#selfhosted #selfhosting #databases #docker #bacula #homelab #postgresql #mariadb

Adding Logical Database Backups to a Homelab That Only Had File-Level Ones

https://rant.mvh.dev/adding-logical-database-backups-to-a-homelab-that-only-had-file-level-ones/

#selfhosted #selfhosting #databases #docker #bacula #homelab #postgresql #mariadb

Adding Logical Database Backups to a Homelab That Only Had File-Level Ones

https://rant.mvh.dev/adding-logical-database-backups-to-a-homelab-that-only-had-file-level-ones/

#selfhosted #selfhosting #databases #docker #bacula #homelab #postgresql #mariadb

Ripping Out Three Backup Systems and Replacing Them with One (Part 1: The Mess)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-1-the-mess/

#selfhosted #bacula #backups #homelab #rsnapshot #rsync

Ripping Out Three Backup Systems and Replacing Them with One (Part 1: The Mess)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-1-the-mess/

#selfhosted #bacula #backups #homelab #rsnapshot #rsync

Ripping Out Three Backup Systems and Replacing Them with One (Part 1: The Mess)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-1-the-mess/

#selfhosted #bacula #backups #homelab #rsnapshot #rsync

Ripping Out Three Backup Systems and Replacing Them with One (Part 1: The Mess)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-1-the-mess/

#selfhosted #bacula #backups #homelab #rsnapshot #rsync

Ripping Out Three Backup Systems and Replacing Them with One (Part 1: The Mess)

https://rant.mvh.dev/ripping-out-three-backup-systems-and-replacing-them-with-one-part-1-the-mess/

#selfhosted #bacula #backups #homelab #rsnapshot #rsync

And the Fortune said;

RAID is not a backup
The cloud ☁️ is also not a backup!

Tar is a backup Bacula and ZFS with proper configuration also

#Cloud #backup #bacula #ZFS #RAID #tar

https://koreajoongangdaily.joins.com/news/2025-10-01/national/socialAffairs/NIRS-fire-destroys-governments-cloud-storage-system-no-backups-available/2412936

And the Fortune said;

RAID is not a backup
The cloud ☁️ is also not a backup!

Tar is a backup Bacula and ZFS with proper hardware configuration also.

Even just `tar -cvfz` would be great with the tar dumped on HDD off site.

WTF Korea now the millions of vital records are gone :(

The damage of this is incalculable

#Cloud #backup #bacula #ZFS #RAID #tar

https://koreajoongangdaily.joins.com/news/2025-10-01/national/socialAffairs/NIRS-fire-destroys-governments-cloud-storage-system-no-backups-available/2412936

And the Fortune said;

RAID is not a backup
The cloud ☁️ is also not a backup!

Tar is a backup Bacula and ZFS with proper hardware configuration also.

Even just `tar -cvfz` would be great with the tar dumped on HDD off site.

WTF Korea now the millions of vital records are gone :(

The damage of this is incalculable

#Cloud #backup #bacula #ZFS #RAID #tar

https://koreajoongangdaily.joins.com/news/2025-10-01/national/socialAffairs/NIRS-fire-destroys-governments-cloud-storage-system-no-backups-available/2412936

And the Fortune said;

RAID is not a backup
The cloud ☁️ is also not a backup!

Tar is a backup Bacula and ZFS with proper hardware configuration also.

Even just `tar -cvfz` would be great with the tar dumped on HDD off site.

WTF Korea now the millions of vital records are gone :(

The damage of this is incalculable

#Cloud #backup #bacula #ZFS #RAID #tar

https://koreajoongangdaily.joins.com/news/2025-10-01/national/socialAffairs/NIRS-fire-destroys-governments-cloud-storage-system-no-backups-available/2412936

And the Fortune said;

RAID is not a backup
The cloud ☁️ is also not a backup!

Tar is a backup Bacula and ZFS with proper hardware configuration also.

Even just `tar -cvfz` would be great with the tar dumped on HDD off site.

WTF Korea now the millions of vital records are gone :(

The damage of this is incalculable

#Cloud #backup #bacula #ZFS #RAID #tar

https://koreajoongangdaily.joins.com/news/2025-10-01/national/socialAffairs/NIRS-fire-destroys-governments-cloud-storage-system-no-backups-available/2412936

If you use #Bacula in Bookworm, be aware that the upgrade to Trixie will initiate a major overhaul of the database, which will need a lot of disk space and time.

https://www.debian.org/releases/trixie/release-notes/issues.en.html#bacula-director-database-schema-update-needs-large-amounts-of-disk-space-and-time

If you use #Bacula in Bookworm, be aware that the upgrade to Trixie will initiate a major overhaul of the database, which will need a lot of disk space and time.

https://www.debian.org/releases/trixie/release-notes/issues.en.html#bacula-director-database-schema-update-needs-large-amounts-of-disk-space-and-time

If you use #Bacula in Bookworm, be aware that the upgrade to Trixie will initiate a major overhaul of the database, which will need a lot of disk space and time.

https://www.debian.org/releases/trixie/release-notes/issues.en.html#bacula-director-database-schema-update-needs-large-amounts-of-disk-space-and-time

If you use #Bacula in Bookworm, be aware that the upgrade to Trixie will initiate a major overhaul of the database, which will need a lot of disk space and time.

https://www.debian.org/releases/trixie/release-notes/issues.en.html#bacula-director-database-schema-update-needs-large-amounts-of-disk-space-and-time

If you use #Bacula in Bookworm, be aware that the upgrade to Trixie will initiate a major overhaul of the database, which will need a lot of disk space and time.

https://www.debian.org/releases/trixie/release-notes/issues.en.html#bacula-director-database-schema-update-needs-large-amounts-of-disk-space-and-time

Aujourd'hui 31 mars, c'est la journée de sensibilisation à l'importance des #sauvegardes, le #worldbackupday https://www.worldbackupday.com/fr Le monde de l'opensource n'est pas en reste avec des solutions de #sauvegardes performantes comme #Borg ou #Bacula
Les sauvegardes doivent suivre la règle des 3-2-1 : 3 sauvegardes, 2 support différent, 1 externalisé. Et surtout une sauvegarde est une sauvegarde que l'on sait restaurer ! Pensez à bien tester vos sauvegardes et leurs intégrités/contenus.

Aujourd'hui 31 mars, c'est la journée de sensibilisation à l'importance des #sauvegardes, le #worldbackupday https://www.worldbackupday.com/fr Le monde de l'opensource n'est pas en reste avec des solutions de #sauvegardes performantes comme #Borg ou #Bacula
Les sauvegardes doivent suivre la règle des 3-2-1 : 3 sauvegardes, 2 support différent, 1 externalisé. Et surtout une sauvegarde est une sauvegarde que l'on sait restaurer ! Pensez à bien tester vos sauvegardes et leurs intégrités/contenus.

Aujourd'hui 31 mars, c'est la journée de sensibilisation à l'importance des #sauvegardes, le #worldbackupday https://www.worldbackupday.com/fr Le monde de l'opensource n'est pas en reste avec des solutions de #sauvegardes performantes comme #Borg ou #Bacula
Les sauvegardes doivent suivre la règle des 3-2-1 : 3 sauvegardes, 2 support différent, 1 externalisé. Et surtout une sauvegarde est une sauvegarde que l'on sait restaurer ! Pensez à bien tester vos sauvegardes et leurs intégrités/contenus.

Aujourd'hui 31 mars, c'est la journée de sensibilisation à l'importance des #sauvegardes, le #worldbackupday https://www.worldbackupday.com/fr Le monde de l'opensource n'est pas en reste avec des solutions de #sauvegardes performantes comme #Borg ou #Bacula
Les sauvegardes doivent suivre la règle des 3-2-1 : 3 sauvegardes, 2 support différent, 1 externalisé. Et surtout une sauvegarde est une sauvegarde que l'on sait restaurer ! Pensez à bien tester vos sauvegardes et leurs intégrités/contenus.

Aujourd'hui 31 mars, c'est la journée de sensibilisation à l'importance des #sauvegardes, le #worldbackupday https://www.worldbackupday.com/fr Le monde de l'opensource n'est pas en reste avec des solutions de #sauvegardes performantes comme #Borg ou #Bacula
Les sauvegardes doivent suivre la règle des 3-2-1 : 3 sauvegardes, 2 support différent, 1 externalisé. Et surtout une sauvegarde est une sauvegarde que l'on sait restaurer ! Pensez à bien tester vos sauvegardes et leurs intégrités/contenus.

Yesterday I accidentally destroyed a file I was using in a very active directory.

So I hopped on to the Web frontend to my local backup server, and asked it to restore file X on machine Y from the most recent copy. It worked. (Yay!)

My backup system is #Bareos, a fork of #Bacula. However, I chose it for very specific reasons, and I *don't* recommend it for anyone unless you share the same concerns.

Yesterday I accidentally destroyed a file I was using in a very active directory.

So I hopped on to the Web frontend to my local backup server, and asked it to restore file X on machine Y from the most recent copy. It worked. (Yay!)

My backup system is #Bareos, a fork of #Bacula. However, I chose it for very specific reasons, and I *don't* recommend it for anyone unless you share the same concerns.

Yesterday I accidentally destroyed a file I was using in a very active directory.

So I hopped on to the Web frontend to my local backup server, and asked it to restore file X on machine Y from the most recent copy. It worked. (Yay!)

My backup system is #Bareos, a fork of #Bacula. However, I chose it for very specific reasons, and I *don't* recommend it for anyone unless you share the same concerns.

Yesterday I accidentally destroyed a file I was using in a very active directory.

So I hopped on to the Web frontend to my local backup server, and asked it to restore file X on machine Y from the most recent copy. It worked. (Yay!)

My backup system is #Bareos, a fork of #Bacula. However, I chose it for very specific reasons, and I *don't* recommend it for anyone unless you share the same concerns.

Резервное копирование в Linux: инструменты и стратегия 3-2-1

В статье делюсь методами и инструментами полного резервного копирования операционной системы Linux и рассказываю о своих практиках. Чек-лист резервного копирования здорового человека Полнота . Бэкапы должны включать все критически важные компоненты проекта: базы данных, файлы сайта, конфигурационные файлы и мультимедийный контент. Регулярность — чтобы минимизировать потери данных. Частота создания бэкапов зависит от динамики изменений на сайте. Как правило — варьируется от ежедневного до еженедельного. Надежное хранение . Резервные копии не хранят на основных серверах. Желательно использовать облачные хранилища или отдельные физические носители. Шифрование . Данные должны быть зашифрованы — это защита конфиденциальных данных от несанкционированного доступа. Критически важно! Обязательно заучиваем пароль шифрования. Проверьте — все хорошо только, если вас разбудили ночью и вы сразу и правильно его вспомнили. Автоматизация . Автоматизация процессов снижает риск человеческой ошибки. Тестирование восстановления — чтобы убедиться в работоспособности бэкапов. Версионность . Хранение нескольких версий бэкапов полезно, если пригодится восстановление данных на определенный момент времени. Прежде чем углубляться в детали инструментов и методов резервного копирования, расскажу о базовой, но чрезвычайно эффективной стратегии — основе любого плана защиты данных. Это концепция 3-2-1.

https://habr.com/ru/companies/ispmanager/articles/844154/

#серверное_администрирование #системное_администрирование #itинфраструктура #321 #резервное_копирование #bacula #cyber_backup #amanda #veeam_backup_and_replication #acronis_cyber_protect

Резервное копирование в Linux: инструменты и стратегия 3-2-1

В статье делюсь методами и инструментами полного резервного копирования операционной системы Linux и рассказываю о своих практиках. Чек-лист резервного копирования здорового человека Полнота . Бэкапы должны включать все критически важные компоненты проекта: базы данных, файлы сайта, конфигурационные файлы и мультимедийный контент. Регулярность — чтобы минимизировать потери данных. Частота создания бэкапов зависит от динамики изменений на сайте. Как правило — варьируется от ежедневного до еженедельного. Надежное хранение . Резервные копии не хранят на основных серверах. Желательно использовать облачные хранилища или отдельные физические носители. Шифрование . Данные должны быть зашифрованы — это защита конфиденциальных данных от несанкционированного доступа. Критически важно! Обязательно заучиваем пароль шифрования. Проверьте — все хорошо только, если вас разбудили ночью и вы сразу и правильно его вспомнили. Автоматизация . Автоматизация процессов снижает риск человеческой ошибки. Тестирование восстановления — чтобы убедиться в работоспособности бэкапов. Версионность . Хранение нескольких версий бэкапов полезно, если пригодится восстановление данных на определенный момент времени. Прежде чем углубляться в детали инструментов и методов резервного копирования, расскажу о базовой, но чрезвычайно эффективной стратегии — основе любого плана защиты данных. Это концепция 3-2-1.

https://habr.com/ru/companies/ispmanager/articles/844154/

#серверное_администрирование #системное_администрирование #itинфраструктура #321 #резервное_копирование #bacula #cyber_backup #amanda #veeam_backup_and_replication #acronis_cyber_protect

Резервное копирование в Linux: инструменты и стратегия 3-2-1

В статье делюсь методами и инструментами полного резервного копирования операционной системы Linux и рассказываю о своих практиках. Чек-лист резервного копирования здорового человека Полнота . Бэкапы должны включать все критически важные компоненты проекта: базы данных, файлы сайта, конфигурационные файлы и мультимедийный контент. Регулярность — чтобы минимизировать потери данных. Частота создания бэкапов зависит от динамики изменений на сайте. Как правило — варьируется от ежедневного до еженедельного. Надежное хранение . Резервные копии не хранят на основных серверах. Желательно использовать облачные хранилища или отдельные физические носители. Шифрование . Данные должны быть зашифрованы — это защита конфиденциальных данных от несанкционированного доступа. Критически важно! Обязательно заучиваем пароль шифрования. Проверьте — все хорошо только, если вас разбудили ночью и вы сразу и правильно его вспомнили. Автоматизация . Автоматизация процессов снижает риск человеческой ошибки. Тестирование восстановления — чтобы убедиться в работоспособности бэкапов. Версионность . Хранение нескольких версий бэкапов полезно, если пригодится восстановление данных на определенный момент времени. Прежде чем углубляться в детали инструментов и методов резервного копирования, расскажу о базовой, но чрезвычайно эффективной стратегии — основе любого плана защиты данных. Это концепция 3-2-1.

https://habr.com/ru/companies/ispmanager/articles/844154/

#серверное_администрирование #системное_администрирование #itинфраструктура #321 #резервное_копирование #bacula #cyber_backup #amanda #veeam_backup_and_replication #acronis_cyber_protect

State of my bacula storage:

- status storage
- Device File: "FileStorage" is not open (Available Space=1.387 TB)
- mount
- File device "FileStorage" is always mounted
- umount
- Device "FileStorage" is already unmounted

Well...

#bacula

State of my bacula storage:

- status storage
- Device File: "FileStorage" is not open (Available Space=1.387 TB)
- mount
- File device "FileStorage" is always mounted
- umount
- Device "FileStorage" is already unmounted

Well...

#bacula

State of my bacula storage:

- status storage
- Device File: "FileStorage" is not open (Available Space=1.387 TB)
- mount
- File device "FileStorage" is always mounted
- umount
- Device "FileStorage" is already unmounted

Well...

#bacula