On 4/25/14 5:16 AM, Rob Landry wrote:
If you don't backup/restore the database, you have to re-import all
the audio files. All the metadata is in the database; there will be
none on the files, so it will all have to be put in manually.
Moreover, if you have markers in your files they will need to be
re-created, too.
Just my .02, but I've had really good luck with this too. Decided
recently to bring all our stations under the BA from various
installations for consistency. The backup/restore has been a piece of
cake and saved tons of time. I just migrated 3 systems over the last
couple of days.
Couple words of advice and maybe a tip from just having done this:
1) backup the database twice to two separate files (I'm a redundancy nut
when it comes to this stuff). That way, if something is wonky in one,
you'll have a second to try, though I've never had one be bad.
2) if you're /var/snd is mounted to it's own hard drive (ie. your audio
files are on their own hard drive separate from the OS drive), just
unplug that drive from the computer while you install the new broadcast
appliance, since the appliance by default will format all drives plugged
in (you can modify it to not do that, but in the V1, I did that and it
still formatted both my drives). Then, after you have the V2 up and
running, just plug it back in and edit your /etc/fstab to put the UUID
of the drive and /var/snd mount point in and you'll be good to go after
issuing a mount -a as root. (Also make sure to change the /var/snd that
the appliance creates to something else)
3) you'll have to check user/group on your audio files to make sure they
match what RD is looking for. Being from different systems, i had to use
the good chown command, but once done everything was right there.
4) make sure your hostname matches the host in rdadmin either by
creating a new host in rdamin to match the machine or match the machine
to the host you imported by changing /etc/sysconfig/network
5) and make sure you point a 127.0.0.anythingbut1 to your hosts in
/etc/hosts
This last one may or may not be necessary, but I did all these and
didn't have 1 even minute problem as far as rivendell was concerned.
The only problems I had were not directly appliance related, they were
due to NVIDIA drivers I needed (NVIDIA is a real pain on linux) and due
to trying to install the OS on small hard drives. If you're using a
secondary drive for audio and your primary drive is less than 300Gb,
you'll have to create the install partitions manually during the install
process. The appliance doesn't like anything smaller than 300Gb, but
that's in specs so was to be expected. Other than that, you have to do a
little searching if you want the polymer look from earlier versions as
well as qt3-config to make it work but google is your friend. If I get a
little time to do it, I'll try to throw them one of my servers and link
to them from the wiki so people don't have to do the digging like I did.
The machines we just converted all had in the neighborhood of 40-50k
songs in them and all made the migration without issue including all
data and markers in place. It's really a great and easy process. Fred
and the gang have done a great job of making this work very well for you.
Anyway, sorry for the long post, but maybe that will help a few folks
out a little.
Tim
Owner, engineer, jock of all trades
Kat Kountry Radio
EpicMix Radio
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
