Centova Technologies Forum

Centova Cast v3 => General discussion => Topic started by: My Auto DJ on June 27, 2012, 11:33:45 am

Title: Backups
Post by: My Auto DJ on June 27, 2012, 11:33:45 am
I think I read somewhere there was a backup script? If not how would you recommend we run backups, rsync ?   
Title: Re: Backups
Post by: Centova - Steve B. on June 27, 2012, 09:53:04 pm
Yup, check /usr/local/centovacast/extra/backup.sh. :)
Title: Re: Backups
Post by: Centova - Steve B. on June 27, 2012, 09:58:48 pm
Whoops, that hasn't been updated for v3 yet.  It just needs /home/centovacast/ replaced with /usr/local/centovacast/ and /vhosts/ replaced with /var/vhosts/ -- do a search/replace and it should work fine with v3.

I'll update this script for the next build but we have a proper backup system in the works that is able to provide per-account backups/restoration (as well as backing up an account and restoring it to a different Centova Cast installation) which will eventually replace this.  It's unfortunately a very complicated procedure behind the scenes (mainly due to the fact that ID numbers have to be stripped at backup time, then unique ID numbers reintroduced at restoration time, and everything has to maintain its referential integrity) so it won't make the initial 3.0 release, but hopefully will be available at least for testing in one of the subsequent point releases.


Title: Re: Backups
Post by: My Auto DJ on June 28, 2012, 05:36:38 am
Yes I do understand that all my other Centova servers all used cPanel/WHM so I was able to set up automated backups.
I would be willing (and I am sure others) to a  pay-per-month or even a one time fee for some type of addon-on for a automated script that would allow me and my clients to set up backups, download backups, schedule, send to local or remote server, and manage their backups right in their Centova Panel, that would be a great selling feature and also save lots of time. That is one valuable lesson I have learned in the past, backups are very important and you just sleep better @ night! Guess this should be moved to feature request.
Title: Re: Backups
Post by: Gother on July 02, 2012, 01:25:12 am
Can we know what files or directories are backup and where ?
Title: Re: Backups
Post by: My Auto DJ on March 17, 2013, 01:27:56 pm
Any updates on this Steve?
Title: Re: Backups
Post by: Centova - Steve B. on March 19, 2013, 01:38:17 am
I'm actually just going to post this here for now, rather than in the manual, because technically it's still experimental.

So to make this clear: YMMV, this may break, you may lose all your data, your cat may become impregnated, errors may occur, etc.

That said, the v2-to-v3 import utility is actually built on top of the backup/restore functionality in v3, so it has indirectly received a fair bit of testing and should be reasonably usable.

Creating a Backup

The command to back up an account is:
Code: [Select]
/usr/local/centovacast/bin/ccmanage backup --username=USERNAME
USERNAME is, of course, the username of the account to backup.

