One final question about this - when i issue the query command from the console
this way, is there a way to either pagenate the results or send them to a file
so I can browse them? These are 3 months of CCTV from multiple cameras running
24/7 in 20 minute sections, so there are rather a lot of
I never realized you could copy the sample SQL commands that way. So I did
that, found the job id's from 14 then the listing from 12. Excellent,
thanks!
+--
|This was sent by bill.dam...@yahoo.com via Backup Central.
|Forward
On 04/21/2015 03:27 PM, Eric Bollengier wrote:
Hello Silver,
On 21/04/2015 10:29, Silver Salonen wrote:
I think there is something else wrong with my backups here. We now have
7.0.5, but Base job is still not selected when starting restore. Maybe
we're missing DB entries here or... ?
===
On Wed, Apr 22, 2015 at 12:38 PM, Michael Schwager
mschwa...@mochotrading.com wrote:
Hello,
I have a couple of tapes that I believe should be up for recycling. These
tapes have a VolRetention period of 7,776,000 which is 90 days ( / 86400 ==
90). Now is:
# date +%s
1429719504
So 90 days ago
Hi Steve,
Would you like to try a shell script in a RunBeforeJob directive? Maybe
this should work:
#!/bin/bash
#
# Usage: myscript.sh MyBackupJob
JOB=$1
BCONSOLE=/pathtoyourbconsole/bconsole
MYSTORAGE=myStorage
MYPOOL=myPool
BYTES=$(echo estimate job=$JOB | $BCONSOLE)
GBYTES=$(echo
Hi,
Maybe something like this:
#!/bin/bash
VOLUME=$1
DBHOST=localhost
DATABASE=bacula
USER=
PASSWORD=
JOBS=($(mysql --host=$DBHOST --database=$DATABASE --user=$USER
--password=$PASSWORD -N -e SELECT DISTINCT Job.JobId as JobId,Job.Name as
Name,Job.StartTime as StartTime, Job.Type as
Hi,
It would be far quicker to find the files I needed
and it means I can do this search without interfering with the daily
backups which are using the same drive. By the way, the CCTV isn't on 100%
of the time, so having said that the files might not be present and/or the
filenames not
As I said, it's not necessarily a disk space issue.
But it is harder to find if it isn't :(
It can also be a RAM issue, even if it would appear that there's plenty of free
memory left.
Some kernel and driver parts of windows allocate a fixed pool of memory at
boot, and can't grow that later.
Hello,
I would be careful about assuming that VSS is reporting errors on the E
drive. It could well be some other drive, so it would be a good idea to
check them all.
Generally, VSS has a number of bugs, and you may be triggering one,
which can explain why it works after a reboot and then fails
Hi,
I have a client with multiple drive ( e: , f: , g:, h: ).
I Split into 4 jobs with 4 Fileset, with 4 pools. It's a big Client ( 10
To ) with Millions of files.
All works fine.
The Windows is bacula-enterprise-win64-7.0.5.
But if i enable Vss, i have a system call Fail for the 3 others.
10 matches
Mail list logo
