six demon bag
Wind, fire, all that kind of thing!
Barracuda Backup reports show a warning when the Windows agent cannot find a drive that is supposed to be backed up:
A Volume (drive) that was previously backed up is no longer there and being backed up.: Removing volume X: because it no longer exists.
The vendor documentation has an article that describes how to bring the missing drive back online. But what if the drive was removed on purpose and people just forgot to adjust the backup configuration first? You can't simply change the backup configuration to ignore the drive after the fact, since the drive is already absent and thus cannot be de-selected.
Posted 11:05 [permalink]
Recently I tried to install LXD (Canonical's container manager) from backports on a Ubuntu 16.04 system (running without Systemd). The version shipping with the system (2.0) doesn't suffice, because I need the new storage API that was introduced with LXD 2.15. However, upgrading to the backports package failed post-install:
invoke-rc.d: initscript lxd, action "start" failed. dpkg: error processing package lxd (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-19) ... Errors were encountered while processing: lxd E: Sub-process /usr/bin/dpkg returned an error code (1)
Which was weird, since the upgrade had worked for me before.
Posted 13:57 [permalink]
If you have a
DataTable object in PowerShell and you want to persist that object as a file (and restore it back to a
DataTable object sometime later) the naïve approach would be to export the (tabular) data to a (tabular) CSV:
$dt | Export-Csv -Path 'C:\path\to\table.csv' -NoType
However, the problem with this approach is that you lose the type information for the columns of the datatable (the only type information saved by the
Export-Csv cmdlet is about the type of the objects representing the rows). Also, there's no simple way to restore the CSV back to a datatable.
Posted 17:01 [permalink]
Sometimes a situation arises where an SQL Server instance comes back up with a database tagged as "suspect". Apparently there is a number of possible causes for this, like transaction log corruption, insufficient memory or disk space, or unexpected shutdowns due to hardware or power failure. In our case the reason was probably a hardware failure, since the database resides on an iSCSI volume, and we were making changes to our iSCSI network. And to make things a little bit more interesting, our
msdb database just had to be among the affected databases.
Posted 19:07 [permalink]
Although IBM doesn't officially support its TSM client on Linux distributions other than SLES and RHEL the client works quite nicely on Debian. With version 6.4 you need at least the following 4 packages on AMD64 systems:
Posted 00:46 [permalink]