The available parameters are documented in the backup API reference (http://www.centova.com/doc/cast/internals/API_Reference/system_class_method_reference#account_backup).  (For example, to use the "nocontent" argument documented in the API reference, pass the --nocontent=1 parameter to the backup command).

Restoring a Backup

To restore a backup, use:
Code: [Select]
/usr/local/centovacast/bin/ccmanage restore --filename=FILENAME --rpchostid=RPCHOSTID
FILENAME is the full pathname to the backup file to restore, and RPCHOSTID is the ID number of the server you want to restore it onto.  If you only have one server, use --rpchostid=1.  If you have multiple servers, check the Management->Hosts page in the admin area for the ID numbers.  (Hover over the "Edit" link -- the ID is at the end of the URL.)

The available parameters are documented in the restore API reference (http://www.centova.com/doc/cast/internals/API_Reference/system_class_method_reference#account_restore).

General Information

An account backup is just a zip file.  No crazy proprietary formats.  A backup contains all the user's files (all of them, including the server/source configuration files, media files, logs, etc.), a database dump in a custom format internal to Centova Cast (which is necessary since a standard SQL dump would cause key conflicts upon restoration), and some metadata files.

Backups contain ALL data relevant to the account -- the account configuration, bandwidth limits/disk quota settings, statistics, media files, playlists, etc.

If the user has a lot of files, the backup will be huge and will take ages to create.  You may consider using the --nocontent and/or --nologs parameters to omit the var/spool/ and var/log/ directories from the backups, and then use rsync or another efficient mechanism to externally backup the users' media files to another machine.  You'll find that that's a LOT faster than including them in the backups -- ZIP compression of media files (or any general-purpose compression, really) is very slow and provides a very poor compression ratio.

Backups can be created on one machine and restored to the same machine, or copied to another machine and restored there.  During restoration, Centova Cast will change the IP address to the local machine's IP address, and will change the port (if needed) to an available port, but everything else will remain unchanged and should yield a copy of the account on the new server that is completely identical to the original.

Backups are cryptographically signed using a key that's unique to your server.  By default, the "restore" command will reject any backups that weren't created by your server.  This is so that (in future, when we put the backup/restore functionality into the UI) users won't be able to restore backups created on other servers that have configurations not permitted on your server.  You can bypass this (as admin) with the --novalidate parameter to restore a backup from another server.

Enjoy, and if you encounter bugs, report them. :)
Title: Re: Backups
Post by: mikels on March 19, 2013, 06:28:33 am
Thanks. But isn't any way to make a global backup to move all the data to another server? For example, in v2, backup the vhost dir and export the full database...
Title: Re: Backups
Post by: My Auto DJ on March 19, 2013, 06:54:56 pm
We can right now just go into the database by clicking on the manage database under utilities, then export / save the entire DB, but a more complete backup option, or even as MIKELS said, using something like RSYNC to move the backups to another server right in the panel would really help me sleep better @ night, even automate them using a cron -- I think I already recommended it in the feature request though
Title: Re: Backups
Post by: Centova - Steve B. on March 27, 2013, 02:17:53 pm
Thanks. But isn't any way to make a global backup to move all the data to another server? For example, in v2, backup the vhost dir and export the full database...
Well, yes, you can of course do the same thing under v3.  Dump the database, and take a snapshot of /usr/local/centovacast/var/vhosts.

And yes, there is already an automated script to make a full backup and rsync it to a remote server:
Code: [Select]
/usr/local/centovacast/sbin/simplebackup --host=remote.example.com --port=22 --username=root --path=/path/to/store/backups/
You'll probably also want the --delete option, but run it with --help first to see what that does and understand the risks.
Title: Re: Backups
Post by: DJFire_CFR on June 01, 2013, 11:49:34 am
This backup utility does work right?

When I try to do a backup on an account, I get the following:

Code: [Select]
[INF] Creating database backup
[INF] Creating database dump /usr/local/centovacast/var/tmp/cc-app/database-usernamehere_20130601-114749_51aa41d539b5f.ccsql
[INF] Creating backup manifest
[INF] Creating backup archive
Result: ERROR Socket error while receiving command response

What would be causing that socket error ?
Title: Re: Backups
Post by: My Auto DJ on June 01, 2013, 12:22:13 pm
I have not been able to get it to work either, it's been a while since I tried but I think I had the same error messages
Title: Re: Backups
Post by: DJFire_CFR on June 01, 2013, 12:37:57 pm
Well, for some reason it seem to have fixed itself..

When I went looking around to see if a file was created somewhere, I did find one.. under 

/usr/local/centovacast/var/vhosts/username/.backup

then after transfering it to another server.. I tried restoring, but seems i did something wrong, cause it said the zip file wasnt found.. So I went back over to the original server, ran the back up again, and its going through the process now..

Now I just got to figure out how to get this backup to restore on another server.  I did read the posts about that said rsync.. but im not keen on how to use rsync.. =\


After it completes the backup fully, it puts it here:

/usr/local/centovacast/var/backups/vhosts/
Title: Re: Backups
Post by: DJFire_CFR on June 03, 2013, 11:42:15 am
Well, I got closer with this...

but when using  --novalidate=0

I get a mismatch error, as if its not even acknowledging it

Code: [Select]
/usr/local/centovacast/bin/ccmanage restore --filename=/usr/local/centovacast/var/backups/vhosts/backup-username_20130601-123518_51aa4cf6da626.zip --rpchostid=1 --username=username --novalidate=0


Results in:
Code: [Select]
[INF] Extracting backup archive ...
Result: ERROR Could not unpack backup file: Signature verification failed: Signature mismatch
Title: Re: Backups
Post by: My Auto DJ on June 03, 2013, 11:46:29 am
I messed with it over the weekend a little, seemed to just hang, tried multiple Centova servers and remote servers never got it to work
Title: Re: Backups
Post by: DJFire_CFR on June 03, 2013, 02:32:14 pm
I got it working great now.  :)


tested it out on 1 account, and it worked pretty much perfectly... just had to make 2 changes after the restore.

