Interworx 3 and backup, documentation?

[Dj-Grobe]

I open this post, for request to sombody form iworx repply and post all info available possible.

Interowrx have now scheduled and autorotation backup?

For backup all server, have some shell command? continue on the old and clasic way?

How the backup handle the resellers?

When restore, site come form reseller account and account reseller no exist, interowrx ask to create taht reseller?
Some command for skip that answer and just asme always is YES?

I apreciate all info, available soon i have to move lot of sites form iworx to new servers and want to find some easy way to move the resellers : )

Please if some shell command change, and more options are availabla when restore, please put here in this post : )

i apreciate if can put all info avilable about this, this is a feature i saty wating for long time :)

Thankyou !

[IWorx-Socheat]

Interowrx have now scheduled and autorotation backup?

InterWorx always had the capability of scheduling backups from the SiteWorx interface. NodeWorx users will still need to use the cron interface or you can schedule it in cron from the shell.

We try to stick to the Unix philosophy of making our scripts do one thing, and do it well. So, auto-rotation isn't a part of the command line backup utility. However, the backup command has a lot of new features, and you have more control over the the naming format of the final file, using the new --filename-format parameter (similar to PHP's strftime). For example, the following:
--filename-format"dj-grobe-%D-%a"

would translate to backup files named:

dj-grobe-domain1.com-mon.tgz
dj-grobe-domain2.net-wed.tgz
etc, etc


So, it's even easier now to script your own auto-rotation solution.

For backup all server, have some shell command? continue on the old and clasic way?

Yes, this is the same as in iworx 2.1.x. backup.pex --domains all

How the backup handle the resellers?

backup.pex --domains all --reseller-id=20

will backup all domains under reseller #20.

backup.pex --domains 'a.*\.net' --reseller-id=20

will backup all domains that start with 'a' and end in '.net' under reseller #20. :)

When restore, site come form reseller account and account reseller no exist, interowrx ask to create taht reseller?
Some command for skip that answer and just asme always is YES?

Reseller's are uniquely identified by their email address. In the interface, you'll have the option to "Create" the reseller from the backup file. What this does is it checks the reseller info that's in the backup file and does the following:
- If you specified to create the reseller during import, and the reseller email stored in the backup *does not* exist on the server, the reseller will be imported automatically.
- If you specified to create the reseller during import, and the reseller email stored in the backup *does* exist, the account will automatically be imported under that reseller.

Similar thing happens on the command line when you use import.pex with the --create-reseller option. This makes it easy for you to restore a complete reseller account, either from the NodeWorx interface or from the command line.

Please if some shell command change, and more options are availabla when restore, please put here in this post : )

We will update the documentation as soon as possible. :)

[Dj-Grobe]

One point not really clear how work

If i run backup using this way:

backup.pex --domains all

This way backup resellers too? and when want restore can use the option --create-reseller

or need run on this way for all resellers om the server?
backup.pex --domains all --reseller-id=XX


Mi idea its make complete backup of all server , i make that abckups for restore ounder disaster situations like loose complete HD, and need easya dn faster way to restore all sites.
Usually for masive imports just put all backups file on folder of server to restore and run simple xsript like this:


for a in *.gz ; do
mport.pex --archive=/home/backup/$a --control-panel=iworx --ip-address=xx.xxx.xxx.xx
done


Now can run backups using backup.pex --domains all
and then restore absolutly all in automatic adding the option --create-reseller to my masive restore script?

[IWorx-Socheat]

backup.pex --domains all

This will backup all accounts on the box, including all reseller accounts. If you have 3 resellers with 25 accounts each, and the master nodeworx user has 25 accounts, the total number of backups would be 100 backups.

This way backup resellers too? and when want restore can use the option --create-reseller

Yes, each siteworx account backup also has the information needed to restore the reseller info. The import.pex --create-reseller parameter is what you use to import the reseller information.

backup.pex --domains all --reseller-id=XX
This will backup all the accounts for ONLY the given reseller.

Mi idea its make complete backup of all server , i make that abckups for restore ounder disaster situations like loose complete HD, and need easya dn faster way to restore all sites.
Usually for masive imports just put all backups file on folder of server to restore and run simple xsript like this:


