Question about DB Backups
Using Jamroom
I can see my media folders numbered 1-15, with the newest one being from 2/15. I'll get back to the idea that my site hasn't fully backed up (media) yet.
My concern at the moment is I'm not seeing the DB backed up. I kick off a manual backup of the database only, and I don't see it go into S3.
I reloaded the module with similar result.
I dont see anything out of the ordinary in the logs, but next to the "manual backup completed" log in PHP, I click the "!" button to the right and I get this output:
Message [xxxxxxx]: manual system backup started
Date 02/17/14 13:58:25
IP Address xx.xx.xx.xx
URL /
Memory 3MB
Data
ffmpeg version N-50408-gdc666d3 Copyright (c) 2000-2013 the FFmpeg developers
built on Feb 28 2013 23:01:11 with gcc 4.3.2 (Debian 4.3.2-1.1)
configuration: --enable-shared --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --cc=cc --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame
libavutil 52. 17.103 / 52. 17.103
libavcodec 54. 92.100 / 54. 92.100
libavformat 54. 63.102 / 54. 63.102
libavdevice 54. 3.103 / 54. 3.103
libavfilter 3. 41.100 / 3. 41.100
libswscale 2. 2.100 / 2. 2.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 2.100 / 52. 2.100
[mp3 @ 0x106435e0] Format mp3 detected only with low score of 1, misdetection possible!
[mp3 @ 0x10643f20] Header missing
[mp3 @ 0x106435e0] decoding for stream 0 failed
[mp3 @ 0x106435e0] Could not find codec parameters for stream 0 (Audio: mp3, 0 channels, s16p): unspecified frame size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mp3 @ 0x106435e0] Estimating duration from bitrate, this may be inaccurate
/home/xxxx/public_html/data/media/1/152/jrAudio_606_audio_file.mp3: could not find codec parameters
I dont know how that's related... Can I validate anything else to try to get this working?