Just now gotta figure out the reseller accounts... and then I'll be golden.
Title: Re: Backups
Post by: DJFire_CFR on June 07, 2013, 03:30:07 pm
Is there a way to do multiple users, not an entire server, but say like 5-6 users...

Would you just do it as  --username=USERNAME --username=USERNAME etc?

Or is there a specific way to do multiple users
Title: Re: Backups
Post by: bbrink on September 21, 2013, 01:43:22 pm
Well, I got closer with this...

but when using  --novalidate=0

I get a mismatch error, as if its not even acknowledging it

Code: [Select]
/usr/local/centovacast/bin/ccmanage restore --filename=/usr/local/centovacast/var/backups/vhosts/backup-username_20130601-123518_51aa4cf6da626.zip --rpchostid=1 --username=username --novalidate=0


Results in:
Code: [Select]
[INF] Extracting backup archive ...
Result: ERROR Could not unpack backup file: Signature verification failed: Signature mismatch

How did you solve this?
Title: Re: Backups
Post by: DJFire_CFR on September 21, 2013, 04:11:29 pm
Just use  --novalidate
Title: Re: Backups
Post by: Jim on August 04, 2014, 11:17:50 am
Backing up and restoring to the local server (rpchostid=1) works fine but trying to restore to a different server (rpchostid=2) gives the error "Backup file does not exist". I've also tried moving the backup file to the different server and it gives the same error.

root@cc3:~# /usr/local/centovacast/bin/ccmanage backup --username=backuptest
Enter password for admin:
[INF] Creating database backup
[INF] Creating database dump /usr/local/centovacast/var/tmp/cc-app/database-backuptest_20140804-185544_53dfc9205d7a2.ccsql
[INF] Creating backup manifest
[INF] Creating backup archive
[INF]   Compressing backuptest/.backup/database-backuptest_20140804-185544_53dfc92060b88.zip (1466 bytes, file 1/33)
[INF]   Compressing backuptest/etc/source.conf (2102 bytes, file 33/33)
filename: "/usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip"
Result: OK Created backup

root@cc3:~# /usr/local/centovacast/bin/ccmanage restore --filename=/usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip --username=newbackup --rpchostid=2
Enter password for admin:
[INF] Processing backup /usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip
Result: ERROR Backup file /usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip does not exist

root@cc3:~# ls -lat /usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip
-rw-rw---- 1 ccuser centovacast 47215 Aug  4 18:55 /usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip

Has anyone else successfully managed to backup from one rpchost id and restored it to another ?
Title: Re: Backups
Post by: Centova - Steve B. on August 04, 2014, 12:01:45 pm
I've also tried moving the backup file to the different server and it gives the same error.
You may want to try that again, as the error in the example you quoted below is caused by the backup file not existing on rpchostid number 2 (because you haven't copied it there).


root@cc3:~# /usr/local/centovacast/bin/ccmanage backup --username=backuptest

The shell prompt here shows that you're running the backup command on a machine named "cc3", which corresponds to rpchostid number 1 ...


root@cc3:~# /usr/local/centovacast/bin/ccmanage restore --filename=/usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip --username=newbackup --rpchostid=2

... but here, you're telling Centova Cast to try to find that backup on a different server (rpchostid number 2).  But since you haven't copied it to server 2, Centova Cast cannot, of course, find it there.


root@cc3:~# ls -lat /usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip
-rw-rw---- 1 ccuser centovacast 47215 Aug  4 18:55 /usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip

All you're doing here is demonstrating that the backup file exists on server 1.  That does absolutely no good if you're trying to use the backup file on server 2.
Title: Re: Backups
Post by: Jim on August 04, 2014, 12:15:29 pm
Thanks for the prompt reply Steve.

I did have the file on the rpchostid 2 server but it was in /root/. I moved it to /usr/local/centovacast/var/backups/vhosts/ and it worked.
Title: Re: Backups
Post by: Centova - Steve B. on August 04, 2014, 12:19:03 pm
I did have the file on the rpchostid 2 server but it was in /root/. I moved it to /usr/local/centovacast/var/backups/vhosts/ and it worked.

It's fine to have it in /root, but if so you need to use --filename=/root/backup-backuptest_20140804-185544_53dfc9206159d.zip in the restore command.  Centova Cast will use whatever filename you give it, so if you specify --filename=/usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip then Centova Cast is going to look for /usr/local/centovacast/var/backups/vhosts/backup-backuptest_20140804-185544_53dfc9206159d.zip.
Title: Re: Backups
Post by: Jim on August 04, 2014, 12:20:03 pm
Great. Thanks for the clarification.  8)
Title: Re: Backups
Post by: Jim on August 27, 2014, 10:16:14 am
I've been doing some more testing with the backup and restore functionality but I'm running into some issues again. I exported an account from CCv2 to the CCv3 with the following command line :