for a in *.gz ; do
mport.pex --archive=/home/backup/$a --control-panel=iworx --ip-address=xx.xxx.xxx.xx
done


Now can run backups using backup.pex --domains all
and then restore absolutly all in automatic adding the option --create-reseller to my masive restore script?

Yes. That should work.

[Dj-Grobe]

Socheat i thinking about how the system work realted to reseller ad i think houston we have a problem !!

Imagine this scenario:

Whats up if i move sites form one interworx box, to other interworx box...where same reseller ID EXIST?

Sites are automatically asigned based on the reseller ID to wrong reseller, if same ID reseller exist on the server where i move?

[IWorx-Socheat]

Accounts are automatically assigned by reseller ID only if you use the --create-reseller option. Otherwise, the reseller information in the backup file is ignored. Then, you have two options:

1.) Import with the --reseller-id= option, which will import the account under the specific reseller you specified.

2.) Import without the --reseller-id option (and without the --create-reseller option), and it will automatically import under the master reseller.

[Dj-Grobe]

perfect.......
How move on interworx 3, acount from MASTER to any reselelr id i decide?

[NEXCESS.NET (Greg)]

If you go to the SiteWorx > Accounts page and click Edit next to the account you'd like to move, you'll see a Reseller: with a dropdown next to it with all the resellers on the server. Choose the dropdown you'd like to move that account to, then click the Save button

[Henrik]

A backup-related question:

If a siteworx (or reseller) choose to do a remote backup via FTP/SSH, will the bandwidth used for this remote backup count to this user's / reseller's quota?

[Dj-Grobe]

Based on waht i know....no
Anyway wait for iworx staff confirmation

[Dj-Grobe]

Th id for resellers is the email?

Interworx not unse ID for resller based on number when restore?

Please confirm this, because i move multiple reseller from diferent servers to one common server.
If the reseller its ID number based this itsa trouble, but if reseller its mail based : ) this can be maded really faster : )

Please i apreciate if can cofirm this somebody form interworx.

[IWorx-Socheat]

I assume you are referring to the backup.pex command. When you use the --create-reseller option, it will use the email address stored in the backup file. When you use the --reseller-id <number> option, it uses the reseller ID number that you just passed in.

[Dj-Grobe]

Ok imagine i have 2 servers, server a, where have 3 resellers, server b where have 3 resellers.

Ig i backup using domain all on both servers, and then restore an new server using command --create-reseller, all resellers are created correcltya nd sited reasigned in correct way?

[IWorx-Socheat]

Ok imagine i have 2 servers, server a, where have 3 resellers, server b where have 3 resellers.

Ig i backup using domain all on both servers, and then restore an new server using command --create-reseller, all resellers are created correcltya nd sited reasigned in correct way?

Yes, that is correct.

[pascal]

Hi,

Now with the structure-only backup option we will be able to just backup accounts structure only and choose our own solution to backup the data itself.

Ok, but I think it'd be great if Interworx could define wth precision which data has to be backuped. Tell for one domain :
- /home/accounts/domainname
- /var/lib/mysql/accounts_*

Is it enough ?

I continue to think that Interworx could provide "off the record" (like here in the forum) some perl/bash/php scripts as example to backups all accounts with different methods. All know that to have a good backup and recovery plan (of interworx data ONLY, not the server itself) is one of the most important thing and I think that Interworx could help their customers to set this plan by providing some scripts (even if I know it completly depends of the need of everyone. But some examples and scripts that could help the customers to perform:- A full backup - A full import of all accounts on a new box - A full migration from a box to another - would be great for the community).

No ? don't you agreee with this ?

Pascal

[IWorx-Socheat]

Ok, but I think it'd be great if Interworx could define wth precision which data has to be backuped. Tell for one domain :
- /home/accounts/domainname
- /var/lib/mysql/accounts_*


You'll also need to grab /home/accounts/var/domainname/mail. Structure-only backups only grab the email usernames, groups, aliases, and passwords. The actual email contents of each email account is considered data and not included in a structure-only backup. Also, if there's any files in the top level /home/accounts/ directory, you'll obviously want to grab that too.

