diff --git a/src-qt4/life-preserver/LPGUtils.h b/src-qt4/life-preserver/LPGUtils.h deleted file mode 100644 index b8c9d2d28..000000000 --- a/src-qt4/life-preserver/LPGUtils.h +++ /dev/null @@ -1,18 +0,0 @@ -#ifndef _LP_GUTILS_H -#define _LP_GUTILS_H - -#include -#include -#include -#include - -#include "LPBackend.h" -#include "LPContainers.h" - -class LPGUtils{ -public: - static LPDataset loadPoolData(QString zpool); //Load backend data into container - -}; - -#endif \ No newline at end of file diff --git a/src-qt4/life-preserver/LPMain.cpp b/src-qt4/life-preserver/LPMain.cpp deleted file mode 100644 index 447c8e850..000000000 --- a/src-qt4/life-preserver/LPMain.cpp +++ /dev/null @@ -1,90 +0,0 @@ -#include "LPMain.h" - -LPMain::LPMain(QWidget *parent) : QMainWindow(parent), ui(new Ui::LPMain){ - ui->setupUi(); //load the Qt-designer UI file - //Create the basic/advanced view options - viewBasic = new QRadioButton(tr("Basic"), ui->menuView); - viewAdvanced = new QRadioButton(tr("Advanced"), ui->menuView); - ui->menuView->addWidget(viewBasic); - ui->menuView->addWidget(viewAdvanced); - connect(viewBasic, SIGNAL(toggled()), this, SLOT(viewChanged()) ); - //Now set the default view type - viewBasic->setChecked(true); //will automatically call the "viewChanged" function - - //Connect the UI to all the functions - -} - -LPMain::~LPMain(){ - -} - -// ============== -// PUBLIC SLOTS -// ============== -void LPMain::updateUI(){ - //Get the currently selected pool (if there is one) - QString cPool; - if(ui->combo_pools->currentIndex != -1){ cPool = ui->combo_pools_currentText(); } - //Get the list of managed pools - QStringList pools = LPBackend::listDatasets(); - //Now put that list into the UI - ui->combo_pools->clear(); - for(int i=0; i 0){ - int index = pools.indexOf(cPool); - if(index < 0){ ui->combo_pools->setCurrentIndex(0); } - else{ ui->combo_pools->setCurrentIndex(index); } - poolSelected=true; - }else{ - //No managed pools - ui->combo_pools->addItem("No Managed Pools!"); - ui->combo_pools->setCurrentIndex(0); - poolSelected=false; - } - //Now update the interface appropriately - updateInterface(); -} - -// ============== -// PRIVATE -// ============== - - -// ============== -// PRIVATE SLOTS -// ============== -void LPMain::viewChanged(){ - if(viewBasic->isChecked()){ - ui->menuDisks->setVisible(false); - ui->menuSnapshots->setVisible(false); - }else{ - ui->menuDisks->setVisible(true); - ui->menuSnapshots->setVisible(true); - } -} - -void updateInterface(){ - viewChanged(); - ui->tabWidget->setEnabled(poolSelected); - ui->menuView->setVisible(poolSelected); - ui->tool_configure->setVisible(poolSelected); - ui->tool_configBackups->setVisible(poolSelected); - ui->actionUnmanage_Pool->setEnabled(poolSelected); - ui->action_SaveKeyToUSB->setEnabled(poolSelected); - if(poolSelected){ - POOLDATA = LPGUtils::loadPoolData(ui->combo_pools->currentText()); - //Now list the status information - - //Now list the data restore options - QStringList - }else{ - //No Pool selected - ui->menuDisks->setVisible(false); //make sure this is always invisible if nothing selected - ui->menuSnapshots->setVisible(false); //make sure this is always invisible if nothing selected - } - -} diff --git a/src-qt4/life-preserver/LPMain.h b/src-qt4/life-preserver/LPMain.h deleted file mode 100644 index 77d327c94..000000000 --- a/src-qt4/life-preserver/LPMain.h +++ /dev/null @@ -1,44 +0,0 @@ -#ifndef _LP_MAIN_H -#define _LP_MAIN_H - -#include -#include -#include -#include -#include -#include -#include - -#include "LPBackend.h" -#include "LPContainers.h" - -namespace Ui{ - class LPMain; -}; - -class LPMain : public QMainWindow{ - Q_OBJECT -public: - LPMain(QWidget *parent = 0); - ~LPMain(); - -public slots: - void setupUI(); - -private: - Ui::LPMain *ui; - QRadioButton *viewBasic, *viewAdvanced; - bool poolSelected; - LPDataset POOLDATA; - - void updateInterface(); //update interface based on selected pool - LPDataset loadPoolData(QString pool); - -private slots: - void viewChanged(); - -protected: - -}; - -#endif \ No newline at end of file diff --git a/src-qt4/life-preserver/i18n/LifePreserver_af.ts b/src-qt4/life-preserver/i18n/LifePreserver_af.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_af.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ar.ts b/src-qt4/life-preserver/i18n/LifePreserver_ar.ts deleted file mode 100644 index f1eb8cd1c..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ar.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - إسم المضيف - - - User Name - إسم المستخدم - - - SSH Port - منفذ SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - إغلاق - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - إسم المضيف - - - User Name - إسم المستخدم - - - SSH Port - منفذ SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - حزام إنقاذ الحياة - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - إزالة - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_az.ts b/src-qt4/life-preserver/i18n/LifePreserver_az.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_az.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_bg.ts b/src-qt4/life-preserver/i18n/LifePreserver_bg.ts deleted file mode 100644 index 477ac742f..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_bg.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Име на хоста - - - User Name - Потребителско име - - - SSH Port - SSH Порт - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Затвори - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Име на хоста - - - User Name - Потребителско име - - - SSH Port - SSH Порт - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Премахни - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_bn.ts b/src-qt4/life-preserver/i18n/LifePreserver_bn.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_bn.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_bs.ts b/src-qt4/life-preserver/i18n/LifePreserver_bs.ts deleted file mode 100644 index 317141b4e..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_bs.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Zatvori - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Ukloni - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ca.ts b/src-qt4/life-preserver/i18n/LifePreserver_ca.ts deleted file mode 100644 index 275f721e5..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ca.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nom d'equip - - - User Name - Nom d'usuari - - - SSH Port - Port SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Tancar - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nom d'equip - - - User Name - Nom d'usuari - - - SSH Port - Port SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Treure - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_cs.ts b/src-qt4/life-preserver/i18n/LifePreserver_cs.ts deleted file mode 100644 index a955371e2..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_cs.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Jméno hostitele - - - User Name - Jméno uživatele - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Zavřít - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Jméno hostitele - - - User Name - Jméno uživatele - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Záchranná vesta - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Odstranit - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_cy.ts b/src-qt4/life-preserver/i18n/LifePreserver_cy.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_cy.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_da.ts b/src-qt4/life-preserver/i18n/LifePreserver_da.ts deleted file mode 100644 index a327903eb..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_da.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Værtsnavn - - - User Name - Brugernavn - - - SSH Port - SSH port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Luk - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Værtsnavn - - - User Name - Brugernavn - - - SSH Port - SSH port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Fjern - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_de.ts b/src-qt4/life-preserver/i18n/LifePreserver_de.ts deleted file mode 100644 index c5836267d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_de.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Schliessen - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Entfernen - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_el.ts b/src-qt4/life-preserver/i18n/LifePreserver_el.ts deleted file mode 100644 index db1363e65..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_el.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Όνομα κόμβου - - - User Name - Όνομα χρήστη - - - SSH Port - Θύρα SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Κλείσιμο - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Όνομα κόμβου - - - User Name - Όνομα χρήστη - - - SSH Port - Θύρα SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Συντηρητής - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Αφαίρεση - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_en_GB.ts b/src-qt4/life-preserver/i18n/LifePreserver_en_GB.ts deleted file mode 100644 index e8d1732bd..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_en_GB.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Close - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Remove - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_en_ZA.ts b/src-qt4/life-preserver/i18n/LifePreserver_en_ZA.ts deleted file mode 100644 index e8d1732bd..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_en_ZA.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Close - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Remove - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_es.ts b/src-qt4/life-preserver/i18n/LifePreserver_es.ts deleted file mode 100644 index 489e76bb0..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_es.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nombre de Host - - - User Name - Nombre de Usuario - - - SSH Port - Puerto SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Cerrar - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nombre de Host - - - User Name - Nombre de Usuario - - - SSH Port - Puerto SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life-Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Eliminar - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_et.ts b/src-qt4/life-preserver/i18n/LifePreserver_et.ts deleted file mode 100644 index 642cd791b..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_et.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Hostinimi - - - User Name - Kasutajanimi - - - SSH Port - SSH port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Sulge - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Hostinimi - - - User Name - Kasutajanimi - - - SSH Port - SSH port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Eemalda - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_eu.ts b/src-qt4/life-preserver/i18n/LifePreserver_eu.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_eu.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_fa.ts b/src-qt4/life-preserver/i18n/LifePreserver_fa.ts deleted file mode 100644 index 2de36866a..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_fa.ts +++ /dev/null @@ -1,714 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - -نام دستگاه - - - User Name - -نام کاربر - - - SSH Port - -پورت SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - -نام دستگاه - - - User Name - -نام کاربر - - - SSH Port - -پورت SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - -حذف - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_fi.ts b/src-qt4/life-preserver/i18n/LifePreserver_fi.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_fi.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_fr.ts b/src-qt4/life-preserver/i18n/LifePreserver_fr.ts deleted file mode 100644 index b9554c9c0..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_fr.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nom de l’hôte - - - User Name - Nom d'utilisateur - - - SSH Port - Port SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Fermer - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nom de l’hôte - - - User Name - Nom d'utilisateur - - - SSH Port - Port SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Bouée de sauvetage - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Supprimer - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_fr_CA.ts b/src-qt4/life-preserver/i18n/LifePreserver_fr_CA.ts deleted file mode 100644 index debebc204..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_fr_CA.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nom de l'hôte - - - User Name - Nom d'utilisateur - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Fermer - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nom de l'hôte - - - User Name - Nom d'utilisateur - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Supprimer - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_fur.ts b/src-qt4/life-preserver/i18n/LifePreserver_fur.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_fur.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_gl.ts b/src-qt4/life-preserver/i18n/LifePreserver_gl.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_gl.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_he.ts b/src-qt4/life-preserver/i18n/LifePreserver_he.ts deleted file mode 100644 index 9a56fa5ae..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_he.ts +++ /dev/null @@ -1,713 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - גלגל הצלה - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - הסרה - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_hi.ts b/src-qt4/life-preserver/i18n/LifePreserver_hi.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_hi.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_hr.ts b/src-qt4/life-preserver/i18n/LifePreserver_hr.ts deleted file mode 100644 index c322a35dd..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_hr.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Naziv računala - - - User Name - Korisničko ime - - - SSH Port - SSH port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Zatvori - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Naziv računala - - - User Name - Korisničko ime - - - SSH Port - SSH port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Ukloni - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_hu.ts b/src-qt4/life-preserver/i18n/LifePreserver_hu.ts deleted file mode 100644 index 80444c1a0..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_hu.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Gazdagép neve - - - User Name - Felhasználónév - - - SSH Port - SSH-port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Bezárás - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Gazdagép neve - - - User Name - Felhasználónév - - - SSH Port - SSH-port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Törlés - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_id.ts b/src-qt4/life-preserver/i18n/LifePreserver_id.ts deleted file mode 100644 index 1106637ec..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_id.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nama Host - - - User Name - Nama User - - - SSH Port - Port SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Tutup - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nama Host - - - User Name - Nama User - - - SSH Port - Port SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Pelampung - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Hapus - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_is.ts b/src-qt4/life-preserver/i18n/LifePreserver_is.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_is.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_it.ts b/src-qt4/life-preserver/i18n/LifePreserver_it.ts deleted file mode 100644 index 5da4eeba7..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_it.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nome host - - - User Name - Nome utente - - - SSH Port - Porta SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Chiudi - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nome host - - - User Name - Nome utente - - - SSH Port - Porta SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Rimuovere - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ja.ts b/src-qt4/life-preserver/i18n/LifePreserver_ja.ts deleted file mode 100644 index b6ae66a25..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ja.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - ホスト名 - - - User Name - ユーザー名 - - - SSH Port - SSH のポート - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - 閉じる(&C) - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - ホスト名 - - - User Name - ユーザー名 - - - SSH Port - SSH のポート - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - 削除 - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ka.ts b/src-qt4/life-preserver/i18n/LifePreserver_ka.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ka.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ko.ts b/src-qt4/life-preserver/i18n/LifePreserver_ko.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ko.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_lt.ts b/src-qt4/life-preserver/i18n/LifePreserver_lt.ts deleted file mode 100644 index dae38023b..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_lt.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Pagrindinio kompiuterio pavadinimas - - - User Name - Vartotojo vardas - - - SSH Port - SSH jungtis - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Uždaryti - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Pagrindinio kompiuterio pavadinimas - - - User Name - Vartotojo vardas - - - SSH Port - SSH jungtis - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Gyvybės išlaikytojas - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Pašalinti - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_lv.ts b/src-qt4/life-preserver/i18n/LifePreserver_lv.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_lv.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_mk.ts b/src-qt4/life-preserver/i18n/LifePreserver_mk.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_mk.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_mn.ts b/src-qt4/life-preserver/i18n/LifePreserver_mn.ts deleted file mode 100644 index 1a955747e..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_mn.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Хостын Нэр - - - User Name - Хэрэглэгчийн Нэр - - - SSH Port - SSH Порт дугаар - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Хаах - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Хостын Нэр - - - User Name - Хэрэглэгчийн Нэр - - - SSH Port - SSH Порт дугаар - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Устгах - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ms.ts b/src-qt4/life-preserver/i18n/LifePreserver_ms.ts deleted file mode 100644 index cc6428849..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ms.ts +++ /dev/null @@ -1,714 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Tutup - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_mt.ts b/src-qt4/life-preserver/i18n/LifePreserver_mt.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_mt.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_nb.ts b/src-qt4/life-preserver/i18n/LifePreserver_nb.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_nb.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ne.ts b/src-qt4/life-preserver/i18n/LifePreserver_ne.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ne.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_nl.ts b/src-qt4/life-preserver/i18n/LifePreserver_nl.ts deleted file mode 100644 index 8fae900b8..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_nl.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Systeemnaam - - - User Name - Gebruikersnaam - - - SSH Port - SSH-poort - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Sluiten - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Systeemnaam - - - User Name - Gebruikersnaam - - - SSH Port - SSH-poort - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Reddingsboei - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Verwijderen - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_pa.ts b/src-qt4/life-preserver/i18n/LifePreserver_pa.ts deleted file mode 100644 index 58bf434f4..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_pa.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - ਹੋਸਟ ਨਾਂ - - - User Name - ਯੂਜ਼ਰ ਨਾਂ - - - SSH Port - SSH ਪੋਰਟ - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - ਬੰਦ ਕਰੋ - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - ਹੋਸਟ ਨਾਂ - - - User Name - ਯੂਜ਼ਰ ਨਾਂ - - - SSH Port - SSH ਪੋਰਟ - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - ਜਾਨ ਬਚਾਉ - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - ਹਟਾਓ - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_pl.ts b/src-qt4/life-preserver/i18n/LifePreserver_pl.ts deleted file mode 100644 index 64bbcf372..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_pl.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nazwa Komputera - - - User Name - Nazwa użytkownika - - - SSH Port - Port SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Zamknij - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nazwa Komputera - - - User Name - Nazwa użytkownika - - - SSH Port - Port SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Usuń - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_pt.ts b/src-qt4/life-preserver/i18n/LifePreserver_pt.ts deleted file mode 100644 index dc3636ff2..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_pt.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nome do anfitrião (host) - - - User Name - Nome do utilizador - - - SSH Port - Porta SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Fechar - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nome do anfitrião (host) - - - User Name - Nome do utilizador - - - SSH Port - Porta SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Conservador de vida - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Remover - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_pt_BR.ts b/src-qt4/life-preserver/i18n/LifePreserver_pt_BR.ts deleted file mode 100644 index a0eba5f5e..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_pt_BR.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Nome do host - - - User Name - Nome do Usuário - - - SSH Port - Porta SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Fechar - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Nome do host - - - User Name - Nome do Usuário - - - SSH Port - Porta SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Remover - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ro.ts b/src-qt4/life-preserver/i18n/LifePreserver_ro.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ro.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ru.ts b/src-qt4/life-preserver/i18n/LifePreserver_ru.ts deleted file mode 100644 index f6d951c19..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ru.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Имя хоста - - - User Name - Имя пользователя - - - SSH Port - SSH порт - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Закрыть - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Имя хоста - - - User Name - Имя пользователя - - - SSH Port - SSH порт - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Удалить - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_sa.ts b/src-qt4/life-preserver/i18n/LifePreserver_sa.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_sa.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_sk.ts b/src-qt4/life-preserver/i18n/LifePreserver_sk.ts deleted file mode 100644 index fba403984..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_sk.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Meno hostiteľa - - - User Name - Meno užívateľa - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Zatvoriť - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Meno hostiteľa - - - User Name - Meno užívateľa - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Záchranný server - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Odstrániť - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_sl.ts b/src-qt4/life-preserver/i18n/LifePreserver_sl.ts deleted file mode 100644 index 5c5e06349..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_sl.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Ime gostitelja - - - User Name - Uporabniško ime - - - SSH Port - Vrata SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Zapri - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Ime gostitelja - - - User Name - Uporabniško ime - - - SSH Port - Vrata SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Odstrani - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_sr.ts b/src-qt4/life-preserver/i18n/LifePreserver_sr.ts deleted file mode 100644 index 317141b4e..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_sr.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Zatvori - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Host Name - - - User Name - User Name - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Ukloni - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_sv.ts b/src-qt4/life-preserver/i18n/LifePreserver_sv.ts deleted file mode 100644 index c944e5847..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_sv.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Värdnamn - - - User Name - Användarnamn - - - SSH Port - SSH Port - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Stäng - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Värdnamn - - - User Name - Användarnamn - - - SSH Port - SSH Port - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Ta bort - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_sw.ts b/src-qt4/life-preserver/i18n/LifePreserver_sw.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_sw.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_ta.ts b/src-qt4/life-preserver/i18n/LifePreserver_ta.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_ta.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_tg.ts b/src-qt4/life-preserver/i18n/LifePreserver_tg.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_tg.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_th.ts b/src-qt4/life-preserver/i18n/LifePreserver_th.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_th.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_tr.ts b/src-qt4/life-preserver/i18n/LifePreserver_tr.ts deleted file mode 100644 index 6c9417535..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_tr.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Makine Adı - - - User Name - Kullanıcı Adı - - - SSH Port - SSH Portu - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Kapat - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Makine Adı - - - User Name - Kullanıcı Adı - - - SSH Port - SSH Portu - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Kaldır - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_uk.ts b/src-qt4/life-preserver/i18n/LifePreserver_uk.ts deleted file mode 100644 index 26ba39c17..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_uk.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - Ім'я хоста - - - User Name - Ім'я користувача - - - SSH Port - Порт SSH - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Закрити - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - Ім'я хоста - - - User Name - Ім'я користувача - - - SSH Port - Порт SSH - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Рятувальний круг - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Вилучити - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_uz.ts b/src-qt4/life-preserver/i18n/LifePreserver_uz.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_uz.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_vi.ts b/src-qt4/life-preserver/i18n/LifePreserver_vi.ts deleted file mode 100644 index 76220964a..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_vi.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - lưu trữ tên - - - User Name - Tên người dùng - - - SSH Port - SSH Cảng - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - Đóng - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - lưu trữ tên - - - User Name - Tên người dùng - - - SSH Port - SSH Cảng - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - Hủy bỏ - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_zh_CN.ts b/src-qt4/life-preserver/i18n/LifePreserver_zh_CN.ts deleted file mode 100644 index a56826764..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_zh_CN.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - 主机名称 - - - User Name - 用户名 - - - SSH Port - SSH端口 - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - 关闭 - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - 主机名称 - - - User Name - 用户名 - - - SSH Port - SSH端口 - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - 删除 - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_zh_HK.ts b/src-qt4/life-preserver/i18n/LifePreserver_zh_HK.ts deleted file mode 100644 index f51a98073..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_zh_HK.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - 電腦名稱 - - - User Name - 用戶名稱 - - - SSH Port - SSH 連接埠 - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - 關閉 - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - 電腦名稱 - - - User Name - 用戶名稱 - - - SSH Port - SSH 連接埠 - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - 移除 - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_zh_TW.ts b/src-qt4/life-preserver/i18n/LifePreserver_zh_TW.ts deleted file mode 100644 index 8a9bcde6a..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_zh_TW.ts +++ /dev/null @@ -1,706 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - 主機名稱 - - - User Name - 使用者名稱 - - - SSH Port - SSH通道(Port) - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - 關閉 - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - 主機名稱 - - - User Name - 使用者名稱 - - - SSH Port - SSH通道(Port) - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - Life Preserver - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - 移除 - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/i18n/LifePreserver_zu.ts b/src-qt4/life-preserver/i18n/LifePreserver_zu.ts deleted file mode 100644 index 62fce548d..000000000 --- a/src-qt4/life-preserver/i18n/LifePreserver_zu.ts +++ /dev/null @@ -1,715 +0,0 @@ - - - - - LPConfig - - Configure Dataset - - - - Data Set: - - - - Local Snapshots - - - - Schedule: - - - - Daily - - - - Hourly - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - @ h AP - - - - Days - - - - Total - - - - Keep: - - - - Replication - - - - Replicate on a Remote System - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - h AP - - - - Apply - - - - Cancel - - - - - LPMessages - - Life Preserver Messages - - - - Messages - - - - Log Files - - - - Close - - - - - No recent messages - - - - No Log Files Available - - - - (Life Preserver) No file contents to display - - - - (Life Preserver) File does not exist: %1 - - - - (Life Preserver) File could not be opened: %1 - - - - - LPTray - - View Messages - - - - Start Application UI - - - - Close Life Preserver Tray - - - - Time: %1 - - - - %1: %2 - - - - System Alert - - - - - LPWatcher - - New snapshot of %1 - - - - Creating snapshot for %1 - - - - Replication Starting - - - - Starting replication for %1 - - - - Replication Log - - - - Finished Replication - - - - Finished replication for %1 - - - - Replication Failed for %1 - - - - Logfile available at: %1 - - - - Replication Failed - - - - Replication Error Log - - - - Replicating %1: %2 - - - - Scrub repaired %1 bad blocks - - - - Scrub repaired %1 blocks in %2 with %3 errors - - - - Scrub completed - - - - Scrub completed without needing repairs - - - - Scrubbing %1: %2 (%3 remaining) - - - - Resilvering: %1 (%2 remaining) - - - - Resilvering Started: %1 remaining - - - - Resilver completed in %1 with %2 errors - - - - Resilver completed successfully in %1 - - - - The pool is in a degraded state. See additional device error(s). - - - - %1 is degraded. - - - - The device is faulty, and should be replaced. - - - - %1 is faulty. - - - - The device was removed, and should be either be re-attached or replaced. - - - - %1 was removed. - - - - The device is unavailable and should be re-added to the pool. - - - - %1 is unavailable. - - - - - LPWizard - - New Life Preserver - - - - This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: - - - - Snapshot schedule - - - - Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. - - - - Hourly - - - - Daily @ - - - - h AP - - - - 30 minutes - - - - 10 minutes - - - - 5 minutes - - - - Snapshot pruning - - - - <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> - - - - Keep - - - - days worth of snapshots - - - - total snapshots - - - - Replication Server - - - - Replication will keep a copy of your data on a remote system in the case of a total disk failure. - - - - NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. - - - - Replicate my data - - - - Frequency - - - - With snapshot creation (Best for daily snapshots) - - - - Daily at: - - - - Host Name - - - - - User Name - - - - - SSH Port - - - - - Remote Dataset - - - - <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> - - - - - mainUI - - Life Preserver - - - - - Data Set - - - - Latest Snapshot - - - - Available - - - - Replication - - - - Enable backups of a new dataset - - - - Add - - - - Remove selected dataset from automatic backup - - - - Remove - - - - - Customize the backup configuration for the selected dataset - - - - Configure - - - - Manage SSH keys for replication authentication - - - - Key Setup - - - - Make a new snapshot immediately - - - - ... - - - - Browse a snapshot and safely recover that version of a file - - - - Browse - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - - Revert - - - - File - - - - Close Window - - - - Copy To USB Stick - - - - Generate SSH Key - - - - Mirror Dataset to USB - - - - Updating the database - - - - Enabled - - - - Disabled - - - - Configuring dataset: %1 - - - - Configuring replication: %1 - - - - Reminder - - - - Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!! - - - - Removing replication: %1 - - - - Verify Dataset Backup Removal - - - - Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset? - - - - Verify Snapshot Deletion - - - - Do you wish to remove the local snapshots for this dataset? - - - - WARNING: This is a permanant change that cannot be reversed - - - - %1: Removing snapshots - - - - %1: Disabling Replication - - - - %1: Disabling Life-Preserver Management - - - - New Snapshot Name - - - - Snapshot Name: - - - - Name - - - - Snapshot Pending - - - - The new snapshot creation has been added to the queue - - - - Verify Snapshot Reversion - - - - Are you sure that you wish to revert %1 to the selected snapshot? - - - - WARNING: This will result in the loss of any data not previously backed up. - - - - %1: Reverting dataset: %2 - - - - Reversion Error - - - - The snapshot reversion could not be completed successfully. - - - - Reversion Success - - - - The snapshot reversion was completed successfully. - - - - Revert a file - - - - Backup Files (*) - - - - Invalid Snapshot File - - - - Please select a file from within the chosen snapshot that you wish to revert - - - - %1: Reverting File: %2 - - - - Error Reverting File - - - - An error occurred while tring to revert the file %1. Please try again. - - - - FIle Reverted - - - - The reverted file is now available at: %1 - - - - Enabling dataset management: %1 - - - - %1: Setting up SSH Key - - - - Failure - - - - There was an error while creating the SSH key. - - - - Success - - - - The SSH key was successfully generated. - - - - There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin. - - - - No Valid USB Devices - - - - No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again. - - - - Select USB Device - - - - Available USB Devices: - - - - The public SSH key file was successfully copied onto the USB device. - - - - The public SSH key file could not be copied onto the USB device. - - - - diff --git a/src-qt4/life-preserver/images/tray-icon-active10.png b/src-qt4/life-preserver/images/tray-icon-active10.png deleted file mode 100644 index fee2f4097..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active10.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active11.png b/src-qt4/life-preserver/images/tray-icon-active11.png deleted file mode 100644 index 9b963f982..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active11.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active12.png b/src-qt4/life-preserver/images/tray-icon-active12.png deleted file mode 100644 index a5b880995..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active12.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active13.png b/src-qt4/life-preserver/images/tray-icon-active13.png deleted file mode 100644 index 8dd3c0aad..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active13.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active14.png b/src-qt4/life-preserver/images/tray-icon-active14.png deleted file mode 100644 index 4ebcb14d5..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active14.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active15.png b/src-qt4/life-preserver/images/tray-icon-active15.png deleted file mode 100644 index fd7306156..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active15.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active16.png b/src-qt4/life-preserver/images/tray-icon-active16.png deleted file mode 100644 index a92d1b42c..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active16.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active2.png b/src-qt4/life-preserver/images/tray-icon-active2.png deleted file mode 100644 index 1ed7472c7..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active2.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active3.png b/src-qt4/life-preserver/images/tray-icon-active3.png deleted file mode 100644 index 2355c5435..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active3.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active4.png b/src-qt4/life-preserver/images/tray-icon-active4.png deleted file mode 100644 index 0700749fb..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active4.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active5.png b/src-qt4/life-preserver/images/tray-icon-active5.png deleted file mode 100644 index d7773e34f..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active5.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active6.png b/src-qt4/life-preserver/images/tray-icon-active6.png deleted file mode 100644 index 9d0daf5c0..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active6.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active7.png b/src-qt4/life-preserver/images/tray-icon-active7.png deleted file mode 100644 index c31bef626..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active7.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active8.png b/src-qt4/life-preserver/images/tray-icon-active8.png deleted file mode 100644 index 630e81710..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active8.png and /dev/null differ diff --git a/src-qt4/life-preserver/images/tray-icon-active9.png b/src-qt4/life-preserver/images/tray-icon-active9.png deleted file mode 100644 index d3e5bca0e..000000000 Binary files a/src-qt4/life-preserver/images/tray-icon-active9.png and /dev/null differ diff --git a/src-qt4/life-preserver/life-preserver.pro b/src-qt4/life-preserver/life-preserver.pro index 34fc6ecd4..251f713ed 100644 --- a/src-qt4/life-preserver/life-preserver.pro +++ b/src-qt4/life-preserver/life-preserver.pro @@ -1,118 +1,3 @@ -TEMPLATE = app -LANGUAGE = C++ -LIBS += -lQtSolutions_SingleApplication-head +TEMPLATE = subdirs -CONFIG += qt warn_on release - -HEADERS += LPTray.h \ - mainUI.h \ - LPBackend.h \ - LPWizard.h \ - LPContainers.h \ - LPConfig.h \ - LPWatcher.h \ - LPMessages.h - -SOURCES += main.cpp \ - LPTray.cpp \ - mainUI.cpp \ - LPBackend.cpp \ - LPWizard.cpp \ - LPConfig.cpp \ - LPWatcher.cpp \ - LPMessages.cpp - -RESOURCES += lPreserve.qrc - -FORMS = mainUI.ui \ - LPWizard.ui \ - LPConfig.ui \ - LPMessages.ui - -TARGET=life-preserver -target.path=/usr/local/bin - -scripts.path=/usr/local/share/lifePreserver/scripts -scripts.files=scripts/setup-ssh-keys.sh - -images.path=/usr/local/share/lifePreserver/images/ -images.files=images/lifepreserver.png - -desktop.path=/usr/local/share/applications -desktop.files=lifepreserver.desktop - -desktopperm.path=/usr/local/share/applications/ -desktopperm.extra=chmod 644 /usr/local/share/applications/lifepreserver.desktop - -dotrans.path=/usr/local/share/lifePreserver/i18n/ -dotrans.extra=cd i18n && lrelease-qt4 -nounfinished *.ts && cp *.qm $(INSTALL_ROOT)/usr/local/share/lifePreserver/i18n/ - -INSTALLS += target dotrans images scripts - -TRANSLATIONS = i18n/LifePreserver_af.ts \ - i18n/LifePreserver_ar.ts \ - i18n/LifePreserver_az.ts \ - i18n/LifePreserver_bg.ts \ - i18n/LifePreserver_bn.ts \ - i18n/LifePreserver_bs.ts \ - i18n/LifePreserver_ca.ts \ - i18n/LifePreserver_cs.ts \ - i18n/LifePreserver_cy.ts \ - i18n/LifePreserver_da.ts \ - i18n/LifePreserver_de.ts \ - i18n/LifePreserver_el.ts \ - i18n/LifePreserver_en_GB.ts \ - i18n/LifePreserver_en_ZA.ts \ - i18n/LifePreserver_es.ts \ - i18n/LifePreserver_et.ts \ - i18n/LifePreserver_eu.ts \ - i18n/LifePreserver_fa.ts \ - i18n/LifePreserver_fi.ts \ - i18n/LifePreserver_fr.ts \ - i18n/LifePreserver_fr_CA.ts \ - i18n/LifePreserver_fur.ts \ - i18n/LifePreserver_gl.ts \ - i18n/LifePreserver_he.ts \ - i18n/LifePreserver_hi.ts \ - i18n/LifePreserver_hr.ts \ - i18n/LifePreserver_hu.ts \ - i18n/LifePreserver_id.ts \ - i18n/LifePreserver_is.ts \ - i18n/LifePreserver_it.ts \ - i18n/LifePreserver_ja.ts \ - i18n/LifePreserver_ka.ts \ - i18n/LifePreserver_ko.ts \ - i18n/LifePreserver_lt.ts \ - i18n/LifePreserver_lv.ts \ - i18n/LifePreserver_mk.ts \ - i18n/LifePreserver_mn.ts \ - i18n/LifePreserver_ms.ts \ - i18n/LifePreserver_mt.ts \ - i18n/LifePreserver_nb.ts \ - i18n/LifePreserver_ne.ts \ - i18n/LifePreserver_nl.ts \ - i18n/LifePreserver_pa.ts \ - i18n/LifePreserver_pl.ts \ - i18n/LifePreserver_pt.ts \ - i18n/LifePreserver_pt_BR.ts \ - i18n/LifePreserver_ro.ts \ - i18n/LifePreserver_ru.ts \ - i18n/LifePreserver_sa.ts \ - i18n/LifePreserver_sk.ts \ - i18n/LifePreserver_sl.ts \ - i18n/LifePreserver_sr.ts \ - i18n/LifePreserver_sv.ts \ - i18n/LifePreserver_sw.ts \ - i18n/LifePreserver_ta.ts \ - i18n/LifePreserver_tg.ts \ - i18n/LifePreserver_th.ts \ - i18n/LifePreserver_tr.ts \ - i18n/LifePreserver_uk.ts \ - i18n/LifePreserver_uz.ts \ - i18n/LifePreserver_vi.ts \ - i18n/LifePreserver_zh_CN.ts \ - i18n/LifePreserver_zh_HK.ts \ - i18n/LifePreserver_zh_TW.ts \ - i18n/LifePreserver_zu.ts - -QMAKE_LIBDIR = /usr/local/lib/qt4 /usr/local/lib +SUBDIRS+= lp-tray lp-gui diff --git a/src-qt4/life-preserver/LPBackend.cpp b/src-qt4/life-preserver/lp-gui/LPBackend.cpp similarity index 83% rename from src-qt4/life-preserver/LPBackend.cpp rename to src-qt4/life-preserver/lp-gui/LPBackend.cpp index 7a10bc3ed..5bdb5bdaf 100644 --- a/src-qt4/life-preserver/LPBackend.cpp +++ b/src-qt4/life-preserver/lp-gui/LPBackend.cpp @@ -63,7 +63,7 @@ QStringList LPBackend::listLPSnapshots(QString dataset){ QStringList out = LPBackend::getCmdOutput(cmd); //Now process the output QStringList list; - for(int i=out.length()-1; i>=0; i--){ //go in reverse order for proper time format (newest first) + for(int i=0; inewest if(out[i].startsWith(dataset+"@")){ QString snap = out[i].section("@",1,3).section(" ",0,0).simplified();; if(!snap.isEmpty()){ list << snap; } @@ -184,55 +184,6 @@ bool LPBackend::revertSnapshot(QString dataset, QString snapshot){ return (ret == 0); } -QString LPBackend::revertSnapshotFile(QString dsmountpoint, QString snapshot, QString filepath){ - //Copy the given file from the snapshot back into the main dataset - // -- filepath: full path to the file in the snapshot directory - //qDebug() << " - Revert file:" << filepath; - filepath.replace("~",QDir::homePath()); - //Check that the file path is complete and the file exists - if(!QFile::exists(filepath)){ - //invalid file given - return ""; - } - //Generate the new file path - QString newfilepath = filepath.replace(dsmountpoint+"/.zfs/snapshot/"+snapshot, dsmountpoint); - if( QFile::exists(newfilepath) ){ - //get the file extension - QString filename = newfilepath.section("/",-1); - QString ext = filename.section(".",-1); - if( !ext.isEmpty() && !filename.startsWith("."+ext) && ext!=filename){ - newfilepath.chop(ext.length()+1); - newfilepath.append("-reversion."+ext); - int i=1; - //append a number to the end if a reversion file already exists - while(QFile::exists(newfilepath)){ - newfilepath.chop(ext.length()+1); - newfilepath.append(QString::number(i)+"."+ext); - i ++; - } - }else{ - //File without an extension - just append a number - newfilepath.append("-reversion"); - int i=1; - QString npath = newfilepath; - while(QFile::exists(npath)){ - npath = newfilepath.append(QString::number(i)); - i++; - } - newfilepath = npath; - } - } - //perform the copy - qDebug() << " - File Reversion:" << filepath << newfilepath; - bool ok = QFile::copy(filepath,newfilepath); - //return the path to the new file if the copy was successful - if(ok){ - //reset the permissions on the reverted file to match the original - QFile::setPermissions(newfilepath, QFile::permissions(filepath)); - return newfilepath; - }else{ return ""; } -} - // ================== // Replication Management // ================== @@ -318,7 +269,7 @@ bool LPBackend::copySSHKey(QString mountPath, QString localHost){ } // ====================== -// Device Management +// USB Device Management // ====================== QStringList LPBackend::listDevices(){ //Scan the system for all valid da* and ada* devices (USB/SCSI, SATA) @@ -336,15 +287,48 @@ QStringList LPBackend::listDevices(){ } bool LPBackend::isMounted(QString device){ - qDebug() << "Device mount check not implemented yet"; + qDebug() << "Device mount check not implemented yet:" << device; return false; } bool LPBackend::unmountDevice(QString device){ - qDebug() << "Device unmounting not implemented yet"; + qDebug() << "Device unmounting not implemented yet:" << device; return false; } +// ====================== +// ZPOOL Disk Management +// ====================== +bool LPBackend::attachDisk(QString pool, QString disk){ + if( !disk.startsWith("/dev/") ){ disk.prepend("/dev/"); } //make sure it is the full disk path + if( !QFile::exists(disk) ){ return false; } //make sure the disk exists + QString cmd = "lpreserver zpool attach "+pool+" "+disk; + //Run the command + int ret = LPBackend::runCmd(cmd); + return (ret ==0); +} + +bool LPBackend::detachDisk(QString pool, QString disk){ + QString cmd = "lpreserver zpool detach "+pool+" "+disk; + //Run the command + int ret = LPBackend::runCmd(cmd); + return (ret ==0); +} + +bool LPBackend::setDiskOnline(QString pool, QString disk){ + QString cmd = "lpreserver zpool online "+pool+" "+disk; + //Run the command + int ret = LPBackend::runCmd(cmd); + return (ret ==0); +} + +bool LPBackend::setDiskOffline(QString pool, QString disk){ + QString cmd = "lpreserver zpool offline "+pool+" "+disk; + //Run the command + int ret = LPBackend::runCmd(cmd); + return (ret ==0); +} + // ========================= // PRIVATE FUNCTIONS // ========================= diff --git a/src-qt4/life-preserver/LPBackend.h b/src-qt4/life-preserver/lp-gui/LPBackend.h similarity index 89% rename from src-qt4/life-preserver/LPBackend.h rename to src-qt4/life-preserver/lp-gui/LPBackend.h index bfb2af900..cfef1f100 100644 --- a/src-qt4/life-preserver/LPBackend.h +++ b/src-qt4/life-preserver/lp-gui/LPBackend.h @@ -28,7 +28,6 @@ class LPBackend{ static void newSnapshot(QString dataset, QString snapshotname); static bool removeSnapshot(QString dataset, QString snapshot); static bool revertSnapshot(QString dataset, QString snapshot); //revert to given snapshot - static QString revertSnapshotFile(QString dataset, QString snapshot, QString filepath); //Replication Management static bool setupReplication(QString dataset, QString remotehost, QString user, int port, QString remotedataset, int time); static bool removeReplication(QString dataset); @@ -37,12 +36,15 @@ class LPBackend{ static bool setupSSHKey(QString remoteHost, QString remoteUser, int remotePort); static QStringList findValidUSBDevices(); static bool copySSHKey(QString mountPath, QString localHost); - //Device Management + //USB Device Management static QStringList listDevices(); static bool isMounted(QString device); static bool unmountDevice(QString device); - //Mirroring Management - + //Zpool disk Management + static bool attachDisk(QString pool, QString disk); + static bool detachDisk(QString pool, QString disk); + static bool setDiskOnline(QString pool, QString disk); + static bool setDiskOffline(QString pool, QString disk); //General utility functions static QStringList getCmdOutput(QString); static int runCmd(QString); diff --git a/src-qt4/life-preserver/LPConfig.cpp b/src-qt4/life-preserver/lp-gui/LPConfig.cpp similarity index 100% rename from src-qt4/life-preserver/LPConfig.cpp rename to src-qt4/life-preserver/lp-gui/LPConfig.cpp diff --git a/src-qt4/life-preserver/LPConfig.h b/src-qt4/life-preserver/lp-gui/LPConfig.h similarity index 100% rename from src-qt4/life-preserver/LPConfig.h rename to src-qt4/life-preserver/lp-gui/LPConfig.h diff --git a/src-qt4/life-preserver/LPConfig.ui b/src-qt4/life-preserver/lp-gui/LPConfig.ui similarity index 100% rename from src-qt4/life-preserver/LPConfig.ui rename to src-qt4/life-preserver/lp-gui/LPConfig.ui diff --git a/src-qt4/life-preserver/LPContainers.h b/src-qt4/life-preserver/lp-gui/LPContainers.h similarity index 83% rename from src-qt4/life-preserver/LPContainers.h rename to src-qt4/life-preserver/lp-gui/LPContainers.h index 4018a6684..038732eb7 100644 --- a/src-qt4/life-preserver/LPContainers.h +++ b/src-qt4/life-preserver/lp-gui/LPContainers.h @@ -12,9 +12,11 @@ class LPDataset{ ~LPDataset(){} //Information needed on each dataset - QString latestReplication; + QString finishedStatus, runningStatus, errorStatus; QString latestSnapshot; - QString numberOfSnapshots; + QStringList harddisks; + QStringList harddiskStatus; + QString poolStatus; QHash subsetHash; // (complete dataset name should be ) //Simplification functions for getting info from the hash diff --git a/src-qt4/life-preserver/lp-gui/LPGUtils.cpp b/src-qt4/life-preserver/lp-gui/LPGUtils.cpp new file mode 100644 index 000000000..798117e05 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/LPGUtils.cpp @@ -0,0 +1,254 @@ +#include "LPGUtils.h" + +LPDataset LPGUtils::loadPoolData(QString zpool){ + //Load the current information for the given zpool + qDebug() << "New Dataset: " << zpool; + LPDataset DSC; + //List all the mountpoints in this dataset + QStringList subsets = LPBackend::listDatasetSubsets(zpool); + QStringList lpsnaps = LPBackend::listLPSnapshots(zpool); + //populate the list of snapshots available for each mountpoint + for(int i=0; i -1){ subsnaps << lpsnaps[s]; snaps.removeAt(index); } + } + /*//Now list all the other available snapshots (no certain ordering) + if(!snaps.isEmpty()){try + subsnaps << "--"; //so we know that this is a divider between the sections + subsnaps << snaps; + }*/ + DSC.subsetHash.insert(subsets[i],subsnaps); //add it to the internal container hash + } + } + //Parse "zpool status " + QStringList zstat = LPBackend::getCmdOutput("zpool status "+zpool); + //qDebug() << "zpool status "+zpool+":\n" << zstat.join("\n"); + bool atheader=false; + QStringList disks, diskstates, running, errors, finished; + for(int i=0; iclear(); + //Determine if the file exists + if( !QFile::exists(packagePath) ){ return false; } + //Check the username of the home dir in the package + QStringList ret = LPBackend::getCmdOutput("tar -tvf "+packagePath); + if(ret.isEmpty()){ return false; } + QString username = ret[0].section(" ",2,2,QString::SectionSkipEmpty).simplified(); + QString dirname = ret[0].section(" ",8,8,QString::SectionSkipEmpty).section("/",0,0).simplified(); + user->append(username); //additional output + //Now check for the user on the local system + //This is just a simple check that the user directory exists, and the user/directory are the same within the package + return (username == dirname && QFile::exists("/usr/home/"+dirname) ); +} + +bool LPGUtils::extractHomeDirPackage(QString packagePath){ + //Determine if the file exists + if( !QFile::exists(packagePath) ){ return false; } + //Now extract the archive in the home directory + QString cmd = "tar -xpf "+packagePath+" -C /usr/home"; + qDebug() << "Extract command:" << cmd; + int ret = LPBackend::runCmd(cmd); + return (ret == 0); +} + +QStringList LPGUtils::listAvailableHardDisks(){ + QDir dev("/dev"); + QStringList filters; + filters << "ada*" << "da*"; + QStringList devs = dev.entryList(filters, QDir::Files | QDir::System | QDir::NoDotAndDotDot, QDir::Name); + //Filter out all the partitions (only keep full devices) + for(int i=0; i +#include +#include +#include +#include +#include + +#include "LPBackend.h" +#include "LPContainers.h" + +class LPGUtils{ +public: + static LPDataset loadPoolData(QString zpool); //Load backend data into container + static QString generateReversionFileName(QString filename, QString destDir); + static bool revertFile(QString oldPath, QString newPath); //copy a file out of a snapshot + static QStringList revertDir(QString oldPath, QString newPath); //copy a dir out of a snapshot + //Functions for packaging up a user's home directory and extracting it later + static QString packageHomeDir(QString username, QString packageName); + static bool checkPackageUserPath(QString packagePath, QString *user); + static bool extractHomeDirPackage(QString packagePath); + //Function to scan the system for available harddisks/devices + static QStringList listAvailableHardDisks(); +}; + +#endif diff --git a/src-qt4/life-preserver/lp-gui/LPMain.cpp b/src-qt4/life-preserver/lp-gui/LPMain.cpp new file mode 100644 index 000000000..832ac1402 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/LPMain.cpp @@ -0,0 +1,671 @@ +#include "LPMain.h" +#include "ui_LPMain.h" + +LPMain::LPMain(QWidget *parent) : QMainWindow(parent), ui(new Ui::LPMain){ + ui->setupUi(this); //load the Qt-designer UI file + //Create the basic/advanced view options + viewBasic = new QRadioButton(tr("Basic"), ui->menuView); + QWidgetAction *WABasic = new QWidgetAction(this); WABasic->setDefaultWidget(viewBasic); + ui->menuView->addAction(WABasic); + viewAdvanced = new QRadioButton(tr("Advanced"), ui->menuView); + QWidgetAction *WAAdv = new QWidgetAction(this); WAAdv->setDefaultWidget(viewAdvanced); + ui->menuView->addAction(WAAdv); + connect(viewBasic, SIGNAL(toggled(bool)), this, SLOT(viewChanged()) ); + //Now set the default view type + viewBasic->setChecked(true); //will automatically call the "viewChanged" function + //Create the filesystem model and tie it to the treewidget + fsModel = new QFileSystemModel(this); + fsModel->setReadOnly(true); + ui->treeView->setModel(fsModel); + //Connect the UI to all the functions + connect(ui->tool_refresh, SIGNAL(clicked()), this, SLOT(updatePoolList()) ); + connect(ui->combo_pools, SIGNAL(currentIndexChanged(int)), this, SLOT(updateTabs()) ); + connect(ui->combo_datasets, SIGNAL(currentIndexChanged(int)), this, SLOT(updateDataset()) ); + connect(ui->slider_snapshots, SIGNAL(valueChanged(int)), this, SLOT(updateSnapshot()) ); + connect(ui->push_prevsnap, SIGNAL(clicked()), this, SLOT(prevSnapshot()) ); + connect(ui->push_nextsnap, SIGNAL(clicked()), this, SLOT(nextSnapshot()) ); + connect(ui->check_hidden, SIGNAL(stateChanged(int)), this, SLOT(setFileVisibility()) ); + connect(ui->push_restore, SIGNAL(clicked()), this, SLOT(restoreFiles()) ); + connect(ui->push_configure, SIGNAL(clicked()), this, SLOT(openConfigGUI()) ); + //Connect the Menu buttons + connect(ui->menuManage_Pool, SIGNAL(triggered(QAction*)), this, SLOT(menuAddPool(QAction*)) ); + connect(ui->menuUnmanage_Pool, SIGNAL(triggered(QAction*)), this, SLOT(menuRemovePool(QAction*)) ); + connect(ui->action_SaveKeyToUSB, SIGNAL(triggered()), this, SLOT(menuSaveSSHKey()) ); + connect(ui->actionClose_Window, SIGNAL(triggered()), this, SLOT(menuCloseWindow()) ); + connect(ui->menuCompress_Home_Dir, SIGNAL(triggered(QAction*)), this, SLOT(menuCompressHomeDir(QAction*)) ); + connect(ui->actionExtract_Home_Dir, SIGNAL(triggered()), this, SLOT(menuExtractHomeDir()) ); + connect(ui->actionAdd_Disk, SIGNAL(triggered()), this, SLOT(menuAddDisk()) ); + connect(ui->menuRemove_Disk, SIGNAL(triggered(QAction*)), this, SLOT(menuRemoveDisk(QAction*)) ); + connect(ui->menuSet_Disk_Offline, SIGNAL(triggered(QAction*)), this, SLOT(menuOfflineDisk(QAction*)) ); + connect(ui->menuSet_Disk_Online, SIGNAL(triggered(QAction*)), this, SLOT(menuOnlineDisk(QAction*)) ); + connect(ui->action_startScrub, SIGNAL(triggered()), this, SLOT(menuStartScrub()) ); + connect(ui->action_stopScrub, SIGNAL(triggered()), this, SLOT(menuStopScrub()) ); + connect(ui->action_newSnapshot, SIGNAL(triggered()), this, SLOT(menuNewSnapshot()) ); + connect(ui->menuDelete_Snapshot, SIGNAL(triggered(QAction*)), this, SLOT(menuRemoveSnapshot(QAction*)) ); + //Update the interface + QTimer::singleShot(0,this,SLOT(updatePoolList()) ); + + //Make sure the status tab is shown initially + ui->tabWidget->setCurrentWidget(ui->tab_status); +} + +LPMain::~LPMain(){ + +} + +// ============== +// PUBLIC SLOTS +// ============== +void LPMain::slotSingleInstance(){ + this->raise(); + this->show(); +} + +// ============== +// PRIVATE +// ============== +void LPMain::showErrorDialog(QString title, QString message, QString errors){ + QMessageBox MB(QMessageBox::Warning, title, message, QMessageBox::Ok, this); + MB.setDetailedText(errors); + MB.exec(); +} + +void LPMain::showWaitBox(QString message){ + if(waitBox == 0){ + qDebug() << "New Wait Box"; + waitBox = new QMessageBox(QMessageBox::NoIcon, tr("Please Wait"), message, QMessageBox::NoButton, this); + waitBox->setWindowModality(Qt::WindowModal); + }else{ + qDebug() << "Update Wait Box:" << message; + waitBox->setText(message); + } + if(!waitBox->isVisible()){ waitBox->show(); waitBox->raise(); } + QCoreApplication::processEvents(); +} + +void LPMain::hideWaitBox(){ + if(waitBox != 0){ + if(waitBox->isVisible()){ waitBox->hide(); } + } + +} + +// ============== +// PRIVATE SLOTS +// ============== +void LPMain::updatePoolList(){ + //Get the currently selected pool (if there is one) + qDebug() << "Update Pool List"; + QString cPool; + if(ui->combo_pools->currentIndex() != -1){ cPool = ui->combo_pools->currentText(); } + //Get the list of managed pools + QStringList pools = LPBackend::listDatasets(); + QStringList poolsAvail = LPBackend::listPossibleDatasets(); + //Now put the lists into the UI + ui->combo_pools->clear(); + if(!pools.isEmpty()){ ui->combo_pools->addItems(pools); } + //Now set the currently selected pools + if(pools.length() > 0){ + poolSelected=true; + int index = pools.indexOf(cPool); + if(index < 0){ ui->combo_pools->setCurrentIndex(0); } + else{ ui->combo_pools->setCurrentIndex(index); } + }else{ + //No managed pools + poolSelected=false; + ui->combo_pools->addItem("No Managed Pools!"); + ui->combo_pools->setCurrentIndex(0); + } + //Now update the add/remove pool menu's + ui->menuManage_Pool->clear(); + for( int i=0; imenuManage_Pool->addAction(poolsAvail[i]); + } + ui->menuManage_Pool->setEnabled( !ui->menuManage_Pool->isEmpty() ); + ui->menuUnmanage_Pool->clear(); + for( int i=0; imenuUnmanage_Pool->addAction(pools[i]); + } + ui->menuUnmanage_Pool->setEnabled( !ui->menuUnmanage_Pool->isEmpty() ); + //Now update the user's that are available for home-dir packaging + QDir hdir("/usr/home"); + QStringList users = hdir.entryList(QDir::Dirs | QDir::NoDotAndDotDot, QDir::Name); + ui->menuCompress_Home_Dir->clear(); + for(int i=0; imenuCompress_Home_Dir->addAction(users[i]); + } + //Now update the interface appropriately + ui->combo_pools->setEnabled(poolSelected); + updateTabs(); +} + +void LPMain::viewChanged(){ + ui->menuView->hide(); + ui->menubar->clear(); + if(viewBasic->isChecked()){ + ui->menubar->addMenu(ui->menuFile); + ui->menubar->addMenu(ui->menuView); + ui->menubar->addMenu(ui->menuClassic_Backups); + }else{ + ui->menubar->addMenu(ui->menuFile); + ui->menubar->addMenu(ui->menuView); + ui->menubar->addMenu(ui->menuClassic_Backups); + ui->menubar->addMenu(ui->menuSnapshots); + ui->menubar->addMenu(ui->menuDisks); + } +} + +void LPMain::updateTabs(){ + //qDebug() << "Update Tabs" << poolSelected; + viewChanged(); + ui->tabWidget->setEnabled(poolSelected); + ui->menuView->setEnabled(poolSelected); + ui->menuDisks->setEnabled(poolSelected); + ui->menuSnapshots->setEnabled(poolSelected); + ui->push_configure->setVisible(poolSelected); + ui->action_SaveKeyToUSB->setEnabled(poolSelected); + if(poolSelected){ + showWaitBox(tr("Loading zpool information")); + POOLDATA = LPGUtils::loadPoolData(ui->combo_pools->currentText()); + hideWaitBox(); + //Now list the status information + ui->label_status->setText(POOLDATA.poolStatus); + ui->label_numdisks->setText( QString::number(POOLDATA.harddisks.length()) ); + ui->label_latestsnapshot->setText(POOLDATA.latestSnapshot); + if(POOLDATA.finishedStatus.isEmpty()){ ui->label_finishedstat->setVisible(false); } + else{ + ui->label_finishedstat->setText(POOLDATA.finishedStatus); + ui->label_finishedstat->setVisible(true); + } + if(POOLDATA.runningStatus.isEmpty()){ ui->label_runningstat->setVisible(false); } + else{ + ui->label_runningstat->setText(POOLDATA.runningStatus); + ui->label_runningstat->setVisible(true); + } + if(POOLDATA.errorStatus.isEmpty()){ ui->label_errorstat->setVisible(false); } + else{ + ui->label_errorstat->setText(POOLDATA.errorStatus); + ui->label_errorstat->setVisible(true); + } + //Now list the data restore options + QString cds = ui->combo_datasets->currentText(); + ui->combo_datasets->clear(); + QStringList dslist = POOLDATA.subsets(); + ui->combo_datasets->addItems(dslist); + int dsin = dslist.indexOf(cds); + if(dsin >= 0){ ui->combo_datasets->setCurrentIndex(dsin); } + else if( !dslist.isEmpty() ){ ui->combo_datasets->setCurrentIndex(0); } + else{ ui->combo_datasets->addItem(tr("No datasets available")); } + //NOTE: this automatically calls the "updateDataset()" function in a new thread + + //Now update the snapshot removal menu list + QStringList snaps = LPBackend::listLPSnapshots(ui->combo_pools->currentText()); + ui->menuDelete_Snapshot->clear(); + for(int i=0; imenuDelete_Snapshot->addAction(snaps[i]); + } + ui->menuDelete_Snapshot->setEnabled( !ui->menuDelete_Snapshot->isEmpty() ); + //Now update the disk menu items + ui->menuRemove_Disk->clear(); + ui->menuSet_Disk_Offline->clear(); + ui->menuSet_Disk_Online->clear(); + for(int i=0; imenuRemove_Disk->addAction(POOLDATA.harddisks[i]); + if(POOLDATA.harddiskStatus[i] == "OFFLINE"){ + ui->menuSet_Disk_Online->addAction(POOLDATA.harddisks[i]); + }else{ + ui->menuSet_Disk_Offline->addAction(POOLDATA.harddisks[i]); + } + } + ui->menuRemove_Disk->setEnabled(!ui->menuRemove_Disk->isEmpty()); + ui->menuSet_Disk_Offline->setEnabled(!ui->menuSet_Disk_Offline->isEmpty()); + ui->menuSet_Disk_Online->setEnabled(!ui->menuSet_Disk_Online->isEmpty()); + }else{ + //No Pool selected + ui->label_numdisks->clear(); + ui->label_latestsnapshot->clear(); + ui->label_status->clear(); + ui->label_errorstat->setVisible(false); + ui->label_runningstat->setVisible(false); + ui->label_finishedstat->setVisible(false); + } + +} + +void LPMain::updateDataset(){ + //Update the snapshots for the currently selected dataset + QString cds = ui->combo_datasets->currentText(); + if(POOLDATA.subsets().indexOf(cds) >= 0){ + QStringList snaps = POOLDATA.snapshots(cds); + qDebug() << "Update Dataset"; + ui->slider_snapshots->setEnabled(true); + ui->slider_snapshots->setMinimum(0); + int max = snaps.length() -1; + if(max < 0){ max = 0; ui->slider_snapshots->setEnabled(false); } + ui->slider_snapshots->setMaximum(max); + ui->slider_snapshots->setValue(max); //most recent snapshot + updateSnapshot(); + }else{ + ui->slider_snapshots->setEnabled(false); + ui->label_snapshot->clear(); + ui->push_nextsnap->setEnabled(false); + ui->push_prevsnap->setEnabled(false); + } + +} + +void LPMain::updateSnapshot(){ + int sval = ui->slider_snapshots->value(); + QStringList snaps = POOLDATA.snapshots(ui->combo_datasets->currentText()); + //qDebug() << "Update Snapshot"; + //Update the previous/next buttons + if(sval == ui->slider_snapshots->minimum() ){ ui->push_prevsnap->setEnabled(false); } + else{ ui->push_prevsnap->setEnabled(true); } + if(sval == ui->slider_snapshots->maximum() ){ ui->push_nextsnap->setEnabled(false); } + else{ ui->push_nextsnap->setEnabled(true); } + //Now update the snapshot viewer + if(snaps.isEmpty()){ ui->label_snapshot->clear(); ui->slider_snapshots->setEnabled(false); } + else{ + QString snap = snaps.at(sval); + QString path = ui->combo_datasets->currentText() + "/.zfs/snapshot/"+snap; + //qDebug() << "Snapshot path:" << path; + ui->label_snapshot->setText(snap); + //Now update the snapshot view + ui->treeView->setRootIndex( fsModel->setRootPath(path) ); + + } +} + +void LPMain::nextSnapshot(){ + ui->slider_snapshots->setValue( ui->slider_snapshots->value()+1 ); +} + +void LPMain::prevSnapshot(){ + ui->slider_snapshots->setValue( ui->slider_snapshots->value()-1 ); +} + +void LPMain::setFileVisibility(){ + if(ui->check_hidden->isChecked()){ + fsModel->setFilter(QDir::AllDirs | QDir::Files | QDir::NoDotAndDotDot | QDir::Hidden ); + }else{ + fsModel->setFilter(QDir::AllDirs | QDir::Files | QDir::NoDotAndDotDot ); + } +} + +void LPMain::restoreFiles(){ + QString filePath = fsModel->filePath( ui->treeView->currentIndex() ); + qDebug() << " Restore file(s):" << filePath; + QString destDir = filePath.remove("/.zfs/snapshot/"+ui->label_snapshot->text()); + destDir.chop( filePath.section("/",-1).size()+1 ); //get rid of the filename at the end + while(!QFile::exists(destDir)){ destDir.chop( destDir.section("/",-1).size() +1); } + QString newFilePath = destDir+"/"+LPGUtils::generateReversionFileName(filePath, destDir); + //qDebug() << "Destination:" << newFilePath; + //Perform the reversion(s) + QStringList errors; + if(QFileInfo(filePath).isDir()){ + //Is a directory + showWaitBox( QString(tr("Restoring Directory: %1")).arg(newFilePath) ); + errors = LPGUtils::revertDir(filePath, newFilePath); + hideWaitBox(); + if(!errors.isEmpty()){ + qDebug() << "Failed Reversions:" << errors; + errors.prepend(tr("File destination(s) that could not be restored:")+"\n"); + showErrorDialog(tr("Reversion Error"), tr("Some files could not be restored from the snapshot."), errors.join("\n") ); + }else{ + qDebug() << "Reversion successful"; + QMessageBox::information(this,tr("Restore Successful"),QString(tr("The following directory was succesfully restored: %1")).arg(newFilePath) ); + } + }else{ + //Just a single file + showWaitBox( QString(tr("Restoring file: %1")).arg(newFilePath) ); + bool ok = LPGUtils::revertFile(filePath, newFilePath); + hideWaitBox(); + if( !ok ){ + qDebug() << "Failed Reversion:" << newFilePath; + errors << QString(tr("Snapshot file: %1")).arg(filePath); + errors << QString(tr("Destination: %1")).arg(newFilePath); + errors << tr("Please check that the destination directory exists and is writable"); + showErrorDialog(tr("Reversion Error"), tr("The file could not be restored from the snapshot."), errors.join("\n") ); + }else{ + qDebug() << "Reversion successful"; + QMessageBox::information(this,tr("Restore Successful"),QString(tr("The following file was succesfully restored: %1")).arg(newFilePath) ); + } + } + +} + +void LPMain::openConfigGUI(){ + qDebug() << "Open Configuration UI"; + QString ds = ui->combo_pools->currentText(); + if(ds.isEmpty()){ return; } + LPConfig CFG(this); + CFG.loadDataset(ds, LPBackend::listReplicationTargets().contains(ds)); + CFG.exec(); + //Now check for return values and update appropriately + bool change = false; + if(CFG.localChanged){ + ui->statusbar->showMessage(QString(tr("Configuring dataset: %1")).arg(ds),0); + LPBackend::setupDataset(ds, CFG.localSchedule, CFG.localSnapshots); + ui->statusbar->clearMessage(); + change = true; + } + if(CFG.remoteChanged){ + change = true; + if(CFG.isReplicated){ + ui->statusbar->showMessage(QString(tr("Configuring replication: %1")).arg(ds),0); + LPBackend::setupReplication(ds, CFG.remoteHost, CFG.remoteUser, CFG.remotePort, CFG.remoteDataset, CFG.remoteFreq); + QMessageBox::information(this,tr("Reminder"),tr("Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!!")); + }else{ + ui->statusbar->showMessage(QString(tr("Removing replication: %1")).arg(ds),0); + LPBackend::removeReplication(ds); + } + ui->statusbar->clearMessage(); + } + //Now update the UI if appropriate + if(change){ + updateTabs(); + } +} + +// ----------------------------------------------- +// MENU SLOTS +// ----------------------------------------------- +// ==== File Menu ==== +void LPMain::menuAddPool(QAction *act){ + QString dataset = act->text(); + qDebug() << "Start Wizard for new managing pool:" << dataset; + LPWizard wiz(this); + wiz.setDataset(dataset); + wiz.exec(); + //See if the wizard was cancelled or not + if(!wiz.cancelled){ + ui->statusbar->showMessage(QString(tr("Enabling dataset management: %1")).arg(dataset),0); + //run the proper commands to get the dataset enabled + if( LPBackend::setupDataset(dataset, wiz.localTime, wiz.totalSnapshots) ){ + if(wiz.enableReplication){ + LPBackend::setupReplication(dataset, wiz.remoteHost, wiz.remoteUser, wiz.remotePort, wiz.remoteDataset, wiz.remoteTime); + QMessageBox::information(this,tr("Reminder"),tr("Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!!")); + } + } + ui->statusbar->clearMessage(); + //Now update the list of pools + updatePoolList(); + } +} + +void LPMain::menuRemovePool(QAction *act){ + QString ds = act->text(); + qDebug() << "Remove Pool:" << ds; + if(!ds.isEmpty()){ + //Verify the removal of the dataset + if( QMessageBox::Yes == QMessageBox::question(this,tr("Verify Dataset Backup Removal"),tr("Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset?")+"\n\n"+ds,QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + //verify the removal of all the snapshots for this dataset + QStringList snaps = LPBackend::listLPSnapshots(ds); + if(!snaps.isEmpty()){ + if( QMessageBox::Yes == QMessageBox::question(this,tr("Verify Snapshot Deletion"),tr("Do you wish to remove the local snapshots for this dataset?")+"\n"+tr("WARNING: This is a permanant change that cannot be reversed"),QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + //Remove all the snapshots + ui->statusbar->showMessage(QString(tr("%1: Removing snapshots")).arg(ds),0); + showWaitBox(tr("Removing snapshots")); + for(int i=0; istatusbar->clearMessage(); + } + } + //Remove the dataset from life-preserver management + if(LPBackend::listReplicationTargets().contains(ds)){ + ui->statusbar->showMessage(QString(tr("%1: Disabling Replication")).arg(ds),0); + showWaitBox(tr("Disabling Replication")); + LPBackend::removeReplication(ds); + ui->statusbar->clearMessage(); + } + ui->statusbar->showMessage(QString(tr("%1: Disabling Life-Preserver Management")).arg(ds),0); + showWaitBox(tr("Removing Life Preserver Schedules")); + LPBackend::removeDataset(ds); + ui->statusbar->clearMessage(); + updatePoolList(); + hideWaitBox(); + } + } //end check for empty ds + +} + +void LPMain::menuSaveSSHKey(){ + QString ds = ui->combo_pools->currentText(); + qDebug() << "Save SSH Key:" << ds; + if(ds.isEmpty()){ return; } + //Get the local hostname + char host[1023] = "\0"; + gethostname(host,1023); + QString localHost = QString(host).simplified(); + qDebug() << " - hostname:" << localHost; + //Scan for mounted USB devices + QStringList devs = LPBackend::findValidUSBDevices(); + qDebug() << " - devs:" << devs; + if(devs.isEmpty()){ + QMessageBox::warning(this,tr("No Valid USB Devices"), tr("No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again.")); + return; + } + //Ask the user which one to save the file to + bool ok; + QString dev = QInputDialog::getItem(this, tr("Select USB Device"), tr("Available USB Devices:"), devs,0,false,&ok); + if(!ok or dev.isEmpty()){ return; } //cancelled + QString devPath = dev.section("(",0,0).simplified(); + //Now copy the file over + ok = LPBackend::copySSHKey(devPath, localHost); + if(ok){ + QMessageBox::information(this,tr("Success"), tr("The public SSH key file was successfully copied onto the USB device.")); + }else{ + QMessageBox::information(this,tr("Failure"), tr("The public SSH key file could not be copied onto the USB device.")); + } +} + +void LPMain::menuCloseWindow(){ + this->close(); +} + +// ==== Classic Backups Menu ==== +void LPMain::menuCompressHomeDir(QAction* act){ + QString user = act->text(); + qDebug() << "Compress Home Dir:" << user; + //Prompt for the package name + QString pkgName = user+"-"+QDateTime::currentDateTime().toString("yyyyMMdd-hhmm"); + bool ok; + pkgName = QInputDialog::getText(this, tr("Package Name"), tr("Name of the package to create:"), QLineEdit::Normal, pkgName, &ok); + if(!ok || pkgName.isEmpty() ){ return; } //cancelled + //Now create the package + showWaitBox(tr("Packaging home directory")); + QString pkgPath = LPGUtils::packageHomeDir(user, pkgName); + hideWaitBox(); + //Now inform the user of the result + if(pkgPath.isEmpty()){ + qDebug() << "No Package created"; + QMessageBox::warning(this,tr("Package Failure"), tr("The home directory package could not be created.")); + }else{ + qDebug() << "Package created at:" << pkgPath; + QMessageBox::information(this,tr("Package Success"), tr("The home directory package was successfully created.")+"\n\n"+pkgPath); + } +} + +void LPMain::menuExtractHomeDir(){ + qDebug() << "Extract Home Dir"; + //Get the file path from the user + QString filePath = QFileDialog::getOpenFileName(this,tr("Find Home Dir Package"), "/usr/home", tr("Home Dir Package (*.home.tar.gz)") ); + if(filePath.isEmpty() || !QFile::exists(filePath)){ return; } //cancelled + //Now check if the user in the package is also on the system + QString username; + bool ok = LPGUtils::checkPackageUserPath(filePath, &username); + if(!ok){ + QMessageBox::warning(this,tr("User Missing"),QString(tr("The user (%1) does not exist on this system. Please create this user first and then try again.")).arg(username) ); + return; + } + //Now extract the package + showWaitBox(tr("Extracting Home Directory")); + ok = LPGUtils::extractHomeDirPackage(filePath); + hideWaitBox(); + //Now report the results + if(ok){ + QMessageBox::information(this,tr("Package Extracted"), QString(tr("The package was successfully extracted within %1")).arg("/usr/home/"+username) ); + }else{ + QMessageBox::warning(this, tr("Package Failure"), QString(tr("The package could not be extracted within %1")).arg("/usr/home/"+username) ); + } + +} + +// ==== Disks Menu ==== +void LPMain::menuAddDisk(){ + QString pool = ui->combo_pools->currentText(); + //Get the available disks and remove the current disks + QStringList adisks = LPGUtils::listAvailableHardDisks(); + for(int i=0; itext(); + QString pool = ui->combo_pools->currentText(); + //Verify action + if(QMessageBox::Yes != QMessageBox::question(this,tr("Verify Disk Removal"),QString(tr("Are you sure that you want to remove %1 from %2?")).arg(disk,pool) + "\n\n" + tr("CAUTION: This disk can only be re-attached later as a brand new disk"), QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + return; //cancelled + } + qDebug() << "Remove Disk:" << disk << pool; + showWaitBox(tr("Detaching disk")); + bool ok = LPBackend::detachDisk(pool, disk); + hideWaitBox(); + if(ok){ + QMessageBox::information(this,tr("Disk Removal Success"),QString(tr("Success: %1 was removed from %2")).arg(disk, pool) ); + QTimer::singleShot(0,this,SLOT(updateTabs()) ); + }else{ + QMessageBox::warning(this,tr("Disk Removal Failure"),QString(tr("Failure: %1 could not be removed from %2 at this time.")).arg(disk, pool) ); + } +} + +void LPMain::menuOfflineDisk(QAction *act){ + QString disk = act->text(); + QString pool = ui->combo_pools->currentText(); + //Verify action + if(QMessageBox::Yes != QMessageBox::question(this,tr("Verify Disk Offline"),QString(tr("Are you sure you wish to set %1 offline?")).arg(disk), QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + return; //cancelled + } + qDebug() << "Offline Disk:" << disk << pool; + showWaitBox(tr("Setting disk offline")); + bool ok = LPBackend::setDiskOffline(pool, disk); + hideWaitBox(); + if(ok){ + QMessageBox::information(this,tr("Disk Offline Success"),QString(tr("Success: %1 has been taken offline.")).arg(disk) ); + QTimer::singleShot(0,this,SLOT(updateTabs()) ); + }else{ + QMessageBox::warning(this,tr("Disk Offline Failure"),QString(tr("Failure: %1 could not be taken offline at this time.")).arg(disk) ); + } +} + +void LPMain::menuOnlineDisk(QAction *act){ + QString disk = act->text(); + QString pool = ui->combo_pools->currentText(); + //Verify action + if(QMessageBox::Yes != QMessageBox::question(this,tr("Verify Disk Online"),QString(tr("Are you sure you wish to set %1 online?")).arg(disk), QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + return; //cancelled + } + qDebug() << "Online Disk:" << disk << pool; + showWaitBox(tr("Setting disk online")); + bool ok = LPBackend::setDiskOnline(pool, disk); + hideWaitBox(); + if(ok){ + QMessageBox::information(this,tr("Disk Online Success"),QString(tr("Success: %1 has been set online.")).arg(disk) ); + QTimer::singleShot(0,this,SLOT(updateTabs()) ); + }else{ + QMessageBox::warning(this,tr("Disk Online Failure"),QString(tr("Failure: %1 could not be set online at this time.")).arg(disk) ); + } +} + +void LPMain::menuStartScrub(){ + QString pool = ui->combo_pools->currentText(); + //Verify starting a scrub + if( QMessageBox::Yes != QMessageBox::question(this,tr("Verify Scrub"),QString(tr("Are you sure you want to start a scrub on %1?")).arg(pool) + "\n"+tr("NOTE: This may take quite a while to complete"), QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + return; //cancelled + } + qDebug() << "Start Scrub:" << pool; + QString cmd = "zpool scrub "+pool; + showWaitBox(tr("Trying to start a scrub")); + int ret = system(cmd.toUtf8()); + hideWaitBox(); + if(ret == 0){ + //Now let te user know that one has been triggered + QMessageBox::information(this,tr("Scrub Started"),QString(tr("A scrub has just been started on %1")).arg(pool)); + QTimer::singleShot(0,this,SLOT(updateTabs()) ); + }else{ + QMessageBox::warning(this,tr("Scrub Not Started"), QString(tr("A scrub on %1 could not be started at this time.")).arg(pool) + "\n"+tr("Please wait until any current resilvering or scrubs are finished before trying again.") ); + } +} + +void LPMain::menuStopScrub(){ + QString pool = ui->combo_pools->currentText(); + //Verify stopping a scrub + if( QMessageBox::Yes != QMessageBox::question(this,tr("Verify Scrub"),QString(tr("Are you sure you want to stop the scrub on %1?")).arg(pool), QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + return; //cancelled + } + qDebug() << "Stop Scrub:" << pool; + QString cmd = "zpool scrub -s "+pool; + showWaitBox(tr("Trying to stop scrub")); + int ret = system(cmd.toUtf8()); + hideWaitBox(); + if(ret == 0){ + //Now let te user know that one has been triggered + QMessageBox::information(this,tr("Scrub Stopped"),QString(tr("The scrub on %1 has been stopped.")).arg(pool)); + QTimer::singleShot(0,this,SLOT(updateTabs()) ); + }else{ + QMessageBox::warning(this,tr("Scrub Not Running"), QString(tr("There was no scrub running on %1.")).arg(pool) ); + } +} + +// ==== Snapshots Menu ==== +void LPMain::menuNewSnapshot(){ + qDebug() << "New Snapshot"; + QString ds = ui->combo_pools->currentText(); + if(ds.isEmpty()){return; } + //Get the new snapshot name from the user + bool ok; + QString name = QInputDialog::getText(this,tr("New Snapshot Name"), tr("Snapshot Name:"), QLineEdit::Normal, tr("Name"), &ok, 0, Qt::ImhUppercaseOnly | Qt::ImhLowercaseOnly | Qt::ImhDigitsOnly ); + if(!ok || name.isEmpty()){ return; } //cancelled + qDebug() << "Creating a new snapshot:" << ds << name; + //Now create the new snapshot + LPBackend::newSnapshot(ds,name); + QMessageBox::information(this,tr("Snapshot Pending"), tr("The new snapshot creation has been added to the queue")); + updateTabs(); +} + +void LPMain::menuRemoveSnapshot(QAction *act){ + QString snapshot = act->text(); + QString pool = ui->combo_pools->currentText(); + qDebug() << "Remove Snapshot:" << snapshot; + //verify snapshot removal + if( QMessageBox::Yes == QMessageBox::question(this,tr("Verify Snapshot Deletion"),QString(tr("Do you wish to delete this snapshot? %1")).arg(pool+"/"+snapshot)+"\n"+tr("WARNING: This is a permanant change that cannot be reversed"),QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ + bool ok = LPBackend::removeSnapshot(ui->combo_pools->currentText(), snapshot); + if(ok){ + QMessageBox::information(this,tr("Snapshot Removed"),tr("The snapshot was successfully deleted")); + }else{ + QMessageBox::information(this,tr("Snapshot Removal Failure"),tr("The snapshot removal experienced an error and it not be completed at this time.")); + } + updateTabs(); + } +} diff --git a/src-qt4/life-preserver/lp-gui/LPMain.h b/src-qt4/life-preserver/lp-gui/LPMain.h new file mode 100644 index 000000000..e220ce59d --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/LPMain.h @@ -0,0 +1,84 @@ +#ifndef _LP_MAIN_H +#define _LP_MAIN_H + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include "LPBackend.h" +#include "LPContainers.h" +#include "LPGUtils.h" +#include "LPWizard.h" +#include "LPConfig.h" + +namespace Ui{ + class LPMain; +}; + +class LPMain : public QMainWindow{ + Q_OBJECT +public: + LPMain(QWidget *parent = 0); + ~LPMain(); + +public slots: + void slotSingleInstance(); + +private: + Ui::LPMain *ui; + QRadioButton *viewBasic, *viewAdvanced; + QFileSystemModel *fsModel; + bool poolSelected; + LPDataset POOLDATA; + QMessageBox *waitBox; + + void showErrorDialog(QString title, QString message, QString errors); + void showWaitBox(QString message); + void hideWaitBox(); + +private slots: + void updatePoolList(); //re-load available pools + void viewChanged(); + void updateTabs(); //load current pool info and update tabs + void updateDataset(); //restore dataset changed + void updateSnapshot(); //selected snapshot changed + void nextSnapshot(); + void prevSnapshot(); + void setFileVisibility(); + void restoreFiles(); + void openConfigGUI(); + // -- Menu Actions -- + //File Menu + void menuAddPool(QAction*); + void menuRemovePool(QAction*); + void menuSaveSSHKey(); + void menuCloseWindow(); + //Classic Backups + void menuCompressHomeDir(QAction*); + void menuExtractHomeDir(); + //Disk Menu + void menuAddDisk(); + void menuRemoveDisk(QAction*); + void menuOfflineDisk(QAction*); + void menuOnlineDisk(QAction*); + void menuStartScrub(); + void menuStopScrub(); + //Snapshots Menu + void menuNewSnapshot(); + void menuRemoveSnapshot(QAction*); + +protected: + +}; + +#endif diff --git a/src-qt4/life-preserver/LPMain.ui b/src-qt4/life-preserver/lp-gui/LPMain.ui similarity index 68% rename from src-qt4/life-preserver/LPMain.ui rename to src-qt4/life-preserver/lp-gui/LPMain.ui index 62a24dae7..3a86dcc1a 100644 --- a/src-qt4/life-preserver/LPMain.ui +++ b/src-qt4/life-preserver/lp-gui/LPMain.ui @@ -6,17 +6,35 @@ 0 0 - 377 - 245 + 459 + 396 Life Preserver + + + :/images/tray-icon-idle.png:/images/tray-icon-idle.png + + + + + Refresh the UI + + + ... + + + + :/images/refresh.png:/images/refresh.png + + + @@ -25,6 +43,9 @@ 0 + + QComboBox::AdjustToContentsOnFirstShow + @@ -44,9 +65,9 @@ - + - Configure the local snapshot policies + Configure snapshot and replication schedules Configure @@ -57,20 +78,6 @@ - - - - Configure additional data safety procedures - - - ... - - - - :/images/drive-removable-media.png:/images/drive-removable-media.png - - - @@ -79,6 +86,10 @@ 0 + + + :/images/drive-removable-media.png:/images/drive-removable-media.png + Status @@ -147,22 +158,6 @@ - - - - Qt::Vertical - - - QSizePolicy::Expanding - - - - 20 - 40 - - - - @@ -171,7 +166,7 @@ - + @@ -179,7 +174,7 @@ background-color: rgba(10,200,10,100); border-radius: 5px - Replication Status + Finished Status Qt::AlignCenter @@ -190,12 +185,12 @@ - + background-color: rgba(10,100,200,100); border-radius: 5px - Mirror Status + Running Status Qt::AlignCenter @@ -206,7 +201,7 @@ - + background-color: rgba(230,10,10,100); border-radius: 5px @@ -221,9 +216,29 @@ + + + + Qt::Vertical + + + QSizePolicy::Expanding + + + + 20 + 40 + + + + + + + :/images/copy.png:/images/copy.png + Restore Data @@ -238,30 +253,24 @@ - + Select the previous (older) snapshot - - - - Prev + :/images/previous.png:/images/previous.png - - - 16 - 16 - - + + 0 + @@ -288,12 +297,12 @@ - + Select the next (more recent) snapshot - Next + @@ -303,19 +312,6 @@ - - - - Qt::Vertical - - - - 20 - 40 - - - - @@ -323,19 +319,18 @@ + + + - + - Browse through the currently selected snapshot + Display any hidden files/folders - View Snapshot - - - - :/images/view.png:/images/view.png + Show Hidden Files @@ -353,37 +348,17 @@ - + - Revert the entire directory to the selected snapshot + Restore the selected file/folder to the live system. - Restore Dir - - - - :/images/folder.png:/images/folder.png - - - Qt::ToolButtonTextBesideIcon - - - - - - - Retrieve file(s) from the selected snapshot - - - Restore File + Restore :/images/copy.png:/images/copy.png - - Qt::ToolButtonTextBesideIcon - @@ -391,8 +366,8 @@ - verticalSpacer_2 line_2 + treeView @@ -403,7 +378,7 @@ 0 0 - 377 + 459 20 @@ -411,12 +386,32 @@ File - - + + + Manage Pool + + + + :/images/list-add.png:/images/list-add.png + + + + + + Unmanage Pool + + + + :/images/list-remove.png:/images/list-remove.png + + + + + - + @@ -427,27 +422,87 @@ Disks + + + Detach Disk + + + + :/images/list-remove.png:/images/list-remove.png + + + + + + Set Disk Offline + + + + :/images/network-wired-red.png:/images/network-wired-red.png + + + + + + Set Disk Online + + + + :/images/network-wired.png:/images/network-wired.png + + + - + - + + + Snapshots + + + Delete Snapshot + + + + :/images/list-remove.png:/images/list-remove.png + + + - + + + + + Classic Backups + + + + Compress Home Dir + + + + :/images/box_add.png:/images/box_add.png + + + + + - + + - + :/images/application-exit.png:/images/application-exit.png @@ -466,24 +521,6 @@ Basic - - - - :/images/list-add.png:/images/list-add.png - - - Manage Pool - - - - - - :/images/list-remove.png:/images/list-remove.png - - - Unmanage Pool - - Recover File @@ -505,69 +542,108 @@ :/images/list-add.png:/images/list-add.png - Add Disk + Attach Disk + + + + + New Snapshot - + - :/images/list-remove.png:/images/list-remove.png + :/images/camera_add.png:/images/camera_add.png - Remove Disk + New Snapshot - + - :/images/network-wired.png:/images/network-wired.png + :/images/key.png:/images/key.png - Set Disk Offline + Save Key to USB - + + + + :/images/system-run.png:/images/system-run.png + - New Snapshot + Start Scrub + + + Check system data integrity - + - :/images/camera_add.png:/images/camera_add.png + :/images/drive-removable-media.png:/images/drive-removable-media.png - New Snapshot + Classic Backup - + - :/images/list-remove.png:/images/list-remove.png + :/images/box_extract.png:/images/box_extract.png - Delete Snapshot + Extract Home Dir - + + + pools + + + + + pools + + + + + snapshots + + + + + user + + + + + disks + + + - :/images/key.png:/images/key.png + :/images/network-wired-red.png:/images/network-wired-red.png - Save Key to USB + disks - + + + disk + + + - :/images/system-run.png:/images/system-run.png + :/images/application-exit.png:/images/application-exit.png - Start Scrub - - - Check system data integrity + Stop Scrub diff --git a/src-qt4/life-preserver/LPWizard.cpp b/src-qt4/life-preserver/lp-gui/LPWizard.cpp similarity index 100% rename from src-qt4/life-preserver/LPWizard.cpp rename to src-qt4/life-preserver/lp-gui/LPWizard.cpp diff --git a/src-qt4/life-preserver/LPWizard.h b/src-qt4/life-preserver/lp-gui/LPWizard.h similarity index 100% rename from src-qt4/life-preserver/LPWizard.h rename to src-qt4/life-preserver/lp-gui/LPWizard.h diff --git a/src-qt4/life-preserver/LPWizard.ui b/src-qt4/life-preserver/lp-gui/LPWizard.ui similarity index 100% rename from src-qt4/life-preserver/LPWizard.ui rename to src-qt4/life-preserver/lp-gui/LPWizard.ui diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_af.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_af.ts new file mode 100644 index 000000000..ea7376617 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_af.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ar.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ar.ts new file mode 100644 index 000000000..1fe4fe381 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ar.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_az.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_az.ts new file mode 100644 index 000000000..89e6623e7 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_az.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bg.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bg.ts new file mode 100644 index 000000000..6b634838f --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bg.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bn.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bn.ts new file mode 100644 index 000000000..9d88e5458 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bn.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bs.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bs.ts new file mode 100644 index 000000000..e3254b3ad --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_bs.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ca.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ca.ts new file mode 100644 index 000000000..c2ee305ed --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ca.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_cs.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_cs.ts new file mode 100644 index 000000000..45bd85ed8 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_cs.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_cy.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_cy.ts new file mode 100644 index 000000000..28cdd3c24 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_cy.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_da.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_da.ts new file mode 100644 index 000000000..170d55413 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_da.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_de.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_de.ts new file mode 100644 index 000000000..6c32e89b3 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_de.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_el.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_el.ts new file mode 100644 index 000000000..3949e4815 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_el.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_GB.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_GB.ts new file mode 100644 index 000000000..ad663f2f0 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_GB.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_US.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_US.ts new file mode 100644 index 000000000..d0ca95ed9 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_US.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_ZA.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_ZA.ts new file mode 100644 index 000000000..db98ed43a --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_en_ZA.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_es.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_es.ts new file mode 100644 index 000000000..038b7cfec --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_es.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_et.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_et.ts new file mode 100644 index 000000000..b11cd97e5 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_et.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_eu.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_eu.ts new file mode 100644 index 000000000..d9802ced1 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_eu.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fa.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fa.ts new file mode 100644 index 000000000..187fa28e7 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fa.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fi.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fi.ts new file mode 100644 index 000000000..4d4817db2 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fi.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fr.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fr.ts new file mode 100644 index 000000000..256f92d95 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fr.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fr_CA.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fr_CA.ts new file mode 100644 index 000000000..d240aa55b --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fr_CA.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fur.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fur.ts new file mode 100644 index 000000000..f370f072c --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_fur.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_gl.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_gl.ts new file mode 100644 index 000000000..cae3586f8 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_gl.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_he.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_he.ts new file mode 100644 index 000000000..beb7e2484 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_he.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hi.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hi.ts new file mode 100644 index 000000000..37089c53b --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hi.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hr.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hr.ts new file mode 100644 index 000000000..09da9242a --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hr.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hu.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hu.ts new file mode 100644 index 000000000..c2cb2613a --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_hu.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_id.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_id.ts new file mode 100644 index 000000000..238ac54b4 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_id.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_is.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_is.ts new file mode 100644 index 000000000..3897d1d1a --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_is.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_it.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_it.ts new file mode 100644 index 000000000..5fc31f551 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_it.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ja.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ja.ts new file mode 100644 index 000000000..b4eea9743 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ja.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ka.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ka.ts new file mode 100644 index 000000000..17a4824bd --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ka.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ko.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ko.ts new file mode 100644 index 000000000..d5aba911a --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ko.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_lt.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_lt.ts new file mode 100644 index 000000000..a39abd7bf --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_lt.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_lv.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_lv.ts new file mode 100644 index 000000000..7a03c2211 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_lv.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mk.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mk.ts new file mode 100644 index 000000000..611105a2f --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mk.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mn.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mn.ts new file mode 100644 index 000000000..22b8e3d63 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mn.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ms.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ms.ts new file mode 100644 index 000000000..47c6d4bb7 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ms.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mt.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mt.ts new file mode 100644 index 000000000..65f44e22d --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_mt.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_nb.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_nb.ts new file mode 100644 index 000000000..4fb86d20c --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_nb.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ne.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ne.ts new file mode 100644 index 000000000..2c34f364c --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ne.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_nl.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_nl.ts new file mode 100644 index 000000000..6f0dbd700 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_nl.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pa.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pa.ts new file mode 100644 index 000000000..f7323c87a --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pa.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pl.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pl.ts new file mode 100644 index 000000000..9b4cfc408 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pl.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pt.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pt.ts new file mode 100644 index 000000000..fbcd107fb --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pt.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pt_BR.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pt_BR.ts new file mode 100644 index 000000000..5cdc2c85c --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_pt_BR.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ro.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ro.ts new file mode 100644 index 000000000..04487a712 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ro.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ru.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ru.ts new file mode 100644 index 000000000..c9079614a --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ru.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sa.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sa.ts new file mode 100644 index 000000000..bb5bd32bf --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sa.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sk.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sk.ts new file mode 100644 index 000000000..968c1f93f --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sk.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sl.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sl.ts new file mode 100644 index 000000000..125dc62b0 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sl.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sr.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sr.ts new file mode 100644 index 000000000..ddedf6338 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sr.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sv.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sv.ts new file mode 100644 index 000000000..dc3606361 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sv.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sw.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sw.ts new file mode 100644 index 000000000..a581ff19b --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_sw.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ta.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ta.ts new file mode 100644 index 000000000..ebcdb1bf1 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_ta.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_tg.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_tg.ts new file mode 100644 index 000000000..0e30670fc --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_tg.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_th.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_th.ts new file mode 100644 index 000000000..1a909c4be --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_th.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_tr.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_tr.ts new file mode 100644 index 000000000..632af966d --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_tr.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_uk.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_uk.ts new file mode 100644 index 000000000..fabb1fc0b --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_uk.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_uz.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_uz.ts new file mode 100644 index 000000000..df4c7e5aa --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_uz.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_vi.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_vi.ts new file mode 100644 index 000000000..0b638d9c7 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_vi.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_CN.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_CN.ts new file mode 100644 index 000000000..033cd451e --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_CN.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_HK.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_HK.ts new file mode 100644 index 000000000..c1adf014b --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_HK.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_TW.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_TW.ts new file mode 100644 index 000000000..985426852 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zh_TW.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zu.ts b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zu.ts new file mode 100644 index 000000000..338e75221 --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/i18n/LifePreserver_zu.ts @@ -0,0 +1,439 @@ + + + + + LPConfig + + + Configure Dataset + + + + + Data Set: + + + + + Local Snapshots + + + + + Schedule: + + + + + Daily + + + + + Hourly + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + @ h AP + + + + + Days + + + + + Total + + + + + Keep: + + + + + Replication + + + + + Replicate on a Remote System + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + h AP + + + + + Apply + + + + + Cancel + + + + + LPMain + + + Life Preserver + + + + + Configure local data backup schedules + + + + + Configure + + + + + Configure off-disk data backup solutions + + + + + Backups + + + + + Status + + + + + System State: + + + + + Number of Disks: + + + + + Latest Snapshot: + + + + + Restore Data + + + + + Restore + + + + + File + + + + + View + + + + + Disks + + + + + Snapshots + + + + + Close Window + + + + + + Advanced + + + + + + Basic + + + + + Manage Pool + + + + + Unmanage Pool + + + + + Recover File + + + + + Restore Dataset + + + + + + Save Key to USB + + + + + Add Disk + + + + + Remove Disk + + + + + Set Disk Offline + + + + + + New Snapshot + + + + + Delete Snapshot + + + + + Start Scrub + + + + + Check system data integrity + + + + + Classic Backup + + + + + No datasets available + + + + + LPWizard + + + New Life Preserver + + + + + This wizard will walk you through the process of setting up a new snapshot schedule for the following ZFS dataset: + + + + + Snapshot schedule + + + + + Snapshots can be scheduled anywhere from daily, down to every 5 minutes. Snapshots consume very little disk space, and will only grow as the current data on disk changes. + + + + + Hourly + + + + + Daily @ + + + + + + h AP + + + + + 30 minutes + + + + + 10 minutes + + + + + 5 minutes + + + + + Snapshot pruning + + + + + <html><head/><body><p>The oldest snapshots will be auto-pruned after reaching either the number of days or the total number of snapshots that you specify. </p></body></html> + + + + + + Keep + + + + + days worth of snapshots + + + + + total snapshots + + + + + Replication Server + + + + + Replication will keep a copy of your data on a remote system in the case of a total disk failure. + + + + + NOTE: A valid replication target system must be running a compatible version of ZFS and have SSH enabled, such as on a FreeNAS system. + + + + + Replicate my data + + + + + Frequency + + + + + With snapshot creation (Best for daily snapshots) + + + + + Daily at: + + + + + Host Name + + + + + User Name + + + + + SSH Port + + + + + Remote Dataset + + + + + <html><head/><body><p>Your new Life Preserver schedule is now set up! You may go back and change your configuration at any time from within the main Life Preserver window.</p><p><br/></p><p>Click the Finish button to apply these settings and create the new backup schedule.</p></body></html> + + + + diff --git a/src-qt4/life-preserver/images/.directory b/src-qt4/life-preserver/lp-gui/images/.directory similarity index 100% rename from src-qt4/life-preserver/images/.directory rename to src-qt4/life-preserver/lp-gui/images/.directory diff --git a/src-qt4/life-preserver/images/application-exit.png b/src-qt4/life-preserver/lp-gui/images/application-exit.png similarity index 100% rename from src-qt4/life-preserver/images/application-exit.png rename to src-qt4/life-preserver/lp-gui/images/application-exit.png diff --git a/src-qt4/life-preserver/images/backup-failed.png b/src-qt4/life-preserver/lp-gui/images/backup-failed.png similarity index 100% rename from src-qt4/life-preserver/images/backup-failed.png rename to src-qt4/life-preserver/lp-gui/images/backup-failed.png diff --git a/src-qt4/life-preserver/images/backup-ok.png b/src-qt4/life-preserver/lp-gui/images/backup-ok.png similarity index 100% rename from src-qt4/life-preserver/images/backup-ok.png rename to src-qt4/life-preserver/lp-gui/images/backup-ok.png diff --git a/src-qt4/life-preserver/lp-gui/images/box_add.png b/src-qt4/life-preserver/lp-gui/images/box_add.png new file mode 100644 index 000000000..4ae9cdd1a Binary files /dev/null and b/src-qt4/life-preserver/lp-gui/images/box_add.png differ diff --git a/src-qt4/life-preserver/lp-gui/images/box_extract.png b/src-qt4/life-preserver/lp-gui/images/box_extract.png new file mode 100644 index 000000000..5b45fb64b Binary files /dev/null and b/src-qt4/life-preserver/lp-gui/images/box_extract.png differ diff --git a/src-qt4/life-preserver/images/camera_add.png b/src-qt4/life-preserver/lp-gui/images/camera_add.png similarity index 100% rename from src-qt4/life-preserver/images/camera_add.png rename to src-qt4/life-preserver/lp-gui/images/camera_add.png diff --git a/src-qt4/life-preserver/images/configure.png b/src-qt4/life-preserver/lp-gui/images/configure.png similarity index 100% rename from src-qt4/life-preserver/images/configure.png rename to src-qt4/life-preserver/lp-gui/images/configure.png diff --git a/src-qt4/life-preserver/images/copy.png b/src-qt4/life-preserver/lp-gui/images/copy.png similarity index 100% rename from src-qt4/life-preserver/images/copy.png rename to src-qt4/life-preserver/lp-gui/images/copy.png diff --git a/src-qt4/life-preserver/images/drive-removable-media.png b/src-qt4/life-preserver/lp-gui/images/drive-removable-media.png similarity index 100% rename from src-qt4/life-preserver/images/drive-removable-media.png rename to src-qt4/life-preserver/lp-gui/images/drive-removable-media.png diff --git a/src-qt4/life-preserver/images/folder.png b/src-qt4/life-preserver/lp-gui/images/folder.png similarity index 100% rename from src-qt4/life-preserver/images/folder.png rename to src-qt4/life-preserver/lp-gui/images/folder.png diff --git a/src-qt4/life-preserver/images/key.png b/src-qt4/life-preserver/lp-gui/images/key.png similarity index 100% rename from src-qt4/life-preserver/images/key.png rename to src-qt4/life-preserver/lp-gui/images/key.png diff --git a/src-qt4/life-preserver/images/lifepreserver.png b/src-qt4/life-preserver/lp-gui/images/lifepreserver.png similarity index 100% rename from src-qt4/life-preserver/images/lifepreserver.png rename to src-qt4/life-preserver/lp-gui/images/lifepreserver.png diff --git a/src-qt4/life-preserver/images/list-add.png b/src-qt4/life-preserver/lp-gui/images/list-add.png similarity index 100% rename from src-qt4/life-preserver/images/list-add.png rename to src-qt4/life-preserver/lp-gui/images/list-add.png diff --git a/src-qt4/life-preserver/images/list-remove.png b/src-qt4/life-preserver/lp-gui/images/list-remove.png similarity index 100% rename from src-qt4/life-preserver/images/list-remove.png rename to src-qt4/life-preserver/lp-gui/images/list-remove.png diff --git a/src-qt4/life-preserver/lp-gui/images/network-wired-red.png b/src-qt4/life-preserver/lp-gui/images/network-wired-red.png new file mode 100644 index 000000000..f210e6015 Binary files /dev/null and b/src-qt4/life-preserver/lp-gui/images/network-wired-red.png differ diff --git a/src-qt4/life-preserver/images/network-wired.png b/src-qt4/life-preserver/lp-gui/images/network-wired.png similarity index 100% rename from src-qt4/life-preserver/images/network-wired.png rename to src-qt4/life-preserver/lp-gui/images/network-wired.png diff --git a/src-qt4/life-preserver/images/next.png b/src-qt4/life-preserver/lp-gui/images/next.png similarity index 100% rename from src-qt4/life-preserver/images/next.png rename to src-qt4/life-preserver/lp-gui/images/next.png diff --git a/src-qt4/life-preserver/images/previous.png b/src-qt4/life-preserver/lp-gui/images/previous.png similarity index 100% rename from src-qt4/life-preserver/images/previous.png rename to src-qt4/life-preserver/lp-gui/images/previous.png diff --git a/src-qt4/life-preserver/lp-gui/images/refresh.png b/src-qt4/life-preserver/lp-gui/images/refresh.png new file mode 100644 index 000000000..d07fd807c Binary files /dev/null and b/src-qt4/life-preserver/lp-gui/images/refresh.png differ diff --git a/src-qt4/life-preserver/images/system-run.png b/src-qt4/life-preserver/lp-gui/images/system-run.png similarity index 100% rename from src-qt4/life-preserver/images/system-run.png rename to src-qt4/life-preserver/lp-gui/images/system-run.png diff --git a/src-qt4/life-preserver/images/tray-icon-error.png b/src-qt4/life-preserver/lp-gui/images/tray-icon-error.png similarity index 100% rename from src-qt4/life-preserver/images/tray-icon-error.png rename to src-qt4/life-preserver/lp-gui/images/tray-icon-error.png diff --git a/src-qt4/life-preserver/images/tray-icon-failed.png b/src-qt4/life-preserver/lp-gui/images/tray-icon-failed.png similarity index 100% rename from src-qt4/life-preserver/images/tray-icon-failed.png rename to src-qt4/life-preserver/lp-gui/images/tray-icon-failed.png diff --git a/src-qt4/life-preserver/images/tray-icon-idle.png b/src-qt4/life-preserver/lp-gui/images/tray-icon-idle.png similarity index 100% rename from src-qt4/life-preserver/images/tray-icon-idle.png rename to src-qt4/life-preserver/lp-gui/images/tray-icon-idle.png diff --git a/src-qt4/life-preserver/images/tray-icon-working.png b/src-qt4/life-preserver/lp-gui/images/tray-icon-working.png similarity index 100% rename from src-qt4/life-preserver/images/tray-icon-working.png rename to src-qt4/life-preserver/lp-gui/images/tray-icon-working.png diff --git a/src-qt4/life-preserver/images/upload.png b/src-qt4/life-preserver/lp-gui/images/upload.png similarity index 100% rename from src-qt4/life-preserver/images/upload.png rename to src-qt4/life-preserver/lp-gui/images/upload.png diff --git a/src-qt4/life-preserver/images/view.png b/src-qt4/life-preserver/lp-gui/images/view.png similarity index 100% rename from src-qt4/life-preserver/images/view.png rename to src-qt4/life-preserver/lp-gui/images/view.png diff --git a/src-qt4/life-preserver/lPreserve.qrc b/src-qt4/life-preserver/lp-gui/lPreserve.qrc similarity index 52% rename from src-qt4/life-preserver/lPreserve.qrc rename to src-qt4/life-preserver/lp-gui/lPreserve.qrc index 0084724ec..ccc84bd7e 100644 --- a/src-qt4/life-preserver/lPreserve.qrc +++ b/src-qt4/life-preserver/lp-gui/lPreserve.qrc @@ -1,5 +1,9 @@ + images/network-wired-red.png + images/refresh.png + images/box_add.png + images/box_extract.png images/tray-icon-error.png images/tray-icon-working.png images/next.png @@ -21,22 +25,5 @@ images/list-remove.png images/system-run.png images/tray-icon-idle.png - images/tray-icon-active1.png - images/tray-icon-active2.png - images/tray-icon-active3.png - images/tray-icon-active4.png - images/tray-icon-active5.png - images/tray-icon-active6.png - images/tray-icon-active7.png - images/tray-icon-active8.png - images/tray-icon-active9.png - images/tray-icon-active10.png - images/tray-icon-active11.png - images/tray-icon-active12.png - images/tray-icon-active13.png - images/tray-icon-active14.png - images/tray-icon-active15.png - images/tray-icon-active16.png - images/tray-icon-failed.png diff --git a/src-qt4/life-preserver/lp-gui/life-preserver.pro b/src-qt4/life-preserver/lp-gui/life-preserver.pro new file mode 100644 index 000000000..5d656ca4f --- /dev/null +++ b/src-qt4/life-preserver/lp-gui/life-preserver.pro @@ -0,0 +1,105 @@ +TEMPLATE = app +LANGUAGE = C++ +LIBS += -lQtSolutions_SingleApplication-head + +CONFIG += qt warn_on release + +HEADERS += LPBackend.h \ + LPWizard.h \ + LPContainers.h \ + LPConfig.h \ + LPMain.h \ + LPGUtils.h + +SOURCES += main.cpp \ + LPBackend.cpp \ + LPWizard.cpp \ + LPConfig.cpp \ + LPMain.cpp \ + LPGUtils.cpp + +RESOURCES += lPreserve.qrc + +FORMS = LPWizard.ui \ + LPConfig.ui \ + LPMain.ui + +TARGET=life-preserver +target.path=/usr/local/bin + +scripts.path=/usr/local/share/lifePreserver/scripts +scripts.files=scripts/setup-ssh-keys.sh + +dotrans.path=/usr/local/share/lifePreserver/i18n/ +dotrans.extra=cd i18n && lrelease-qt4 -nounfinished *.ts && cp *.qm $(INSTALL_ROOT)/usr/local/share/lifePreserver/i18n/ + +INSTALLS += target dotrans scripts + +TRANSLATIONS = i18n/LifePreserver_af.ts \ + i18n/LifePreserver_ar.ts \ + i18n/LifePreserver_az.ts \ + i18n/LifePreserver_bg.ts \ + i18n/LifePreserver_bn.ts \ + i18n/LifePreserver_bs.ts \ + i18n/LifePreserver_ca.ts \ + i18n/LifePreserver_cs.ts \ + i18n/LifePreserver_cy.ts \ + i18n/LifePreserver_da.ts \ + i18n/LifePreserver_de.ts \ + i18n/LifePreserver_el.ts \ + i18n/LifePreserver_en_US.ts \ + i18n/LifePreserver_en_GB.ts \ + i18n/LifePreserver_en_ZA.ts \ + i18n/LifePreserver_es.ts \ + i18n/LifePreserver_et.ts \ + i18n/LifePreserver_eu.ts \ + i18n/LifePreserver_fa.ts \ + i18n/LifePreserver_fi.ts \ + i18n/LifePreserver_fr.ts \ + i18n/LifePreserver_fr_CA.ts \ + i18n/LifePreserver_fur.ts \ + i18n/LifePreserver_gl.ts \ + i18n/LifePreserver_he.ts \ + i18n/LifePreserver_hi.ts \ + i18n/LifePreserver_hr.ts \ + i18n/LifePreserver_hu.ts \ + i18n/LifePreserver_id.ts \ + i18n/LifePreserver_is.ts \ + i18n/LifePreserver_it.ts \ + i18n/LifePreserver_ja.ts \ + i18n/LifePreserver_ka.ts \ + i18n/LifePreserver_ko.ts \ + i18n/LifePreserver_lt.ts \ + i18n/LifePreserver_lv.ts \ + i18n/LifePreserver_mk.ts \ + i18n/LifePreserver_mn.ts \ + i18n/LifePreserver_ms.ts \ + i18n/LifePreserver_mt.ts \ + i18n/LifePreserver_nb.ts \ + i18n/LifePreserver_ne.ts \ + i18n/LifePreserver_nl.ts \ + i18n/LifePreserver_pa.ts \ + i18n/LifePreserver_pl.ts \ + i18n/LifePreserver_pt.ts \ + i18n/LifePreserver_pt_BR.ts \ + i18n/LifePreserver_ro.ts \ + i18n/LifePreserver_ru.ts \ + i18n/LifePreserver_sa.ts \ + i18n/LifePreserver_sk.ts \ + i18n/LifePreserver_sl.ts \ + i18n/LifePreserver_sr.ts \ + i18n/LifePreserver_sv.ts \ + i18n/LifePreserver_sw.ts \ + i18n/LifePreserver_ta.ts \ + i18n/LifePreserver_tg.ts \ + i18n/LifePreserver_th.ts \ + i18n/LifePreserver_tr.ts \ + i18n/LifePreserver_uk.ts \ + i18n/LifePreserver_uz.ts \ + i18n/LifePreserver_vi.ts \ + i18n/LifePreserver_zh_CN.ts \ + i18n/LifePreserver_zh_HK.ts \ + i18n/LifePreserver_zh_TW.ts \ + i18n/LifePreserver_zu.ts + +QMAKE_LIBDIR = /usr/local/lib/qt4 /usr/local/lib diff --git a/src-qt4/life-preserver/main.cpp b/src-qt4/life-preserver/lp-gui/main.cpp similarity index 95% rename from src-qt4/life-preserver/main.cpp rename to src-qt4/life-preserver/lp-gui/main.cpp index 85d1287b9..7393ba780 100644 --- a/src-qt4/life-preserver/main.cpp +++ b/src-qt4/life-preserver/lp-gui/main.cpp @@ -6,7 +6,7 @@ #include #include -#include "LPTray.h" +#include "LPMain.h" //#include "../config.h" #ifndef PREFIX @@ -34,7 +34,7 @@ int main( int argc, char ** argv ) a.installTranslator( &translator ); qDebug() << "Locale:" << langCode; - LPTray *w = new LPTray(); + LPMain *w = new LPMain(); w->show(); QObject::connect( &a, SIGNAL( messageReceived(const QString &) ), w, SLOT( slotSingleInstance() ) ); diff --git a/src-qt4/life-preserver/scripts/setup-ssh-keys.sh b/src-qt4/life-preserver/lp-gui/scripts/setup-ssh-keys.sh similarity index 100% rename from src-qt4/life-preserver/scripts/setup-ssh-keys.sh rename to src-qt4/life-preserver/lp-gui/scripts/setup-ssh-keys.sh diff --git a/src-qt4/life-preserver/LPMessages.cpp b/src-qt4/life-preserver/lp-tray/LPMessages.cpp similarity index 88% rename from src-qt4/life-preserver/LPMessages.cpp rename to src-qt4/life-preserver/lp-tray/LPMessages.cpp index 3badf0a3d..e838f80f9 100644 --- a/src-qt4/life-preserver/LPMessages.cpp +++ b/src-qt4/life-preserver/lp-tray/LPMessages.cpp @@ -15,16 +15,20 @@ LPMessages::~LPMessages(){ // ------------------------------ // PUBLIC FUNCTIONS // ------------------------------ -void LPMessages::setMessages(QString msg){ - if(msg.isEmpty()){ msg = tr("No recent messages"); } - ui->label_messages->setText(msg); - //Make sure that the messages tab is visible - ui->tabWidget->setCurrentWidget(ui->tab_messages); -} - -void LPMessages::setErrors(QString err){ +void LPMessages::setMessages(QString msg, QString err){ + //standard messages + if(msg.isEmpty()){ ui->label_messages->setText(tr("No recent messages")); } + else{ ui->label_messages->setText(msg); } + //error messages ui->label_errors->setText(err); + if(msg.isEmpty() && !err.isEmpty()){ + ui->label_messages->setVisible(false); + }else{ + ui->label_messages->setVisible(true); + } ui->label_errors->setVisible( !err.isEmpty() ); + //Make sure that the messages tab is visible + ui->tabWidget->setCurrentWidget(ui->tab_messages); } void LPMessages::setLogFiles(QStringList logs){ diff --git a/src-qt4/life-preserver/LPMessages.h b/src-qt4/life-preserver/lp-tray/LPMessages.h similarity index 90% rename from src-qt4/life-preserver/LPMessages.h rename to src-qt4/life-preserver/lp-tray/LPMessages.h index 434a11a9e..a26f1a088 100644 --- a/src-qt4/life-preserver/LPMessages.h +++ b/src-qt4/life-preserver/lp-tray/LPMessages.h @@ -19,8 +19,7 @@ class LPMessages : public QDialog{ LPMessages(QWidget *parent=0); ~LPMessages(); - void setMessages(QString msg); - void setErrors(QString err); + void setMessages(QString msg, QString err); void setLogFiles(QStringList logs); private: diff --git a/src-qt4/life-preserver/LPMessages.ui b/src-qt4/life-preserver/lp-tray/LPMessages.ui similarity index 100% rename from src-qt4/life-preserver/LPMessages.ui rename to src-qt4/life-preserver/lp-tray/LPMessages.ui diff --git a/src-qt4/life-preserver/LPTray.cpp b/src-qt4/life-preserver/lp-tray/LPTray.cpp similarity index 82% rename from src-qt4/life-preserver/LPTray.cpp rename to src-qt4/life-preserver/lp-tray/LPTray.cpp index f9b79abd3..f51d364e1 100644 --- a/src-qt4/life-preserver/LPTray.cpp +++ b/src-qt4/life-preserver/lp-tray/LPTray.cpp @@ -8,15 +8,16 @@ LPTray::LPTray() : QSystemTrayIcon(){ connect(watcher,SIGNAL(StatusUpdated()),this,SLOT(watcherMessage()) ); //Setup the context menu menu = new QMenu; - menu->addAction(QIcon(":/images/backup-failed.png"),tr("View Messages"),this,SLOT(startMessageDialog()) ); menu->addAction(QIcon(":/images/tray-icon-idle.png"),tr("Start Application UI"),this,SLOT(startGUI()) ); menu->addSeparator(); + menu->addAction(QIcon(":/images/backup-failed.png"),tr("View Messages"),this,SLOT(startMessageDialog()) ); + menu->addAction(QIcon(":/images/refresh.png"),tr("Refresh Tray"),this,SLOT(refreshStatus()) ); + menu->addSeparator(); menu->addAction(QIcon(":/images/application-exit.png"),tr("Close Life Preserver Tray"),this,SLOT(slotClose()) ); this->setContextMenu(menu); //Setup initial icon for the tray this->setIcon( QIcon(":/images/tray-icon-idle.png") ); - //Create the configuration GUI - GUI = new mainUI(); + //Create the messages GUI msgdlg = new LPMessages(); //connect other signals/slots connect(this, SIGNAL(activated(QSystemTrayIcon::ActivationReason)), this, SLOT(slotTrayClicked(QSystemTrayIcon::ActivationReason)) ); @@ -29,7 +30,6 @@ LPTray::LPTray() : QSystemTrayIcon(){ LPTray::~LPTray(){ watcher->stop(); delete watcher; - delete GUI; delete msgdlg; } @@ -114,10 +114,7 @@ void LPTray::watcherMessage(QString type){ } void LPTray::slotTrayClicked(QSystemTrayIcon::ActivationReason reason){ - if(reason == QSystemTrayIcon::Trigger){ - if(GUI->isVisible()){ GUI->hide(); } - else{ startGUI(); } - }else if( reason == QSystemTrayIcon::Context){ + if(reason == QSystemTrayIcon::Trigger || reason == QSystemTrayIcon::Context){ this->contextMenu()->popup(QCursor::pos()); } } @@ -128,18 +125,15 @@ void LPTray::slotClose(){ void LPTray::slotSingleInstance(){ this->show(); - if(!GUI->isVisible()){ startGUI(); } - else{ - GUI->raise(); - GUI->show(); + if(msgdlg->isVisible()){ + msgdlg->raise(); + msgdlg->show(); } } void LPTray::startGUI(){ //Start up the GUI - GUI->setupUI(); - GUI->raise(); - GUI->show(); + system("pc-su life-preserver"); } void LPTray::startMessageDialog(){ @@ -151,19 +145,28 @@ void LPTray::startMessageDialog(){ for(int i=0; igetMessages(types[i], infoL); if(info.isEmpty()){continue;} - if(info[0] == "ERROR"){ - errs << info[1] + " (" + info[2] + "): " + info[3]; - }else if(!info[0].isEmpty()){ - msgs << info[1] + " (" + info[2] + "): " + info[3]; + //Take into account multiple devices/messages per type + QStringList devs=info[2].split(":::"); QStringList msgs=info[3].split(":::"); + for(int j=0; j" + //allow for multiple log files + logs << info[4].split(":::"); // In format: "example logfile " } } //Now start up the dialog - msgdlg->setMessages( msgs.join("\n") ); - msgdlg->setErrors( errs.join("\n") ); + msgdlg->setMessages( msgs.join("\n"), errs.join("\n") ); msgdlg->setLogFiles(logs); msgdlg->raise(); msgdlg->show(); } + +void LPTray::refreshStatus(){ + //Manually trigger the watcher to update status notifications + watcher->refresh(); +} diff --git a/src-qt4/life-preserver/LPTray.h b/src-qt4/life-preserver/lp-tray/LPTray.h similarity index 94% rename from src-qt4/life-preserver/LPTray.h rename to src-qt4/life-preserver/lp-tray/LPTray.h index 02ffb4338..dafae45a8 100644 --- a/src-qt4/life-preserver/LPTray.h +++ b/src-qt4/life-preserver/lp-tray/LPTray.h @@ -6,7 +6,6 @@ #include #include -#include "mainUI.h" #include "LPWatcher.h" #include "LPMessages.h" @@ -20,7 +19,6 @@ class LPTray : public QSystemTrayIcon{ LPWatcher *watcher; LPMessages *msgdlg; QMenu *menu; - mainUI *GUI; void updateTrayIcon(); void updateToolTip(); @@ -33,6 +31,7 @@ private slots: void slotSingleInstance(); void startGUI(); void startMessageDialog(); + void refreshStatus(); }; diff --git a/src-qt4/life-preserver/LPWatcher.cpp b/src-qt4/life-preserver/lp-tray/LPWatcher.cpp similarity index 82% rename from src-qt4/life-preserver/LPWatcher.cpp rename to src-qt4/life-preserver/lp-tray/LPWatcher.cpp index 1c92f95aa..8bdbbabb2 100644 --- a/src-qt4/life-preserver/LPWatcher.cpp +++ b/src-qt4/life-preserver/lp-tray/LPWatcher.cpp @@ -79,6 +79,10 @@ void LPWatcher::stop(){ timer->stop(); } +void LPWatcher::refresh(){ + QTimer::singleShot(1, this, SLOT(checkPoolStatus()) ); +} + QStringList LPWatcher::getMessages(QString type, QStringList msgList){ QStringList output; type = type.toLower(); @@ -142,6 +146,7 @@ bool LPWatcher::hasError(){ // PRIVATE FUNCTIONS // ------------------------------------- void LPWatcher::readLogFile(bool quiet){ + QStringList reppools = listReplicatedPools(); QTextStream in(logfile); while(!LFSTREAM->atEnd()){ QString log = LFSTREAM->readLine(); @@ -166,42 +171,73 @@ void LPWatcher::readLogFile(bool quiet){ //Setup the file watcher for this new log file FILE_REPLICATION = dev; dev = message.section(" ",5,5,QString::SectionSkipEmpty); - startRepFileWatcher(); - //Set the appropriate status variables - LOGS.insert(20,"STARTED"); - LOGS.insert(21, dev); //zpool - LOGS.insert(22, tr("Replication Starting") ); //summary - LOGS.insert(23, QString(tr("Starting replication for %1")).arg(dev) ); //Full message - LOGS.insert(24, timestamp); //full timestamp - LOGS.insert(25, time); // time only - LOGS.insert(26,tr("Replication Log")+" <"+FILE_REPLICATION+">"); //log file - if(!quiet){ emit MessageAvailable("replication"); } + //Make sure the device is currently setup for replication + if( !reppools.contains(dev) ){ FILE_REPLICATION.clear(); continue; } + //Try to start the replication watcher + if( startRepFileWatcher() ){ + //Set the appropriate status variables + LOGS.insert(20,"STARTED"); + LOGS.insert(21, dev); //zpool + LOGS.insert(22, tr("Replication Starting") ); //summary + LOGS.insert(23, QString(tr("Starting replication for %1")).arg(dev) ); //Full message + LOGS.insert(24, timestamp); //full timestamp + LOGS.insert(25, time); // time only + LOGS.insert(26,tr("Replication Log")+" <"+FILE_REPLICATION+">"); //log file + if(!quiet){ emit MessageAvailable("replication"); } + } }else if(message.contains("finished replication")){ stopRepFileWatcher(); dev = message.section(" ",-1).simplified(); - //Now set the status of the process - LOGS.insert(20,"FINISHED"); - LOGS.insert(21,dev); //dataset - LOGS.insert(22, tr("Finished Replication") ); //summary - LOGS.insert(23, QString(tr("Finished replication for %1")).arg(dev) ); - LOGS.insert(24, timestamp); //full timestamp - LOGS.insert(25, time); // time only - LOGS.insert(26, ""); //clear the log file entry - if(!quiet){ emit MessageAvailable("replication"); } + //Make sure the device is currently setup for replication + if( reppools.contains(dev) ){ + //Now set the status of the process + LOGS.insert(20,"FINISHED"); + LOGS.insert(21,dev); //dataset + LOGS.insert(22, tr("Finished Replication") ); //summary + LOGS.insert(23, QString(tr("Finished replication for %1")).arg(dev) ); + LOGS.insert(24, timestamp); //full timestamp + LOGS.insert(25, time); // time only + LOGS.insert(26, ""); //clear the log file entry + if(!quiet){ emit MessageAvailable("replication"); } + }else if( !reppools.contains( LOGS.value(21) ) ){ + //Clear the current replication log, device was removed from replication + LOGS.remove(20); + LOGS.remove(21); + LOGS.remove(22); + LOGS.remove(23); + LOGS.remove(24); + LOGS.remove(25); + LOGS.remove(26); + if(!quiet){ emit MessageAvailable(""); } + } }else if( message.contains("failed replication") ){ stopRepFileWatcher(); //Now set the status of the process dev = message.section(" ",-1).simplified(); - QString file = log.section("LOGFILE:",1,1).simplified(); - QString tt = QString(tr("Replication Failed for %1")).arg(dev) +"\n"+ QString(tr("Logfile available at: %1")).arg(file); - LOGS.insert(20,"ERROR"); - LOGS.insert(21,dev); //dataset - LOGS.insert(22, tr("Replication Failed") ); //summary - LOGS.insert(23, tt ); - LOGS.insert(24, timestamp); //full timestamp - LOGS.insert(25, time); // time only - LOGS.insert(26, tr("Replication Error Log")+" <"+file+">" ); - if(!quiet){ emit MessageAvailable("replication"); } + //Make sure the device is currently setup for replication + if( reppools.contains(dev) ){ + //Update the logs + QString file = log.section("LOGFILE:",1,1).simplified(); + QString tt = QString(tr("Replication Failed for %1")).arg(dev) +"\n"+ QString(tr("Logfile available at: %1")).arg(file); + LOGS.insert(20,"ERROR"); + LOGS.insert(21,dev); //dataset + LOGS.insert(22, tr("Replication Failed") ); //summary + LOGS.insert(23, tt ); + LOGS.insert(24, timestamp); //full timestamp + LOGS.insert(25, time); // time only + LOGS.insert(26, tr("Replication Error Log")+" <"+file+">" ); + if(!quiet){ emit MessageAvailable("replication"); } + }else if( !reppools.contains( LOGS.value(21) ) ){ + //Clear the current replication log, device was removed from replication + LOGS.remove(20); + LOGS.remove(21); + LOGS.remove(22); + LOGS.remove(23); + LOGS.remove(24); + LOGS.remove(25); + LOGS.remove(26); + if(!quiet){ emit MessageAvailable(""); } + } } } @@ -252,11 +288,10 @@ void LPWatcher::readReplicationFile(){ } } -void LPWatcher::startRepFileWatcher(){ +bool LPWatcher::startRepFileWatcher(){ //qDebug() << "Start Rep File Watcher:" << FILE_REPLICATION; - if(FILE_REPLICATION.isEmpty()){ return; } - - if(watcher->files().contains(FILE_REPLICATION)){ return; } //duplicate - file already opened + if(FILE_REPLICATION.isEmpty()){ return false; } + if(watcher->files().contains(FILE_REPLICATION)){ return true; } //duplicate - file already opened /*else if(!watcher->files().isEmpty()){ //Check that the file watcher is not already operating on a file // only one can be running at a time, so always cancel the previous instance (it is stale) @@ -266,7 +301,7 @@ void LPWatcher::startRepFileWatcher(){ FILE_REPLICATION = tmp; }*/ //Check to make sure that lpreserver actually has a process running before starting this - if( !isReplicationRunning() ){ FILE_REPLICATION.clear(); return; } + if( !isReplicationRunning() ){ qDebug() << "PID not found"; FILE_REPLICATION.clear(); return false; } //Check for the existance of the file to watch and create it as necessary if(!QFile::exists(FILE_REPLICATION)){ system( QString("touch "+FILE_REPLICATION).toUtf8() ); } //Now open the file and start watching it for changes @@ -275,6 +310,7 @@ void LPWatcher::startRepFileWatcher(){ RFSTREAM = new QTextStream(repfile); watcher->addPath(FILE_REPLICATION); //qDebug() << "Finished starting rep file watcher"; + return true; } void LPWatcher::stopRepFileWatcher(){ @@ -312,10 +348,34 @@ double LPWatcher::displayToDoubleK(QString displayNumber){ bool LPWatcher::isReplicationRunning(){ //Check for the replication PID QDir dir("/var/db/lpreserver"); - QStringList files = dir.entryList( QStringList() << ".reptask-*" ); + QStringList files = dir.entryList( QStringList() << ".reptask-*", QDir::Files | QDir::Hidden); return ( !files.isEmpty() ); } +QStringList LPWatcher::listReplicatedPools(){ + QStringList out; + QStringList cmdout = getCmdOutput("lpreserver replicate list"); + for(int i=0; i")){ + QString ds = cmdout[i].section("->",0,0).simplified(); + if(!ds.isEmpty()){ out << ds; } + } + } + return out; +} + +QStringList LPWatcher::getCmdOutput(QString cmd){ + QProcess *proc = new QProcess; + proc->setProcessChannelMode(QProcess::MergedChannels); + proc->start(cmd); + while(!proc->waitForFinished(300)){ + QCoreApplication::processEvents(); + } + QStringList out = QString(proc->readAllStandardOutput()).split("\n"); + delete proc; + return out; +} + // ------------------------------ // PRIVATE SLOTS // ------------------------------ @@ -326,7 +386,7 @@ void LPWatcher::fileChanged(QString file){ void LPWatcher::checkPoolStatus(){ //Now check zpool status for bad/running statuses - QStringList zstat = LPBackend::getCmdOutput("zpool status"); + QStringList zstat = getCmdOutput("zpool status"); //parse the output QString pool, state, timestamp; QStringList cDev, cStat, cMsg, cSummary; @@ -365,6 +425,16 @@ void LPWatcher::checkPoolStatus(){ LOGS.insert(64, timestamp); LOGS.insert(65, timestamp.section(" ",3,3) ); if(timer->interval() != sysCheckTime){ timer->start(sysCheckTime); } + }else if(zstat[i].contains(" scrub cancel")){ + //Scrub was cancelled before finishing + zstat[i] = zstat[i].replace("\t"," ").simplified(); + timestamp = zstat[i].section(" ",4,8,QString::SectionSkipEmpty); + LOGS.insert(60, "FINISHED"); + LOGS.insert(61, pool); + LOGS.insert(62, QString(tr("Scrub cancelled for %1")).arg(pool) ); + LOGS.insert(63, QString(tr("Scrub cancelled for %1")).arg(pool) ); + LOGS.insert(64, timestamp); + LOGS.insert(65,timestamp.section(" ",3,3) ); }else{ //Scrub is running - parse the line timestamp = zstat[i].section(" ",5,9,QString::SectionSkipEmpty); diff --git a/src-qt4/life-preserver/LPWatcher.h b/src-qt4/life-preserver/lp-tray/LPWatcher.h similarity index 87% rename from src-qt4/life-preserver/LPWatcher.h rename to src-qt4/life-preserver/lp-tray/LPWatcher.h index ae4eec1f5..68e7fd3a4 100644 --- a/src-qt4/life-preserver/LPWatcher.h +++ b/src-qt4/life-preserver/lp-tray/LPWatcher.h @@ -1,6 +1,8 @@ #ifndef _LP_WATCHER_H #define _LP_WATCHER_H +#include +#include #include #include #include @@ -10,8 +12,7 @@ #include #include #include - -#include "LPBackend.h" +#include class LPWatcher : public QObject{ Q_OBJECT @@ -27,6 +28,7 @@ class LPWatcher : public QObject{ public slots: void start(); void stop(); + void refresh(); private: //Internal paths for the lpreserver output files @@ -45,12 +47,15 @@ public slots: void readLogFile(bool quiet = false); void readReplicationFile(); //always sends quiet signals - void startRepFileWatcher(); + bool startRepFileWatcher(); void stopRepFileWatcher(); double displayToDoubleK(QString); // string->double conversion bool isReplicationRunning(); //check for replication PID file + QStringList listReplicatedPools(); + QStringList getCmdOutput(QString cmd); + private slots: void fileChanged(QString); //file system watcher saw a change void checkPoolStatus(); //check for serious system errors diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_af.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_af.ts new file mode 100644 index 000000000..25fd551fc --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_af.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ar.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ar.ts new file mode 100644 index 000000000..d288ccdea --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ar.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_az.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_az.ts new file mode 100644 index 000000000..288a20dc5 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_az.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bg.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bg.ts new file mode 100644 index 000000000..4f867d400 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bg.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bn.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bn.ts new file mode 100644 index 000000000..6eb1a140f --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bn.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bs.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bs.ts new file mode 100644 index 000000000..7d16b7ba9 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_bs.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ca.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ca.ts new file mode 100644 index 000000000..98aed4bed --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ca.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_cs.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_cs.ts new file mode 100644 index 000000000..b7daee9e9 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_cs.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_cy.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_cy.ts new file mode 100644 index 000000000..9619d1174 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_cy.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_da.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_da.ts new file mode 100644 index 000000000..30c0e0542 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_da.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_de.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_de.ts new file mode 100644 index 000000000..4b935f701 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_de.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_el.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_el.ts new file mode 100644 index 000000000..90b53e77c --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_el.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_GB.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_GB.ts new file mode 100644 index 000000000..464913756 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_GB.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_US.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_US.ts new file mode 100644 index 000000000..cfdb1ceb5 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_US.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_ZA.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_ZA.ts new file mode 100644 index 000000000..c56bf203d --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_en_ZA.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_es.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_es.ts new file mode 100644 index 000000000..77c3cff75 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_es.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_et.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_et.ts new file mode 100644 index 000000000..92455d370 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_et.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_eu.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_eu.ts new file mode 100644 index 000000000..4f6656bbc --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_eu.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fa.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fa.ts new file mode 100644 index 000000000..313137762 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fa.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fi.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fi.ts new file mode 100644 index 000000000..af410c0e3 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fi.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fr.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fr.ts new file mode 100644 index 000000000..0a66ea34a --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fr.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fr_CA.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fr_CA.ts new file mode 100644 index 000000000..74df2ef1a --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fr_CA.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fur.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fur.ts new file mode 100644 index 000000000..2a0a77b4c --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_fur.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_gl.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_gl.ts new file mode 100644 index 000000000..c877972a4 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_gl.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_he.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_he.ts new file mode 100644 index 000000000..4904bde35 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_he.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hi.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hi.ts new file mode 100644 index 000000000..e626880c6 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hi.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hr.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hr.ts new file mode 100644 index 000000000..7e005585c --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hr.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hu.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hu.ts new file mode 100644 index 000000000..1e652b28e --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_hu.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_id.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_id.ts new file mode 100644 index 000000000..0b7f459d7 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_id.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_is.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_is.ts new file mode 100644 index 000000000..fbf43a10b --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_is.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_it.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_it.ts new file mode 100644 index 000000000..b98a4015a --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_it.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ja.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ja.ts new file mode 100644 index 000000000..7943ac2e7 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ja.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ka.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ka.ts new file mode 100644 index 000000000..fb0b97799 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ka.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ko.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ko.ts new file mode 100644 index 000000000..eec453488 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ko.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_lt.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_lt.ts new file mode 100644 index 000000000..899088d92 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_lt.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_lv.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_lv.ts new file mode 100644 index 000000000..6fbf136c0 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_lv.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mk.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mk.ts new file mode 100644 index 000000000..ecda97e01 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mk.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mn.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mn.ts new file mode 100644 index 000000000..92d581355 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mn.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ms.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ms.ts new file mode 100644 index 000000000..697639aed --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ms.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mt.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mt.ts new file mode 100644 index 000000000..7053b9eb8 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_mt.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_nb.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_nb.ts new file mode 100644 index 000000000..3157125cb --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_nb.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ne.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ne.ts new file mode 100644 index 000000000..9f8c58b9f --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ne.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_nl.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_nl.ts new file mode 100644 index 000000000..65059c41b --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_nl.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pa.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pa.ts new file mode 100644 index 000000000..d976a3210 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pa.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pl.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pl.ts new file mode 100644 index 000000000..e040a0faa --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pl.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pt.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pt.ts new file mode 100644 index 000000000..ef0278d09 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pt.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pt_BR.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pt_BR.ts new file mode 100644 index 000000000..8502c3967 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_pt_BR.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ro.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ro.ts new file mode 100644 index 000000000..e87d43e9c --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ro.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ru.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ru.ts new file mode 100644 index 000000000..ee905def9 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ru.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sa.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sa.ts new file mode 100644 index 000000000..cda8a964b --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sa.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sk.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sk.ts new file mode 100644 index 000000000..f419a1b7c --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sk.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sl.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sl.ts new file mode 100644 index 000000000..95ead324b --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sl.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sr.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sr.ts new file mode 100644 index 000000000..932aff204 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sr.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sv.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sv.ts new file mode 100644 index 000000000..308aa4e77 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sv.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sw.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sw.ts new file mode 100644 index 000000000..8a6e4cf76 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_sw.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ta.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ta.ts new file mode 100644 index 000000000..791a0f888 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_ta.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_tg.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_tg.ts new file mode 100644 index 000000000..f1bdb3f95 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_tg.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_th.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_th.ts new file mode 100644 index 000000000..cc2236301 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_th.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_tr.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_tr.ts new file mode 100644 index 000000000..9c0654dac --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_tr.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_uk.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_uk.ts new file mode 100644 index 000000000..073675029 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_uk.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_uz.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_uz.ts new file mode 100644 index 000000000..89ea92a19 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_uz.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_vi.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_vi.ts new file mode 100644 index 000000000..44bcfd8cf --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_vi.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_CN.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_CN.ts new file mode 100644 index 000000000..323ee2a52 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_CN.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_HK.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_HK.ts new file mode 100644 index 000000000..0a26b7403 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_HK.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_TW.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_TW.ts new file mode 100644 index 000000000..6405d0799 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zh_TW.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zu.ts b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zu.ts new file mode 100644 index 000000000..57f48e8e1 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/i18n/LifePreserverTray_zu.ts @@ -0,0 +1,237 @@ + + + + + LPMessages + + + Life Preserver Messages + + + + + Messages + + + + + Log Files + + + + + Close + + + + + No recent messages + + + + + No Log Files Available + + + + + (Life Preserver) No file contents to display + + + + + (Life Preserver) File does not exist: %1 + + + + + (Life Preserver) File could not be opened: %1 + + + + + LPTray + + + View Messages + + + + + Start Application UI + + + + + Close Life Preserver Tray + + + + + Time: %1 + + + + + %1: %2 + + + + + System Alert + + + + + LPWatcher + + + New snapshot of %1 + + + + + Creating snapshot for %1 + + + + + Replication Starting + + + + + Starting replication for %1 + + + + + Replication Log + + + + + Finished Replication + + + + + Finished replication for %1 + + + + + Replication Failed for %1 + + + + + Logfile available at: %1 + + + + + Replication Failed + + + + + Replication Error Log + + + + + Replicating %1: %2 + + + + + Scrub repaired %1 bad blocks + + + + + Scrub repaired %1 blocks in %2 with %3 errors + + + + + Scrub completed + + + + + Scrub completed without needing repairs + + + + + + Scrubbing %1: %2 (%3 remaining) + + + + + + Resilvering: %1 (%2 remaining) + + + + + Resilvering Started: %1 remaining + + + + + + Resilver completed in %1 with %2 errors + + + + + + Resilver completed successfully in %1 + + + + + The pool is in a degraded state. See additional device error(s). + + + + + %1 is degraded. + + + + + The device is faulty, and should be replaced. + + + + + %1 is faulty. + + + + + The device was removed, and should be either be re-attached or replaced. + + + + + %1 was removed. + + + + + The device is unavailable and should be re-added to the pool. + + + + + %1 is unavailable. + + + + diff --git a/src-qt4/life-preserver/lp-tray/images/.directory b/src-qt4/life-preserver/lp-tray/images/.directory new file mode 100644 index 000000000..d1cdb3901 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/images/.directory @@ -0,0 +1,4 @@ +[Dolphin] +PreviewsShown=true +Timestamp=2012,11,30,10,24,22 +Version=3 diff --git a/src-qt4/life-preserver/lp-tray/images/application-exit.png b/src-qt4/life-preserver/lp-tray/images/application-exit.png new file mode 100644 index 000000000..ed5f8b251 Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/application-exit.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/backup-failed.png b/src-qt4/life-preserver/lp-tray/images/backup-failed.png new file mode 100644 index 000000000..8e9133789 Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/backup-failed.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/backup-ok.png b/src-qt4/life-preserver/lp-tray/images/backup-ok.png new file mode 100644 index 000000000..0f3153c4b Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/backup-ok.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/configure.png b/src-qt4/life-preserver/lp-tray/images/configure.png new file mode 100644 index 000000000..45b8fae8b Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/configure.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/lifepreserver.png b/src-qt4/life-preserver/lp-tray/images/lifepreserver.png new file mode 100644 index 000000000..32e3f4c5d Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/lifepreserver.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/list-add.png b/src-qt4/life-preserver/lp-tray/images/list-add.png new file mode 100644 index 000000000..e029787c7 Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/list-add.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/list-remove.png b/src-qt4/life-preserver/lp-tray/images/list-remove.png new file mode 100644 index 000000000..2bb1a5983 Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/list-remove.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/refresh.png b/src-qt4/life-preserver/lp-tray/images/refresh.png new file mode 100644 index 000000000..d07fd807c Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/refresh.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/tray-icon-error.png b/src-qt4/life-preserver/lp-tray/images/tray-icon-error.png new file mode 100644 index 000000000..0766f9ab9 Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/tray-icon-error.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/tray-icon-failed.png b/src-qt4/life-preserver/lp-tray/images/tray-icon-failed.png new file mode 100644 index 000000000..fb7e39915 Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/tray-icon-failed.png differ diff --git a/src-qt4/life-preserver/images/tray-icon-active1.png b/src-qt4/life-preserver/lp-tray/images/tray-icon-idle.png similarity index 98% rename from src-qt4/life-preserver/images/tray-icon-active1.png rename to src-qt4/life-preserver/lp-tray/images/tray-icon-idle.png index bc4aa9322..bc62771b3 100644 Binary files a/src-qt4/life-preserver/images/tray-icon-active1.png and b/src-qt4/life-preserver/lp-tray/images/tray-icon-idle.png differ diff --git a/src-qt4/life-preserver/lp-tray/images/tray-icon-working.png b/src-qt4/life-preserver/lp-tray/images/tray-icon-working.png new file mode 100644 index 000000000..ede558b91 Binary files /dev/null and b/src-qt4/life-preserver/lp-tray/images/tray-icon-working.png differ diff --git a/src-qt4/life-preserver/lp-tray/lPreserve.qrc b/src-qt4/life-preserver/lp-tray/lPreserve.qrc new file mode 100644 index 000000000..e6b20dcb0 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/lPreserve.qrc @@ -0,0 +1,16 @@ + + + images/tray-icon-error.png + images/tray-icon-working.png + images/lifepreserver.png + images/backup-ok.png + images/backup-failed.png + images/application-exit.png + images/configure.png + images/list-add.png + images/list-remove.png + images/tray-icon-idle.png + images/tray-icon-failed.png + images/refresh.png + + diff --git a/src-qt4/life-preserver/lifepreserver.desktop b/src-qt4/life-preserver/lp-tray/lifepreserver.desktop similarity index 89% rename from src-qt4/life-preserver/lifepreserver.desktop rename to src-qt4/life-preserver/lp-tray/lifepreserver.desktop index 448f85d58..5b7740dc9 100755 --- a/src-qt4/life-preserver/lifepreserver.desktop +++ b/src-qt4/life-preserver/lp-tray/lifepreserver.desktop @@ -1,5 +1,5 @@ [Desktop Entry] -Exec=sudo /usr/local/bin/life-preserver +Exec=/usr/local/bin/life-preserver-tray Icon=/usr/local/share/lifePreserver/images/lifepreserver.png MimeType= Path= @@ -45,10 +45,9 @@ Name[it]=Life Preserver Name[ja]=Life Preserver Name[ko]=Life Preserver Name[mn]=Life Preserver -Name[nl]=Reddingsboei +Name[nl]=Reddingsvest Name[pl]=Kamizelka ratunkowa Name[pt_BR]=Life Preserver -Name[ro]=Colac de salvare Name[ru]=Life Preserver Name[sk]=Life Preserver Name[sl]=Life Preserver @@ -59,8 +58,8 @@ Name[tr]=Yedekleyici Name[uk]=Зберігач життя Name[vi]=đồ cứu nguy Name[zh_CN]=Life Preserver备份程序 -Name[zh_HK]=救生員 Life Preserver -Name[zh_TW]=救生員 Life Preserver +Name[zh_HK]=Life Preserver +Name[zh_TW]=Life Preserver GenericName=Life Preserver Backup GenericName[af]=Reddingsboei Friends GenericName[ar]=حارس الحياة (النسخ الاحتياطي) @@ -82,14 +81,13 @@ GenericName[he]=גיבוי גלגל הצלה GenericName[hr]=Life Preserver sigurnosne kopije GenericName[hu]=Mentőöv biztonsági mentés GenericName[id]=Life Preserver Backup -GenericName[it]=Life Preserver Backup +GenericName[it]=Strumento per il Backup Life Preserver GenericName[ja]=バックアップ管理プログラム GenericName[ko]=Life Preserver Backup GenericName[mn]=Life Preserver Нөөцлөх -GenericName[nl]=Reddingsboei-reservekopie +GenericName[nl]=Reddingsvest-reservekopie GenericName[pl]=Kopia zapasowa Kamizelki Ratunkowej GenericName[pt_BR]=Backup com o Life Preserver -GenericName[ro]=Copie de rezervă a colacului de slavare GenericName[ru]=Создание резервных копий (Life Preserver) GenericName[sk]=Life Preserver Zálohovanie GenericName[sl]=Varnostno kopiranje @@ -100,5 +98,5 @@ GenericName[tr]=Life Preserver Yedekleme GenericName[uk]=Засіб для створення резервних копій GenericName[vi]=Dồ cứu nguy sao lưu GenericName[zh_CN]=Life Preserver备份 -GenericName[zh_HK]=救生員 Life Preserver 備份程式 -GenericName[zh_TW]=救生員 Life Preserver 備份管理程式 +GenericName[zh_HK]=Life Preserver 備份程式 +GenericName[zh_TW]=Life Preserver備份管理程式 diff --git a/src-qt4/life-preserver/lp-tray/lp-tray.pro b/src-qt4/life-preserver/lp-tray/lp-tray.pro new file mode 100644 index 000000000..62f819ed3 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/lp-tray.pro @@ -0,0 +1,105 @@ +TEMPLATE = app +LANGUAGE = C++ +LIBS += -lQtSolutions_SingleApplication-head + +CONFIG += qt warn_on release + +HEADERS += LPTray.h \ + LPWatcher.h \ + LPMessages.h + +SOURCES += main.cpp \ + LPTray.cpp \ + LPWatcher.cpp \ + LPMessages.cpp + +RESOURCES += lPreserve.qrc + +FORMS = LPMessages.ui + +TARGET=life-preserver-tray +target.path=/usr/local/bin + + +images.path=/usr/local/share/lifePreserver/images/ +images.files=images/lifepreserver.png + +desktop.path=/usr/local/share/applications +desktop.files=lifepreserver.desktop + +desktopperm.path=/usr/local/share/applications/ +desktopperm.extra=chmod 644 /usr/local/share/applications/lifepreserver.desktop + +dotrans.path=/usr/local/share/lifePreserver/i18n/ +dotrans.extra=cd i18n && lrelease-qt4 -nounfinished *.ts && cp *.qm $(INSTALL_ROOT)/usr/local/share/lifePreserver/i18n/ + +INSTALLS += target dotrans images + +TRANSLATIONS = i18n/LifePreserverTray_af.ts \ + i18n/LifePreserverTray_ar.ts \ + i18n/LifePreserverTray_az.ts \ + i18n/LifePreserverTray_bg.ts \ + i18n/LifePreserverTray_bn.ts \ + i18n/LifePreserverTray_bs.ts \ + i18n/LifePreserverTray_ca.ts \ + i18n/LifePreserverTray_cs.ts \ + i18n/LifePreserverTray_cy.ts \ + i18n/LifePreserverTray_da.ts \ + i18n/LifePreserverTray_de.ts \ + i18n/LifePreserverTray_el.ts \ + i18n/LifePreserverTray_en_US.ts \ + i18n/LifePreserverTray_en_GB.ts \ + i18n/LifePreserverTray_en_ZA.ts \ + i18n/LifePreserverTray_es.ts \ + i18n/LifePreserverTray_et.ts \ + i18n/LifePreserverTray_eu.ts \ + i18n/LifePreserverTray_fa.ts \ + i18n/LifePreserverTray_fi.ts \ + i18n/LifePreserverTray_fr.ts \ + i18n/LifePreserverTray_fr_CA.ts \ + i18n/LifePreserverTray_fur.ts \ + i18n/LifePreserverTray_gl.ts \ + i18n/LifePreserverTray_he.ts \ + i18n/LifePreserverTray_hi.ts \ + i18n/LifePreserverTray_hr.ts \ + i18n/LifePreserverTray_hu.ts \ + i18n/LifePreserverTray_id.ts \ + i18n/LifePreserverTray_is.ts \ + i18n/LifePreserverTray_it.ts \ + i18n/LifePreserverTray_ja.ts \ + i18n/LifePreserverTray_ka.ts \ + i18n/LifePreserverTray_ko.ts \ + i18n/LifePreserverTray_lt.ts \ + i18n/LifePreserverTray_lv.ts \ + i18n/LifePreserverTray_mk.ts \ + i18n/LifePreserverTray_mn.ts \ + i18n/LifePreserverTray_ms.ts \ + i18n/LifePreserverTray_mt.ts \ + i18n/LifePreserverTray_nb.ts \ + i18n/LifePreserverTray_ne.ts \ + i18n/LifePreserverTray_nl.ts \ + i18n/LifePreserverTray_pa.ts \ + i18n/LifePreserverTray_pl.ts \ + i18n/LifePreserverTray_pt.ts \ + i18n/LifePreserverTray_pt_BR.ts \ + i18n/LifePreserverTray_ro.ts \ + i18n/LifePreserverTray_ru.ts \ + i18n/LifePreserverTray_sa.ts \ + i18n/LifePreserverTray_sk.ts \ + i18n/LifePreserverTray_sl.ts \ + i18n/LifePreserverTray_sr.ts \ + i18n/LifePreserverTray_sv.ts \ + i18n/LifePreserverTray_sw.ts \ + i18n/LifePreserverTray_ta.ts \ + i18n/LifePreserverTray_tg.ts \ + i18n/LifePreserverTray_th.ts \ + i18n/LifePreserverTray_tr.ts \ + i18n/LifePreserverTray_uk.ts \ + i18n/LifePreserverTray_uz.ts \ + i18n/LifePreserverTray_vi.ts \ + i18n/LifePreserverTray_zh_CN.ts \ + i18n/LifePreserverTray_zh_HK.ts \ + i18n/LifePreserverTray_zh_TW.ts \ + i18n/LifePreserverTray_zu.ts + +QMAKE_LIBDIR = /usr/local/lib/qt4 /usr/local/lib diff --git a/src-qt4/life-preserver/lp-tray/main.cpp b/src-qt4/life-preserver/lp-tray/main.cpp new file mode 100644 index 000000000..a4db38bf2 --- /dev/null +++ b/src-qt4/life-preserver/lp-tray/main.cpp @@ -0,0 +1,47 @@ +#include +#include +#include +#include +#include +#include +#include + +#include "LPTray.h" +//#include "../config.h" + +#ifndef PREFIX +#define PREFIX QString("/usr/local/") +#endif + +int main( int argc, char ** argv ) +{ + QtSingleApplication a(argc, argv); + if (a.isRunning()) + return !(a.sendMessage("show")); + + //Check whether running as root + if( getuid() == 0){ + qDebug() << "Life-Preserver Tray must not be started as root!"; + return 1; + } + + QTranslator translator; + QLocale mylocale; + QString langCode = mylocale.name(); + if ( ! QFile::exists( PREFIX + "/share/lifePreserver/i18n/LifePreserverTray_" + langCode + ".qm" ) ) + langCode.truncate(langCode.indexOf("_")); + translator.load( QString("LifePreserverTray_") + langCode, PREFIX + "/share/lifePreserver/i18n/" ); + a.installTranslator( &translator ); + qDebug() << "Locale:" << langCode; + + LPTray *w = new LPTray(); + w->show(); + + QObject::connect( &a, SIGNAL( messageReceived(const QString &) ), w, SLOT( slotSingleInstance() ) ); + int ret = -1; + while( w->isVisible() ){ + //Make sure the application does not exit while the tray is still open + ret = a.exec(); + } + return ret; +} diff --git a/src-qt4/life-preserver/mainUI.cpp b/src-qt4/life-preserver/mainUI.cpp deleted file mode 100644 index 98f9365a4..000000000 --- a/src-qt4/life-preserver/mainUI.cpp +++ /dev/null @@ -1,501 +0,0 @@ -#include "mainUI.h" -#include "ui_mainUI.h" -#include - -mainUI::mainUI(QWidget *parent) : QMainWindow(parent), ui(new Ui::mainUI){ - //Initialize the graphical items - ui->setupUi(this); //load the mainUI.ui file - revMenu = new QMenu(); - brMenu = new QMenu(); - addMenu = new QMenu(); - //Setup the menu system - ui->tool_revert->setMenu(revMenu); - ui->tool_browse->setMenu(brMenu); - ui->tool_add->setMenu(addMenu); - connect(revMenu,SIGNAL(triggered(QAction*)),this,SLOT(slotRevertToSnapshot(QAction*)) ); - connect(brMenu,SIGNAL(triggered(QAction*)),this,SLOT(slotBrowseSnapshot(QAction*)) ); - connect(addMenu, SIGNAL(triggered(QAction*)),this,SLOT(slotAddDataset(QAction*)) ); - //Setup the Key menu items (static items, never changed) - keyMenu = new QMenu(); - keyMenu->addAction(ui->actionKeyNew); //action from designer - keyMenu->addAction(ui->actionKeyCopy); //action from designer - ui->tool_keys->setMenu(keyMenu); - //Setup the update frequency limiter - freqTimer = new QTimer(); - freqTimer->setSingleShot(true); - freqTimer->setInterval(15000); - connect(freqTimer, SIGNAL(timeout()), this, SLOT(setupUI()) ); -} - -mainUI::~mainUI(){ - -} - -void mainUI::setupUI(){ - //Initialize the Hash (make sure it is not run too frequently - causes kernel panics) - if(lastUpdate.isNull() || lastUpdate.addSecs(15) < QTime::currentTime() ){ - enableButtons(false); //disable the buttons temporarily - lastUpdate = QTime::currentTime(); - qDebug() << "Updating the database"; - ui->statusbar->showMessage(tr("Updating the database"),0); - updateHash(); - ui->statusbar->clearMessage(); - }else{ - freqTimer->start(); - } - //Update the display - updateUI(); - updateMenus(); -} - -LPDataset mainUI::newDataset(QString ds){ - //subroutine to create and fill a new dataset with system information - qDebug() << "New Dataset: " << ds; - LPDataset DSC; - //List all the mountpoints in this dataset - QStringList subsets = LPBackend::listDatasetSubsets(ds); - QStringList lpsnaps = LPBackend::listLPSnapshots(ds); - //populate the list of snapshots available for each mountpoint - for(int i=0; i -1){ subsnaps << lpsnaps[s]; snaps.removeAt(index); } - } - //Now list all the other available snapshots (no certain ordering) - if(!snaps.isEmpty()){ - subsnaps << "--"; //so we know that this is a divider between the sections - subsnaps << snaps; - } - DSC.subsetHash.insert(subsets[i],subsnaps); //add it to the internal container hash - } - } - //Get the time for the latest life-preserver snapshot (and total number) - //Find the index for the current list - int ci = 0; - while(ci < CLIST.length()){ - if(CLIST[ci].startsWith(ds+":::")){ break; } - else{ ci++; } - } - if(CLIST.isEmpty()){ ci = -1; } //catch for empty list - if(DSC.subsetHash.size() < 1){ - DSC.numberOfSnapshots = "0"; - DSC.latestSnapshot= ""; - }else{ - DSC.numberOfSnapshots = QString::number(lpsnaps.length()); - if(lpsnaps.isEmpty()){ DSC.latestSnapshot=""; } - else if(ci > -1 && ci < CLIST.length()){ - QString sna = CLIST[ci].section(":::",1,1); - if(sna != "-"){ DSC.latestSnapshot= sna; } - else{ DSC.latestSnapshot = ""; } - }else{ DSC.latestSnapshot=lpsnaps[0]; } - } - //List the replication status - if(RLIST.contains(ds) && (ci > -1)){ - QString rep = CLIST[ci].section(":::",2,2); - if(rep != "-"){ DSC.latestReplication = rep; } - else{ DSC.latestReplication= tr("Enabled"); } - }else{ - DSC.latestReplication= tr("Disabled"); - } - //Return the dataset - return DSC; -} - -void mainUI::enableButtons(bool enable){ - if(enable){ - //special care must be taken here to only enable the ones that are valid - updateMenus(); - }else{ - ui->tool_add->setEnabled(false); - ui->tool_browse->setEnabled(false); - ui->tool_config->setEnabled(false); - ui->tool_keys->setEnabled(false); - ui->tool_newsnapshot->setEnabled(false); - ui->tool_remove->setEnabled(false); - ui->tool_revert->setEnabled(false); - } - -} - -// ================= -// PRIVATE FUNCTIONS -// ================= -void mainUI::updateHash(QString ds){ - //qDebug() << "Get replication targets"; - RLIST = LPBackend::listReplicationTargets(); //update list of replication datasets - //qDebug() << "Get possible datasets"; - SLIST = LPBackend::listPossibleDatasets(); - //qDebug() << "List current status"; - CLIST = LPBackend::listCurrentStatus(); - //qDebug() << "Check hash"; - if(HLIST.contains(ds) && !ds.isEmpty()){ - //only update the entry for the given dataset - HLIST.insert(ds, newDataset(ds)); //will overwrite the current entry in the hash - }else{ - //Clear and fill the hash - //qDebug() << "Clear hash"; - HLIST.clear(); - //qDebug() << "List datasets"; - QStringList dsList = LPBackend::listDatasets(); - for(int i=0; itreeWidget->clear(); - QStringList dsList = HLIST.keys(); - for(int i=0; itreeWidget->addTopLevelItem( new QTreeWidgetItem(cols) ); - } - //Now adjust the columns in the widget - for(int i=0; i<4; i++){ - ui->treeWidget->resizeColumnToContents(i); - } - //Now make sure that the add button menu only shows the available datasets - addMenu->clear(); - for(int i=0; iaddAction( new QAction(SLIST[i],this) ); } - } - if(addMenu->isEmpty()){ ui->tool_add->setEnabled(false); } - else{ ui->tool_add->setEnabled(true); } -} - -void mainUI::updateMenus(){ - //Reset the button menu's to correspond to the selected dataset - QString ds = getSelectedDS(); - //Enable/disable the remove/config buttons if nothing selected - if(ds.isEmpty()){ - ui->tool_remove->setVisible(false); - ui->tool_config->setVisible(false); - ui->tool_newsnapshot->setVisible(false); - }else{ - ui->tool_remove->setVisible(true); ui->tool_remove->setEnabled(true); - ui->tool_config->setVisible(true); ui->tool_config->setEnabled(true); - ui->tool_newsnapshot->setVisible(true); ui->tool_newsnapshot->setEnabled(true); - } - //Enabled/disable the SSH key management - if(RLIST.contains(ds) && !ds.isEmpty()){ - ui->tool_keys->setVisible(true); - ui->tool_keys->setEnabled(true); - }else{ - ui->tool_keys->setVisible(false); - } - //check for a valid ds/snapshot combination - bool ok = !ds.isEmpty(); - if(ok){ ok = HLIST.contains(ds); } - if(ok){ ok = (HLIST[ds].numberOfSnapshots.toInt() > 0); } - //Now set the items appropriately - revMenu->clear(); - brMenu->clear(); - if(ok){ - //Reset the Menu Contents - QStringList subsets = HLIST[ds].subsets(); - for(int i=0; iaddSeparator(); } - else{ - QAction *act = new QAction(snaps[s],this); - act->setWhatsThis(ds+":::"+subsets[i]+":::"+snaps[s]); - menu->addAction(act); - } - } - revMenu->addMenu(menu); - brMenu->addMenu(menu); - } - //Enable the buttons if appropriate - if(revMenu->isEmpty()){ - ui->tool_revert->setEnabled(false); - ui->tool_browse->setEnabled(false); - }else{ - ui->tool_revert->setEnabled(true); - ui->tool_browse->setEnabled(true); - } - }else{ - //Disable the buttons - ui->tool_revert->setEnabled(false); - ui->tool_browse->setEnabled(false); - } -} - -QString mainUI::getSelectedDS(){ - //Get the currently selected dataset - QString ds=""; - if(ui->treeWidget->topLevelItemCount() > 0){ - if( ui->treeWidget->currentItem() != 0){ - ds = ui->treeWidget->currentItem()->text(0); //first column - } - } - return ds; -} - -// ================= -// PRIVATE SLOTS -// ================= -// --- Buttons Clicked -void mainUI::on_treeWidget_itemSelectionChanged(){ - if(ui->statusbar->currentMessage().isEmpty()){ - //only update the menu's if they are not currently disabled while a process is running - updateMenus(); - } -} - -void mainUI::on_tool_config_clicked(){ - QString ds = getSelectedDS(); - if(ds.isEmpty()){ return; } - LPConfig CFG(this); - CFG.loadDataset(ds, RLIST.contains(ds)); - CFG.exec(); - //Now check for return values and update appropriately - bool change = false; - if(CFG.localChanged){ - enableButtons(false); - ui->statusbar->showMessage(QString(tr("Configuring dataset: %1")).arg(ds),0); - LPBackend::setupDataset(ds, CFG.localSchedule, CFG.localSnapshots); - ui->statusbar->clearMessage(); - change = true; - } - if(CFG.remoteChanged){ - change = true; - enableButtons(false); - if(CFG.isReplicated){ - ui->statusbar->showMessage(QString(tr("Configuring replication: %1")).arg(ds),0); - LPBackend::setupReplication(ds, CFG.remoteHost, CFG.remoteUser, CFG.remotePort, CFG.remoteDataset, CFG.remoteFreq); - QMessageBox::information(this,tr("Reminder"),tr("Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!!")); - }else{ - ui->statusbar->showMessage(QString(tr("Removing replication: %1")).arg(ds),0); - LPBackend::removeReplication(ds); - } - ui->statusbar->clearMessage(); - } - //Now update the UI if appropriate - if(change){ - setupUI(); - } -} - -void mainUI::on_tool_remove_clicked(){ - QString ds = getSelectedDS(); - if(!ds.isEmpty()){ - //Verify the removal of the dataset - if( QMessageBox::Yes == QMessageBox::question(this,tr("Verify Dataset Backup Removal"),tr("Are you sure that you wish to cancel automated snapshots and/or replication of the following dataset?")+"\n\n"+ds,QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ - enableButtons(false); - //verify the removal of all the snapshots for this dataset - QStringList snaps = LPBackend::listLPSnapshots(ds); - if(!snaps.isEmpty()){ - if( QMessageBox::Yes == QMessageBox::question(this,tr("Verify Snapshot Deletion"),tr("Do you wish to remove the local snapshots for this dataset?")+"\n"+tr("WARNING: This is a permanant change that cannot be reversed"),QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ - //Remove all the snapshots - ui->statusbar->showMessage(QString(tr("%1: Removing snapshots")).arg(ds),0); - for(int i=0; istatusbar->clearMessage(); - } - } - //Remove the dataset from life-preserver management - if(RLIST.contains(ds)){ - ui->statusbar->showMessage(QString(tr("%1: Disabling Replication")).arg(ds),0); - LPBackend::removeReplication(ds); - ui->statusbar->clearMessage(); - } - ui->statusbar->showMessage(QString(tr("%1: Disabling Life-Preserver Management")).arg(ds),0); - LPBackend::removeDataset(ds); - ui->statusbar->clearMessage(); - } - } - setupUI(); -} - -void mainUI::on_tool_newsnapshot_clicked(){ - QString ds = getSelectedDS(); - if(ds.isEmpty()){return; } - //Get the new snapshot name from the user - bool ok; - QString name = QInputDialog::getText(this,tr("New Snapshot Name"), tr("Snapshot Name:"), QLineEdit::Normal, tr("Name"), &ok, 0, Qt::ImhUppercaseOnly | Qt::ImhLowercaseOnly | Qt::ImhDigitsOnly ); - if(!ok || name.isEmpty()){ return; } //cancelled - qDebug() << "Creating a new snapshot:" << ds << name; - //Now create the new snapshot - LPBackend::newSnapshot(ds,name); - QMessageBox::information(this,tr("Snapshot Pending"), tr("The new snapshot creation has been added to the queue")); - setupUI(); -} - -// --- Menu Items Clicked -void mainUI::slotRevertToSnapshot(QAction *act){ - QString info = act->whatsThis(); - QString ds = info.section(":::",0,0); - QString subset = info.section(":::",1,1); - QString snap = info.section(":::",2,2); - qDebug() << "Revert Clicked:" << ds << subset << snap; - if(!ds.isEmpty()){ - //Verify the reversion - if( QMessageBox::Yes == QMessageBox::question(this,tr("Verify Snapshot Reversion"), - QString(tr("Are you sure that you wish to revert %1 to the selected snapshot?")).arg(subset)+"\n"+tr("WARNING: This will result in the loss of any data not previously backed up."), - QMessageBox::Yes | QMessageBox::No, QMessageBox::No) ){ - //Perform the reversion - enableButtons(false); - ui->statusbar->showMessage(QString(tr("%1: Reverting dataset: %2")).arg(ds,subset),0); - if( !LPBackend::revertSnapshot(ds+subset,snap) ){ - //Error performing the reversion - qDebug() << " - Error:" << ds+subset << snap; - QMessageBox::warning(this,tr("Reversion Error"), tr("The snapshot reversion could not be completed successfully.")); - }else{ - //Good reversion - qDebug() << " - Revert Complete"; - QMessageBox::information(this,tr("Reversion Success"), tr("The snapshot reversion was completed successfully.")); - } - ui->statusbar->clearMessage(); - enableButtons(true); - } - } -} - -void mainUI::slotBrowseSnapshot(QAction *act){ - QString info = act->whatsThis(); - QString ds = info.section(":::",0,0); - QString subset = info.section(":::",1,1); - QString snap = info.section(":::",2,2); - //Now let the user select a file within the snapshot to revert - QString snapPath = subset+"/.zfs/snapshot/"+snap+"/"; - QString filepath = QFileDialog::getOpenFileName(this,tr("Revert a file"), snapPath, tr("Backup Files (*)") ); - qDebug() << "File to revert:" << filepath; - //Check to make sure that it is a valid file (within the snapshot) - if(filepath.isEmpty() ){ - qDebug() << " - Cancelled"; - //action cancelled - do nothing - }else if(!filepath.startsWith(snapPath)){ - qDebug() << " - Invalid File"; - QMessageBox::warning(this, tr("Invalid Snapshot File"), tr("Please select a file from within the chosen snapshot that you wish to revert")); - }else{ - enableButtons(false); - ui->statusbar->showMessage(QString(tr("%1: Reverting File: %2")).arg(ds,filepath.remove(".zfs/snapshot/"+snap+"/").replace(QDir::homePath(),"~")),0); - //Revert the file - QString newfile = LPBackend::revertSnapshotFile(subset,snap,filepath); - if(newfile.isEmpty()){ - //Error copying the new file over - qDebug() << " - Error copying file"; - QMessageBox::warning(this, tr("Error Reverting File"), QString(tr("An error occurred while tring to revert the file %1. Please try again.")).arg(filepath)); - }else{ - //Let the user know the location of the reverted file - qDebug() << " - Successful reversion:" << newfile; - QMessageBox::information(this, tr("FIle Reverted"), QString(tr("The reverted file is now available at: %1")).arg(newfile) ); - } - ui->statusbar->clearMessage(); - enableButtons(true); - } - return; -} - -void mainUI::slotAddDataset(QAction *act){ - QString dataset = act->text(); - qDebug() << "Start Wizard for new dataset:" << dataset; - LPWizard wiz(this); - wiz.setDataset(dataset); - wiz.exec(); - //See if the wizard was cancelled or not - if(!wiz.cancelled){ - enableButtons(false); - ui->statusbar->showMessage(QString(tr("Enabling dataset management: %1")).arg(dataset),0); - //run the proper commands to get the dataset enabled - if( LPBackend::setupDataset(dataset, wiz.localTime, wiz.totalSnapshots) ){ - if(wiz.enableReplication){ - LPBackend::setupReplication(dataset, wiz.remoteHost, wiz.remoteUser, wiz.remotePort, wiz.remoteDataset, wiz.remoteTime); - QMessageBox::information(this,tr("Reminder"),tr("Don't forget to save your SSH key to a USB stick so that you can restore your system from the remote host later!!")); - } - } - ui->statusbar->clearMessage(); - } - //Now update the UI/Hash - setupUI(); -} - -void mainUI::on_actionClose_triggered(){ - this->close(); -} - -void mainUI::on_actionKeyNew_triggered(){ - QString ds = getSelectedDS(); - if(ds.isEmpty()){ return; } - qDebug() << "New SSH Key triggered for DS:" << ds; - enableButtons(false); - ui->statusbar->showMessage(QString(tr("%1: Setting up SSH Key")).arg(ds),0); - //Get the remote values for this dataset - QString remoteHost, user, remotedataset; - int port, time; - bool ok = LPBackend::replicationInfo(ds, remoteHost, user, port, remotedataset, time); - if(ok){ - if( !LPBackend::setupSSHKey(remoteHost, user, port) ){ - QMessageBox::warning(this,tr("Failure"), tr("There was an error while creating the SSH key.")); - }else{ - QMessageBox::information(this,tr("Success"), tr("The SSH key was successfully generated.")); - } - }else{ - QMessageBox::warning(this,tr("Failure"), tr("There was an error in retrieving the remote replication information for this dataset. Please ensure that replication is enabled and try agin.") ); - } - ui->statusbar->clearMessage(); - enableButtons(true); -} - -void mainUI::on_actionKeyCopy_triggered(){ - QString ds = getSelectedDS(); - if(ds.isEmpty()){ return; } - qDebug() << "Copy SSH Key triggered for DS:" << ds; - //Get the local hostname - char host[1023] = "\0"; - gethostname(host,1023); - QString localHost = QString(host).simplified(); - qDebug() << " - hostname:" << localHost; - //Scan for mounted USB devices - QStringList devs = LPBackend::findValidUSBDevices(); - qDebug() << " - devs:" << devs; - if(devs.isEmpty()){ - QMessageBox::warning(this,tr("No Valid USB Devices"), tr("No valid USB devices could be found. Please mount a FAT32 formatted USB stick and try again.")); - return; - } - //Ask the user which one to save the file to - bool ok; - QString dev = QInputDialog::getItem(this, tr("Select USB Device"), tr("Available USB Devices:"), devs,0,false,&ok); - if(!ok or dev.isEmpty()){ return; } //cancelled - QString devPath = dev.section("(",0,0).simplified(); - //Now copy the file over - ok = LPBackend::copySSHKey(devPath, localHost); - if(ok){ - QMessageBox::information(this,tr("Success"), tr("The public SSH key file was successfully copied onto the USB device.")); - }else{ - QMessageBox::information(this,tr("Failure"), tr("The public SSH key file could not be copied onto the USB device.")); - } -} - -// ============= -// PROTECTED -// ============= -void mainUI::closeEvent(QCloseEvent *event){ - //Make sure this window only gets hidden rather than closed - // this prevents the entire tray application from closing down as well - event->ignore(); - this->hide(); -} diff --git a/src-qt4/life-preserver/mainUI.h b/src-qt4/life-preserver/mainUI.h deleted file mode 100644 index 5296b71fb..000000000 --- a/src-qt4/life-preserver/mainUI.h +++ /dev/null @@ -1,75 +0,0 @@ -#ifndef _LP_MAINUI_H -#define _LP_MAINUI_H - -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include -#include - -#include "LPBackend.h" -#include "LPWizard.h" -#include "LPContainers.h" -#include "LPConfig.h" - -//TERMINOLOGY NOTE: DS=DataSet, SNAP=Snapshot - -namespace Ui { - class mainUI; -} - -class mainUI : public QMainWindow{ - Q_OBJECT - -public: - explicit mainUI(QWidget* parent = 0); - ~mainUI(); - - -public slots: - void setupUI(); //for the tray to call it as necessary - -private: - Ui::mainUI *ui; - QHash HLIST; - QStringList RLIST; //datasets that have replication enabled - QStringList SLIST; //available datasets on the system - QStringList CLIST; //current status for all datasets - QMenu *revMenu, *brMenu, *addMenu, *keyMenu; //button menu's - QTime lastUpdate; - QTimer *freqTimer; - - void updateHash(QString ds=""); - void updateUI(); - void updateMenus(); - QString getSelectedDS(); - LPDataset newDataset(QString); - - void enableButtons(bool); - -private slots: - void on_treeWidget_itemSelectionChanged(); - void on_tool_config_clicked(); - void on_tool_remove_clicked(); - void on_tool_newsnapshot_clicked(); - - void slotRevertToSnapshot(QAction*); - void slotBrowseSnapshot(QAction*); - void slotAddDataset(QAction*); - - void on_actionClose_triggered(); - void on_actionKeyNew_triggered(); - void on_actionKeyCopy_triggered(); - -protected: - void closeEvent(QCloseEvent*); - -}; -#endif diff --git a/src-qt4/life-preserver/mainUI.ui b/src-qt4/life-preserver/mainUI.ui deleted file mode 100644 index 01dbe3b0d..000000000 --- a/src-qt4/life-preserver/mainUI.ui +++ /dev/null @@ -1,257 +0,0 @@ - - - mainUI - - - - 0 - 0 - 456 - 175 - - - - Life Preserver - - - - :/images/lifepreserver.png:/images/lifepreserver.png - - - - - - - 0 - - - 100 - - - - Data Set - - - - - Latest Snapshot - - - - - Available - - - - - Replication - - - - - - - - QFrame::StyledPanel - - - QFrame::Raised - - - - 0 - - - - - Enable backups of a new dataset - - - Add - - - - :/images/list-add.png:/images/list-add.png - - - QToolButton::InstantPopup - - - - - - - Remove selected dataset from automatic backup - - - Remove - - - - :/images/list-remove.png:/images/list-remove.png - - - QToolButton::InstantPopup - - - - - - - Customize the backup configuration for the selected dataset - - - Configure - - - - :/images/configure.png:/images/configure.png - - - QToolButton::InstantPopup - - - - - - - Manage SSH keys for replication authentication - - - Key Setup - - - - :/images/key.png:/images/key.png - - - QToolButton::InstantPopup - - - - - - - Qt::Horizontal - - - - 40 - 20 - - - - - - - - Make a new snapshot immediately - - - ... - - - - :/images/camera_add.png:/images/camera_add.png - - - - - - - Browse a snapshot and safely recover that version of a file - - - Browse - - - - :/images/folder.png:/images/folder.png - - - QToolButton::InstantPopup - - - - - - - Revert an entire data subset to a previous snapshot (overwrites all files) - - - Revert - - - - :/images/lifepreserver.png:/images/lifepreserver.png - - - QToolButton::InstantPopup - - - - - - - - - - - - 0 - 0 - 456 - 20 - - - - - File - - - - - - - - - - :/images/application-exit.png:/images/application-exit.png - - - Close Window - - - - - - :/images/upload.png:/images/upload.png - - - Copy To USB Stick - - - - - - :/images/list-add.png:/images/list-add.png - - - Generate SSH Key - - - - - - :/images/drive-removable-media.png:/images/drive-removable-media.png - - - Mirror Dataset to USB - - - - - - - -