Code: [Select]
./export.sh --local=0 --oldpass=xxx --newpass=xxx --host=control.internet-radio.com --sshport=2222 --accounts=xxxusername
Works great and imports correctly into CCv3. I then backed up the account with the following :

Code: [Select]
/usr/local/centovacast/bin/ccmanage backup --username=xxxusername
I wanted to take advantage of the ability to change username during restore so I deleted the account xxxusername and tried to restore with the following command which according to the API specs should allow me to change the username from xxxusername to xxxNEWusername when it re-imports :
 
Code: [Select]
/usr/local/centovacast/bin/ccmanage restore --username=xxxNEWusername --filename=/usr/local/centovacast/var/backups/vhosts/backup-xxxusername_20140827-000918_53fd139e29450.zip -rpchostid=1 --dryrun=1
I got the following error though :

Code: [Select]
[INF] Processing backup /usr/local/centovacast/var/backups/vhosts/backup-xxxusername_20140827-000918_53fd139e29450.zip
[INF] Extracting backup archive ...
[INF] Reading manifest ...
[INF] Backup was created for user xxxusername at 2014-08-27 00:09:18
[INF] Restoring data files ...
[INF] Unpacking database ...
[INF] Importing database ...
[INF] Imported new account ID 1
Result: ERROR Unable to access imported account: Unable to access account for _xxxNEWusername: Invalid username or password

So next I thought that perhaps the problem was me changing the username while restoring but it gives the same error when I restore with the same username. I also tried it without --dryrun=1 and the same again.

Any suggestions ?
Title: Re: Backups
Post by: heisenberg on August 27, 2014, 10:44:03 pm
Very interesting. I thought there was no way to rename an account in Centova - we've "renamed" them by deleting old account and creating a new one...
Title: Re: Backups
Post by: Jim on September 03, 2014, 07:26:42 am
Yeah for sure. Us too. We do get requests and have previously just setup new accounts but of course you loose all the reporting history and settings. I noticed this thread and bookmarked it until I could give it more of a test but there seems to be issues with it.

Very interesting. I thought there was no way to rename an account in Centova - we've "renamed" them by deleting old account and creating a new one...
Title: Re: Backups
Post by: My Auto DJ on October 08, 2014, 06:35:58 am
Backups do not restore, and if the user has more than about 8GIG of files the backup fails
http://prntscr.com/4u6tzi
Title: Re: Backups
Post by: DJFire_CFR on December 12, 2014, 11:27:25 pm
The only way I found in getting around that "issue", is by just backing up the account itself using --nocontent   then taring up the music/image, etc by itself, transferring everything, restore the account first, then untar the other stuff in the restored folder, then running  permissions and indexing music.  Bit of a process, but only way "I" have done.
Title: Re: Backups
Post by: heisenberg on June 28, 2015, 09:40:11 am
It seems that creating a backup on one server and restoring it on another doesn't work. After attempt to restore it, it just says that it can't access the new account.

By the way, is it possible this failed attempt to move an account somehow corrupted the database? Just asking, everytinhg seems to be working, just need to make sure.
Title: Re: Backups
Post by: Centova - Steve B. on June 29, 2015, 04:24:02 pm
FYI you're resurrecting a really old thread. Account rename has been supported for a couple of versions now, the archive size limit has been corrected for several months, etc. (although it's a bit silly to archive up gigs of MP3s anyway, given that they won't compress any further; --no-content and creating a separate uncompressed tarball is the ideal way to do it).

It seems that creating a backup on one server and restoring it on another doesn't work.
As long as you've disabled signature verification it should.