I continue to think that Interworx could provide "off the record" (like here in the forum) some perl/bash/php scripts as example to backups all accounts with different methods. All know that to have a good backup and recovery plan (of interworx data ONLY, not the server itself) is one of the most important thing and I think that Interworx could help their customers to set this plan by providing some scripts (even if I know it completly depends of the need of everyone. But some examples and scripts that could help the customers to perform:- A full backup - A full import of all accounts on a new box - A full migration from a box to another - would be great for the community).

Sure, here are a few examples, using backup.pex from InterWorx v.3.0...

Backup Examples
This will create full backups of every SiteWorx account on the box, and store them in each SiteWorx account's standard location (/home/username/domain.com/iworx-backup/):
/home/interworx/bin/backup.pex --domains=all

This will create structure-only backups of every SiteWorx account on the box, and store them in each SiteWorx account's standard location (/home/username/domain.com/iworx-backup/):
/home/interworx/bin/backup.pex --domains=all --structure-only

This will create structure-only backups and save them in a central location (/backups):
/home/interworx/bin/backup.pex --domains=all --structure-only --output-dir=/backups

This will create structure-only backups and transfer them via SCP to a remote server (as specified in the /root/my-transfer.ini file):
/home/interworx/bin/backup.pex \
--domains=all \
--structure-only \
--xfer-ini=/root/my-transfer.ini
--xfer-method=scp

This will create structure-only backups, transfer them via FTP to a remote server (as specified in the /root/my-transfer.ini file), with the filename format of "domain.com.tgz":
/home/interworx/bin/backup.pex \
--domains=all \
--structure-only \
--filename-format "%D" \
--xfer-ini=/root/my-transfer.ini
--xfer-method=scp

You can then use rsync to rsync or rsnapshot to copy over /home and /var/lib/mysql to another server to grab the data files that the structure-only backup skipped. We personally use rsnapshot, and we backup mysqldump'd backups instead of the raw MySQL table files.

Import Examples

Let's say you had a hardware failure, and you re-installed the server and the box has the exact same IPs before and after the failure. If you had all the backups in the /backups directory (one backup file per SiteWorx account), you could import all the accounts, using the IP address stored in the backup file, using a bash script like this:


for backup_file in /backups/*.tgz
do
~iworx/bin/import.pex --create-reseller --control-panel=siteworx --ip-address=inifile --archive=$backup_file
done


If the IP addresses are different on the box (for example, migrating from one box to another), you would need to group the backups by IP


for backup_file in /backups/ip_group1/*.tgz
do
~iworx/bin/import.pex --create-reseller --control-panel=siteworx --ip-address=1.2.3.4 --archive=$backup_file
done

for backup_file in /backups/ip_group2/*.tgz
do
~iworx/bin/import.pex --create-reseller --control-panel=siteworx --ip-address=5.6.7.8 --archive=$backup_file
done


Or, if you are migrating boxes, you could use the mass import tool, which has many new improvements to make the process much easier.

If you are importing structure-only backups, you will then need to restore the database data, copy over the web site data, and email files to the appropriate locations. Full backups, obviously, will already have imported the database, website, and email data during the import.

[pascal]

Thanks Socheat it should help few peoples.

Personnaly we use the full backup in a standard location (like /backups), and don't plan to use the structure only backups as if you use it and do a rsync then a tar to save space it would be the same as a full backup in terms of usage and time (?)

But it's true that if you have a huge backups space on a Nas or San server it could be interesting to perform a structure only backups

As you know we've already done few full migration from a box to another and the main problem was to manually create the reselers and attach siteworx accounts to them. We're really happy to now have the ability to perform this directly with the backup command : Great !

If some of you plan to use the structure only backups it could be interesting to put here your scripts as example (of backups and import)

Thanks Socheat

Pascal

[pascal]

You can then use rsync to rsync or rsnapshot to copy over /home and /var/lib/mysql to another server to grab the data files that the structure-only backup skipped. We personally use rsnapshot, and we backup mysqldump'd backups instead of the raw MySQL table files.


Before V3 we also used Rsnapshot (which is great as you can also add a mysqldump script to it) but the import was more complicated (if you have not the same ip from box a to b for example). Now with the v3 and the structure only backups it might be interesting :)

Do you have some example with rsnapshot for the backup and how you'll import the accounts in a new box ?
Do you have some examples of MySQL backups script (I think it is the best method in case of your mysql server is not the same release between server A and B ) ?

It could be great to have a full script (in RPM for example) that do a full backup structure only + rsnapshot and one for importing the data !

Pascal

[IWorx-Socheat]

I personally like structure-only backups for really large accounts.

Also, it'll be far quicker, and less resource intensive, to backup all accounts and grab the data I can't easily backup (i.e., internal iworx data). Imagine that you have 300 accounts on your box, each between few hundred MB and few GB in size. Doing a full backup on all accounts could take a whole day to finish.

If instead you used rsync or rsnapshot to backup the data (which would be very quick after the first time it runs, since only changed files are copied), and you then did structure-only backups of all the accounts, this would finish much quicker.

But yes, you are right. There is more work to restore a structure-only backup, because after restoring the structure-only backup, you then have to copy the data over. But, at least you have the choice. :)

[IWorx-Socheat]

I should also clarify, this is what is considered *DATA*:
- Email files in /home/username/var/domain.com/mail
- Database data in /var/lib/mysql/username_*
- Website data in /home/username/domain.com
- Home directory data in /home/username
- Site log data in /home/username/var/domain.com/logs
- Web stats data in /home/username/var/domain.com/stats

All the above will not be included in the backup when doing structure-only backups. Everything else, is considered structure (rrd graphs, crontab, ssl, usernames, passwords, etc)

[Dj-Grobe]

Something its wrong with backups?
I testing transfer one simple site with just 11.31 MB storage !! and take more of 20 minutes !!!
Is use the panel...... after that 20 minutes ahve error failiure, but o clear on any place what is the error !!

I test with other sites and find the same!!


Now go to shell, create backup using:

/home/interworx/bin/backup.pex --domains=domanname.com --file-path=/root/

This simple task before upgarde to 3.0 take just 2 minutes for little sites.......now take long time.

After backup its generated i move the file to new server where i wnat restore, i move manually.....
I try restore and have failiure again !!

I stay desperate have to move really high number of sites this weekend !!

Something its wrong?
Why backup take absolutly incredible long time !!! with sites with just 20mb 15 mb and no high number of files .....before version 3 this take just 1 or 2 minutes per site !!

On this way make backup of server with 200 sites or more its imposible !!

If sombody from iworx, read, please tellme !! i think have to take a look on this toruble, please !

[Dj-Grobe]

I try with more sites........ all sites cant be imported return failure error !! when try import in other server, with same iworx version !

I asume now this its a bug ; (

[Dj-Grobe]

I opened emergency ticket for this !!

EDIT:

I CANT RESTORE SITES due aprently bug, i have ticket for tat opened right now.
Anyway i found aparently why the backup runing slow, i detect some sites are very little, but are very very very old.........and have 100000 of STATS FILES using 300 400 500mb !!
The backup should add option for skip, any log or stat data..........this in high percent of sites its not critical information, and create big torubels delaying amazing the backup !!!

Please add that feature asap !! its needed........on server with old sites, the backup can be a nightmare !!

Imagine right now i testing with site with just 13mb, but the stats are 545 mb !!! ad thousand of files !!

Anyway not understand why have error when try restore sites on my new servers !
Please iworx guy check te ticket !

[pascal]

I personally like structure-only backups for really large accounts.

Also, it'll be far quicker, and less resource intensive, to backup all accounts and grab the data I can't easily backup (i.e., internal iworx data). Imagine that you have 300 accounts on your box, each between few hundred MB and few GB in size. Doing a full backup on all accounts could take a whole day to finish.

If instead you used rsync or rsnapshot to backup the data (which would be very quick after the first time it runs, since only changed files are copied), and you then did structure-only backups of all the accounts, this would finish much quicker.

But yes, you are right. There is more work to restore a structure-only backup, because after restoring the structure-only backup, you then have to copy the data over. But, at least you have the choice. :)

You absolutly right about the time and resource usage the full backup take. We have 300 accounts and it takes 6 hours (100GB of data)

As soon V3 will be out, we'll try the structure only backups + Rsnapshot + Mysql backup script, if it is fine we'll give here the config of rsnapshot and why not a SRPM of a script that do this job

Just a last question about structure only backups. Tell we want to do a full backup, so we do :
1- A rsync or rsnapshot of /home (in /backups for example)
2- A backup of the Mysql database with a mysqldump (with rsnapshot and in /backups)
3- Perform a backup.pex with --structure-only in /backups (like /home/interworx/bin/backup.pex --domains=all --structure-only --output-dir=/backups )

Is that correct ?
Do you suggest to perform first the backups.pex or the rsync ?

Now we'd like to import all the accounts (tell we have the same Ip shem)

We just have to do something like
for backup_file in /backups/*.tgz
do
~iworx/bin/import.pex --create-reseller --control-panel=siteworx --ip-address=inifile --archive=$backup_file
done


This way, even if it was a structure-only backup ALL the reseler account will be created and all reseler's siteworx accounts will be created and attach to the good reseler ? Is it correct ?

I think about a new feature that could be very usefull.

The import command with --ip-address=inifile allows to restore accounts in the same IP defined in the backup file which is great, good !

You can also define your own ip adress with --ip-address=192.1.1.1, fine !

Indeed, if you are restoring all accounts on the same server the IP are the same, so the inifile is great, but if you are restoring/migratiing all accounts on a new server with different IP then you have to define which accounts has to be set on an IP.

It could be great to have the ability to backup only the accounts that are set on one IP. Like this it could be possible to backup these accounts in a special directory and so more easy to restore these accounts on an other IP, I mean :

Tell we have :
100 accounts on IP 111.168.1.1
100 accounts on IP 111.168.1.2
50 accounts on IP 111.168.1.3

It could be great to be able to backups these accounts like this :
/home/interworx/bin/backup.pex --domains=111.168.1.1 --structure-only --output-dir=/backups/ip-111-168-1-1
or
/home/interworx/bin/backup.pex --ip=111.168.1.1 --structure-only --output-dir=/backups/ip-111-168-1-1

or
/home/interworx/bin/backup.pex --ip=111.168.1.1 --structure-only --output-dir=/backups --filename-format "111-168-1-1-%D"


This way it would be very easy to know the IP of every accounts backuped and so more easy to restore/migrate these accounts on a new IP by doing something like this


for backup_file in /backups/ip_group1/*.tgz
do
~iworx/bin/import.pex --create-reseller --control-panel=siteworx --ip-address=1.2.3.4 --archive=$backup_file
done

or

for backup_file in /backups/111-168-1-1*.tgz
do
~iworx/bin/import.pex --create-reseller --control-panel=siteworx --ip-address=1.2.3.4 --archive=$backup_file
done



In fact, you give a good way to restore an account on a defined IP, so I think it could be a good idea to give the the ability to backup ALL accounts set on one IP, what do you think about this ?

Maybe it is already the case and I have forgotten something ?

Pascal

[Dj-Grobe]

Imposible import sites form any of my old server, udpated to rc3 on my new servers with iworx rc3 too

Failure
Archive file : /tmp/cpbfn7Fjg..tgz
Working directory : /tmp/siteworximportx6mOEA
Archive extracted successfully
Setting IP address : 64.******
Setting old base directory : /home/*****
Loaded Domain : ******
Setting backup options : ALL
Loaded package option : E-mail Boxes => 50
Loaded package option : MySQL Databases => 10
Loaded package option : Subdomains => 0
Loaded package option : FTP Accounts => 50
Loaded package option : CGI Access => 1
Loaded package option : E-mail Aliases => 999999999
Loaded package option : E-mail Groups => 0
Loaded package option : Bandwidth => 4.93
Loaded package option : Storage Space => 222.6
Loaded package option : Save Web Transfer Logs => 0
Loaded package option : Burstable => 0
Loaded package option : MySQL Users => 1
Loaded package option : Resolve DNS Names => 0
Loaded package option : E-mail Autoresponders => 999999999
Loaded package option : Pointer Domains => 0
Loaded package option : Crontab Access => 0
Loaded package option : SSL Access => 0
Loaded package option : ScriptWorx => 0
Loaded package option : Account Backup => 1
Loaded package option : Secondary Domains => 0
Loaded master user *************
Master language loaded : en-us
Loaded unix user : onetwoth
Shell is invalid
Loaded e-mail account : ***********[/EMAIL]
Loaded email account preferences : *************[EMAIL="postmaster@123tuweb.com.br"] (postmaster@123tuweb.com.br)
Loaded spam status : Disabled
Loaded MySQL user : ************
Skipping default FTP user
Quota Sanity Checking
Setting Reseller ID : 1


Some idea?
What cause the error?

[IWorx-Socheat]

The backup should add option for skip, any log or stat data..........this in high percent of sites its not critical information, and create big torubels delaying amazing the backup !!!

Please add that feature asap !! its needed........on server with old sites, the backup can be a nightmare !!

Great idea! That's why we already did it ;)

--backup-options all no-logs no-stats

Will tell it to do a full backup, but skip the logs and stats data. We're looking into your import issues right now from your support ticket.

[IWorx-Socheat]

In fact, you give a good way to restore an account on a defined IP, so I think it could be a good idea to give the the ability to backup ALL accounts set on one IP, what do you think about this ?

Maybe it is already the case and I have forgotten something ?

Pascal

This is a good idea, and I've come up with a solution. ~iworx/bin/listaccounts.pex lists all the accounts on the box, and was improved in 3.0 to add some nice features for 3.0 -> 3.0 mass transfers. For example, right now in the v.3.0 RC, you can run:

~iworx/bin/listaccounts.pex --domain --username --email --storage

And this will list all the accounts on the box, 1 per line, displaying the domain name, username, email address, and the storage used of the account, separated by tabs:

$ ~iworx/bin/listaccounts.pex --domain --username --email --storage
domain1.com domainon domain1@hotmail.com 0.7890625
aaa.domain.com aaadomai domain@domain.com 0.15625
aab.domain.com aabdomai domain@domain.com 0.15625
...


It will print the columns in the order you specify. For example, in the above case, it will print the domain name first, TAB, username, TAB, email, TAB, storage.

I've just added the --ip-address paramater to the code, which will allow you to list the IP address of the account:

$ ~iworx/bin/listaccounts.pex --domain --ip-address
domain1.com 192.168.1.166
aaa.domain.com 192.168.1.155
aab.domain.com 192.168.1.155

You could then incorporate this into a bash script using grep and awk to do what you need:

for domain in `~iworx/bin/listaccounts.pex --domain --ip-address | grep 192.168.1.155 | awk '{print $1}'`
do
~iworx/bin/backup.pex --domains=$domain --output-dir=/backups/ip-192.168.1.155
done

[IWorx-Socheat]

Sorry, I should clarify: the --ip-address parameter has been added to the devel code and will be in the next RC (if we do another RC) or the final release.

[IWorx-Socheat]

Anyway not understand why have error when try restore sites on my new servers !
Please iworx guy check te ticket !

This issue has been resolved via support ticket. For some strange reason, all his accounts had no theme info set in the database (a blank field for each user's theme). This was causing problem with imports. After fixing the missing fields, imports are now working correctly again, and the import code has been tweaked to set a default theme if no theme information is found in the backup file.

[Dj-Grobe]

Thankyou socheat, importcode its patched? on my new server? how can translate that fix to my other new servers?

ABout
--backup-options all no-logs no-stats I dfont know about that options already exist that its wonderfull, any way i start thinkinin no use shell, due this ist masive import i plain use panel, due is the best way to see when some site fail in the import. if i use sell, and import 100 sites, and just one fail, i should make visaul revision site per site for see what site fail, form the panel no way to skip logs and stats?

[IWorx-Socheat]

Thankyou socheat, importcode its patched? on my new server? how can translate that fix to my other new servers?

If you have other servers with the same problem, let us know, and we'll fix them. The fix needs to go on the old server, not the new server. The old server was giving the new server incomplete information.

--backup-options all no-logs no-stats I dfont know about that options already exist that its wonderfull, any way i start thinkinin no use shell, due this ist masive import i plain use panel, due is the best way to see when some site fail in the import. if i use sell, and import 100 sites, and just one fail, i should make visaul revision site per site for see what site fail, form the panel no way to skip logs and stats?

No, not at this time. As you probably found, the mass import page is already pretty full with options and is complex enough as it is. We may add the ability to control backup options on the mass transfer page in a future release, if we can do so without turning the mass import page into an airplane dashboard ;)

[Dj-Grobe]

Well another solution for use page import, be delete the stats and logs on old servers....
But i not have idea how make that with script, i trying figure one script can do that in faster way.

Some sugestion?

Right now, i make the list of old servers on the ticket system, in few minutes i repply that ticket, ....some idea about how delete on easy and faster way logs and stats, in masive way?

[IWorx-Socheat]

Here's how you would list all the log dirs and stats dirs:


ls /home/*/var/*/logs
ls /home/*/var/*/stats


You could probably change "ls" to "rm -rf", but I would *be very careful* with that. A simple typo and you could delete a lot more than you wanted. You have been warned. :D

[IWorx-Socheat]

Actually, you'd probably want to do this:


ls /home/*/var/*/logs/*


You don't want to delete the actual logs dir, just the contents.

[Dj-Grobe]

Oh lol, i think * not work on taht way ....jijiji
Really easy way :)
Thankyou


rm -rf /home/*/var/*/logs/*
rm -rf /home/*/var/*/stats/*


ANyway please post for the future, import from webpage need feature for skip logs and stats if needed :)

[Dj-Grobe]

Just edited : )

[IWorx-Socheat]

More bugs !!! pleas esombody form iworx check !!!!

I have ticket opened !!

It's not a bug in InterWorx... :) You are trying to create/import a reseller on an IP that isn't available to resellers. On the IP management page, switch "IP Available to Resellers" to "Yes" and your "bug" will be fixed. ;)

[Dj-Grobe]

Puf, jaaja
Thankyou jaja i fell like dunceeeeeee
Just error, when i setup the new server i fogort sahre the ip !! for resellers lol !!
Thanks : )

[Dj-Grobe]

socheat? when server its SLAVE dns, just need one IP correct? no need 2 ips, correct?

[IWorx-Socheat]

socheat? when server its SLAVE dns, just need one IP correct? no need 2 ips, correct?

The short answer is yes, you only need one IP.

[Dj-Grobe]

I update ticket, now i find aprently little no importnat bug, but bug.
I update teh ticket.
When restroe NAMESERVERS records are duplicated ! :rolleyes:

Import tool bug?

[IWorx-Socheat]

I update ticket, now i find aprently little no importnat bug, but bug.
I update teh ticket.
When restroe NAMESERVERS records are duplicated ! :rolleyes:

Import tool bug?

Yup, we discovered this bug a couple days ago and his been fixed for the next release (RC or final, whichever it is).

[Dj-Grobe]

Anyway this not cause trouble, correct?
Its just one of taht bugs ugly, but not problematic, correct?

After restore few sites now i have this mesage when restart iworx, i not see that mesage hours ago:


iworx-web: Could not determine the server's fully qualified domain name, using 64.******* for ServerName

what is that?

Socheat why not create IRC chat : )
That be great !!

[Dj-Grobe]

Sites restored show horde when use /webmail/

Not see the nice new menu............. :confused:

[IWorx-Socheat]

Anyway this not cause trouble, correct?
Its just one of taht bugs ugly, but not problematic, correct?

Ugly, yes. But, you'll want to delete the duplicate records, but for your particular setup, there's no real rush.


After restore few sites now i have this mesage when restart iworx, i not see that mesage hours ago:


iworx-web: Could not determine the server's fully qualified domain name, using 64.******* for ServerName

what is that?

Don't think I've seen this before. Check that your /etc/hosts looks correct.

Socheat why not create IRC chat : )
That be great !!
No comment. ;)

[IWorx-Socheat]

Sites restored show horde when use /webmail/

Not see the nice new menu............. :confused:

Could your browser possibly be caching the old page?

[Dj-Grobe]

ABout webmail, i fixed, move all sites form old server to new server work very good with mass transfer feature on iworx RC3 :)

Anyway i update ticket, know with just 2 sites have:


FAILIURE Unknown error.


Just that, no more info, just FAILIURE Unknown error. :eek:

[pascal]

This is a good idea, and I've come up with a solution. ~iworx/bin/listaccounts.pex lists all the accounts on the box, and was improved in 3.0 to add some nice features for 3.0 -> 3.0 mass transfers.

I've just added the --ip-address paramater to the code, which will allow you to list the IP address of the account:

$ ~iworx/bin/listaccounts.pex --domain --ip-address
domain1.com 192.168.1.166
aaa.domain.com 192.168.1.155
aab.domain.com 192.168.1.155

You could then incorporate this into a bash script using grep and awk to do what you need:


Ha ha I thought about this way this night during my attempt to sleep :)

Thanks a lot Socheat, it is a great new feature :)

This post was about backup v3 and documentation, but now it is more a "bug" post and an chat between some........ it's a pity, and you'll surely need to update the doc and include all these new infos/examples (pesonnaly sorry for this)

Good Luck ;)

Pascal

[IWorx-Socheat]

ABout webmail, i fixed, move all sites form old server to new server work very good with mass transfer feature on iworx RC3 :)

Anyway i update ticket, know with just 2 sites have:


FAILIURE Unknown error.


Just that, no more info, just FAILIURE Unknown error. :eek:

This issue was resolved via support ticket. Each account was failing during the backup process. The first account failed because one of the databases in the account needs to be repaired (otherwise mysqldump aborts). The second account failed because there are a few corrupted files in that account's mail directory, and the disk needs to be fsck'd (otherwise tar aborts because it's unable to read those corrupt files).

[bear]

Great resource of information in this thread, very useful
thank you

[Dj-Grobe]

Yeps, lot of great info from socheat, and from pascal : )

[bear]

how would i create a daily backup for a mysql dump only, just for one of my accounts to the default backup directory

thank you

[Dj-Grobe]

/home/interworx/bin/backup.pex --domains=domain.com --backup-options all no-logs no-stats --file-path=/xxx/

The sintaxys its 100% ok?

--backup-options all no-logs no-stats

or

--backup-options= all no-logs no-stats

Or its the same?

This backup absolutly included resellers and just skip logs and stats? correct?
Please confirm about correct syntax

[IWorx-Socheat]

--backup-options all no-logs no-stats

That is the correct syntax, without the '='

[IWorx-Socheat]

This backup absolutly included resellers and just skip logs and stats? correct?

That is correct.

[NeilM]

backup.pex --help suggests that you can use %w in the --filename-format parameter to specify the 3 letter day of the week.

I found this gives

##LG_FILENAME_FORMAT_INVALID## : %D.%wand I need to use the usual date formatting option of %a to get this result.

Cheers
Neil

[Justec]

You absolutly right about the time and resource usage the full backup take. We have 300 accounts and it takes 6 hours (100GB of data)

As soon V3 will be out, we'll try the structure only backups + Rsnapshot + Mysql backup script, if it is fine we'll give here the config of rsnapshot and why not a SRPM of a script that do this job

Just a last question about structure only backups. Tell we want to do a full backup, so we do :
1- A rsync or rsnapshot of /home (in /backups for example)
2- A backup of the Mysql database with a mysqldump (with rsnapshot and in /backups)
3- Perform a backup.pex with --structure-only in /backups (like /home/interworx/bin/backup.pex --domains=all --structure-only --output-dir=/backups )

Is that correct ?
Do you suggest to perform first the backups.pex or the rsync ?

I forgot I had the structure only now, going to update my backup script to do this now. I am currently using rsync backup of the DATA. I do not backup the database doing a dump, but rather the database files themselves. I figure that if something happens I will be restoring it to the same MySQL version and worst case scenario I just use the same version to create a dump and then import to new version.

Might need to take a look at rsnapshot as Im doing a very basic mutliday backup with all data instead of using hard links like rsnapshot does. Anyone who is running rsnapshot (Pascal :) ) have any advice for me?