After attempt to restore it, it just says that it can't access the new account.
It's pretty much impossible to diagnose this with a paraphrased error message.  Feel free to open a ticket with the helpdesk if you'd like us to take a look at the restored account for you.  (We'd need root access to your server via SSH, though.)
Title: Re: Backups
Post by: heisenberg on June 30, 2015, 06:23:48 am
I wasn't saying anything about renaming the account.

I planned to use the backup and restore feature to move client's accounts from one server to another. The servers are different Centova installations (not master and control daemons) and different physical machines. Is it possible, or is there a better way?

For diagonosing the problem, I don't really feel comfortable giving out root password. There should be another way, e.g. tell what information you need and I'll provide it.
Title: Re: Backups
Post by: Centova - Steve B. on July 02, 2015, 04:47:55 pm
I wasn't saying anything about renaming the account.
No, but that was the last issue discussed in this thread over 6mos ago.  What I meant was just that it'd be more appropriate to create a new thread for this issue.

I planned to use the backup and restore feature to move client's accounts from one server to another. The servers are different Centova installations (not master and control daemons) and different physical machines. Is it possible, or is there a better way?
That should work fine, and is certainly one of the intended purposes of the backup/restore feature.

For diagonosing the problem, I don't really feel comfortable giving out root password.
We don't need your root password, just root access.  Public key auth works just as well.

There should be another way, e.g. tell what information you need and I'll provide it.
The problem is that I have no idea what the issue could be -- you have provided neither the commands you're using for backup/restore nor the error message you're receiving, so I have no idea where to even begin looking.

Even with that information, when troubleshooting problems like this it's usually a process of checking lots of things that end up being unrelated before coming across the cause.  The amount of back-and-forth that would require without hands-on access usually makes it impractical.

In any case, regardless of how we proceed, you'll get much faster results via the helpdesk as I said, since I don't regularly monitor the forums.

Title: Re: Backups
Post by: NOcentov4a on July 05, 2015, 10:55:13 am
 >:(
Centovacast once again pissing every one off :-( ... why cant you just behave like normal Fing human beings WE want a FULL BACK UP option that works that dumps and restores every thing COHERANTLY !!! GRRRRRR FFFSSS

not some broken RSYNC garbage bash script that was coded by a 5 year old whom does not comprehend un-escaped strings are bad .. or can not fathom how to code it with out avoid such triviality's
 
"ccmanage backup" once again you attempt to insult us... how is this supposed to help any one .. copy one account at a time...??? this is 2015 get a god damn grip

any time some one asks for help you attempt to question there motives and methods and write off the complaint as admin error.. and try and side step your responsibility to create a reliable usable system that can migrate easily and swiftly.. 

I am personally sick of it .. you make every thing tedious and difficult needlessly ... I have to migrate to new servers and all you've bloody done is fight tooth and nail with people to this end, even down to signing up .. you demonstrate you complete utter contempt for your clients by forcing them to use diabolical mixed upper and lower case passwords with multiple captures to even communicate with you via forums its sicken and pathetic and time wastage that only a stupid greedy and selfish company such as your selves could conjure up .. THANKS FOR NOTHING been nothing but a nuisance over the years and caused considerable upset to my clients.. and here we go again !!

Licencing shambolic
Billing shambolic
Backup/migrate shambolic
Updates shambolic

and don't you worry yourselves .. I wont be using centovacast when a suitable competitor comes to the market
Title: Re: Backups
Post by: heisenberg on July 08, 2015, 02:39:49 am
Thanks for your reply, Steve. I'll contact Helpdesk when I run into this issue again, with more information.
Title: Re: Backups
Post by: NOcentov4a on July 09, 2015, 06:52:30 pm
!!!! >:(  ....

# /usr/local/centovacast/bin/ccmanage restore --username=atr --filename=/usr/local/centovacast/var/vhosts/backups/vhosts/backup-atr_20150708-175629_559d9c8df1e25.zip --reseller=unityradionet --rpchostid=1 --novalidate=1

Enter password for admin: xxxxxxxxx
[INF] Processing backup /usr/local/centovacast/var/vhosts/backups/vhosts/backup-atr_20150708-175629_559d9c8df1e25.zip
[INF] Extracting backup archive ...
[INF] Extracting /usr/local/centovacast/var/vhosts//.restore_atr_559f245ea6636//database.zip | 133999 bytes, file 93/92
[INF] Extracting /usr/local/centovacast/var/vhosts//.restore_atr_559f245ea6636//atr/var/spool/media/Energy 52 - Cafe Del Mar (Deadmau5 Remix) clubfoxs.blogspot.com.mp3 | 15016400 bytes, file 164/92
[INF] Extracted 1 files
[INF] Reading manifest ...
[INF] Backup was created for user atr at 2015-07-08 14:56:29
Result: ERROR This host does not support the software required by the account to be restored (ShoutCast,sctrans)


cant restore and cant install what it wants :(
Title: Re: Backups
Post by: NOcentov4a on July 09, 2015, 07:54:16 pm
ok I have some advise for any one attempting to migrate:

1) If you have reinstalled a 64bit distribution you need to install libc6-i386 to make 32bit shoutcast 1.x work also you need to own the file sc_trans to root/user you want it to run as and set it to executable 

2) you need to enable sctrans1 by pointing it to sc_trans2 *not sure how to get sc_trans1* but i think its inconsequential as sc_trans2 works as sc_trans1  did and and thus is backward compatible... to do this use the enable_package command

3) now you can restore all your streams with ccmanage regardless weather they are shoutcast1/2 or used sctrans1/2 as far as they were concerned




Title: Re: Backups
Post by: Roger on July 13, 2015, 07:00:53 am
ok I have some advise for any one attempting to migrate:

1) If you have reinstalled a 64bit distribution you need to install libc6-i386 to make 32bit shoutcast 1.x work also you need to own the file sc_trans to root/user you want it to run as and set it to executable 

You don't need to manually make sc_trans executable, all you need to do to fix all permissions is run /usr/local/centovacast/sbin/fixperms, besides sc_trans it automatically installed by Centova Cast and set to the proper permissions, unless you're talking about sc_trans v1, in which case this might be necessary but only to restore stations that already use sc_trans v1.

2) you need to enable sctrans1 by pointing it to sc_trans2 *not sure how to get sc_trans1* but i think its inconsequential as sc_trans2 works as sc_trans1  did and and thus is backward compatible... to do this use the enable_package command

Sc_trans v2 is NOT backwards compatible with sc_trans 1, although it might kind of work, there are several key differences which may break a system with large number of accounts. You shouldn't do this unless you are desperate to recover a station or station that originally used sc_trans v1 and you no longer have the sc_trans v1 binary.

3) now you can restore all your streams with ccmanage regardless weather they are shoutcast1/2 or used sctrans1/2 as far as they were concerned

Note that this is only recommended if you are moving individual account, for migration of an entire installation you should use the recommended procedure described at http://www.centova.com/en/faq/cast3/information/migrating_a_centova_cast_installation_to_another_server


HTH
Title: Re: Backups
Post by: NOcentov4a on July 14, 2015, 03:03:56 am
ah yeah I forgot about fixperms at that point thanks for pointing that out
secondly centovacast does not install SCTRANS_1 using  the update command:

perhaps you might want to run that after every install and every update command when adding additional software

I CITE:
http://www.centova.com/doc/cast/installation_manual/07_adding_additional_software
where is sctrans1 in that .. ???

I remember I had to modify my old centovacast installation to actually make it able to add sc_trans1 and I hunted down the binary and after some extensive misisoning I found it..  so I am not sure what on earth your talking about on that one ;/

go ahead and try.. you should know you wrote the software right?

further more seeing as there is no other known or offered way to get the accounts up and running in this scenario people will have no choice its not about desperation its about no choice caused by a limitations of the current backup/restore process and only further compounded by the lack of obvious methods to then change the transcoder to something else after the fact  period.

thanks you like the meerkat
Title: Re: Backups
Post by: Roger on July 14, 2015, 10:03:47 pm
secondly centovacast does not install SCTRANS_1 using  the update command:

sc_trans v1 has been deprecated for a number of years now, although we maintain legacy support for old station that were originally setup to use sc_trans v1 as a source, all you need is a backup of the binary from your old installation.

I CITE:
http://www.centova.com/doc/cast/installation_manual/07_adding_additional_software
where is sctrans1 in that .. ???

Centova Cast isn't bundled with any third-party software due to licensing issues, our automated installer downloads all third-party software from its official download sites respectively. sc_trans v1 is not installed because it hasn't been available for download in a very long time.

I remember I had to modify my old centovacast installation to actually make it able to add sc_trans1 and I hunted down the binary and after some extensive misisoning I found it..  so I am not sure what on earth your talking about on that one ;/

Just to clarify, when I said "sc_trans it automatically installed by Centova Cast and set to the proper permissions, unless you're talking about sc_trans v1", It is pretty clear I was NOT talking about sc_trans v1, and so I am NOT saying that sc_trans v1 will be installed automatically.

It should also be noted that sc_trans v1 doesn't support scripted playlists, meaning that it won't support most of the advanced features of Centova Cast's autoDJ, that is mostly why its use is discouraged, if however, you wan or need to continue using it, and you have the binary, you're more then welcome to do so.


HTH