I'm gonna order my first dedi box. So one question comes up: How should i partition the HD ? It's a low end box with 120gb HD containing CentOS + Plesk, hosting 4-5 websites, nothing special.
I am asking myself what the best backup strategy for my dedicated server could be. I do not host any commercial website on it (just private ones), but we all know that even losing non-commercial data hurts.
What I already do:
More or less recent backups of the most important websites (just webspace, no email or database) on my local computer Having hardware Raid-1 on the server and 2 HDs Using R1Soft Backup Space provided by my server host
I would like to add some FTP space at an external (!) DC to do scheduled cPanel backups.
I think that a further dedicated server or VPS will not be necessary for this task.
Can you recommend a provider of pure FTP Backup Space which is reliable, at least on a 100 Mbps line and affordable?
I guess I need about 100-200 GB of space to keep daily, weekly and monthly backups.
I am writing a website in PHP and just about make the first version live.
I'm a bit concerned with backups at the moment. I don't want to lose all the data, as a lot of effort will be put into adding content to the site. It uses a MySQL database as well as the file system to store data.
I was just going to do MySQL dumps nightly, but I realized that I know nothing about the topic and therefor should ask advice before writing code in PHP ( which only run for 30seconds max? Is that long enough to backup?)
What is the common practices to do backups on a CMS type site? How often? How do you manage backups? Where do you store them too? Does doing backups effect performance? Do you do full backups or just changes? If I write a backup script, should I try do it in perl/python/bash or stick with PHP?
Or any other information which will fill me with confidence.
We are going to host an application for 20 customers. Our application is related to online order system. We will create 20 virtual host on Windows machine. Application developed in dot Net and database is MS SQL 2005. each client have its own database. I Just want to get an Idea from you people about CPU, RAM, Hard Disk, and Bandwidth.
I am working towards launching a site that, among other things, will be a repository for sensitive data on war crimes. As these crimes are ongoing, and occur in a location where assassinations are endemic, I need to develop a comprehensive security strategy that takes into account all levels of the interface between end user / witness and the site / database itself.
I have considered, but am open to insight and advice on, the following:
1. Data security laws in given countries, in order to ensure the privacy and integrity, as much as possible and away from political / state interference, of data communications. Concerns include the interception of data in transfer and the security of stored data (the United States and the UK are almost certainly cancelled out in this regard. Canada appears significantly better, though Greece, it appears, has the greatest level of legislative protection).
2. Encryption as a technique to ensure the security of transfered and stored data. I am particularly interested in best practice advice on encryption.
3. Javascript as a means to establish a more secure interface between the end user (i.e., the browser interface) and the secured database into which sensitive data will be inputed. Has anyone used this, or other techniques of overcoming the inherent insecurity of the browser interface?
4. Various best practices concerning php, MySQL and Apache security. Any and all advice, or guidelines, welcome.
5. Considerations relative to dedicated hosting, and also colocation hosting as an option.
In general, my problem is to ensure that the identities of witnesses, so much as is technically conceivable, can be protected from extra-judicial interference or surveillance. Nothing about this site will be illegal in any way. The problem is that the witness testimony will be about the actions of a powerful state that has demonstrated its disrespect for law.
Ideally I'd find in these forums a few individuals with whom I could discuss these technical matters off-forum. At the same time, general responses would be values.
The site that I'm building is non-profit (indeed zero budget) and does not represent any political party. It's a people's initiative, against aggressive violence and in support of international law.
I've got another server comming online shortly which will be used for shared hosting. A Q9550, 8 GB DDRs, 2 1 TB SATA drives in RAID 1. I know everyone has different opinions and reasons for their partitioning decisions, so I wanted to get a feel on how you would partition the drives durring setup, and why you would do it the way you do.
I just completed building a server and before sending to the co-lo company I realized that I have to advise them on HD partitioning and I am clueless concerning that.
Would you please share your suggestions on setup?
Hardware:
TYAN S7010 Dual processor Nehalem 5520 12 GB RAM Kingston ECC 4 X 1 TB WD RE3 Hard Drives Seasonic 520 Watt PS Chenbro RM 11704 1U Case
Control Pancel - CPanel
Applications - Mostly Blog Type Membership Sites (Joomla & Wordpress). I dont allow upload of photos or video, so its the MYSQL database that will continue to grow because of the article volume.
I have just purchased a "clean" server and I figured I was going to install cpanel on it. My question is; it it possible to successfully re-partition the server after CentOS has been installed on it during setup or does the ISP have to configure the different partitions (I'm guess the last option is the answer, as this would be the most logical way)
I got a new server from Nocster today with a 80GB drive. Went to look at my fee disk space and I notice the largest partition is only 48GB... yuck. Then I noticed the way they partitioned the drive:
This is definately something I'm not used to. Putting all these things on seperate partitions like that is really going to make it difficult for me to utilize all my disk space. On every other server I've had, all the free space was under / with partitions just for /boot and /dev/shm. Is there anyway to fix this without reinstalling the OS?
and the installation can't be completed , it stops at different steps , one time it stops when installing Perl Modules , one time when installing Apache , one time it declares mirror list errors , ...
I have followed a normal installation procedure and before have had successful installations on XEN VPS machines without partitioning the HDD.
I didn't created the partitions as is suggested in cPanel.net guide.
Is it necessary to have different partitions? Can it be the reason of random stop?
We are puting together a Linux Storage server which will have 4 x 1TB SATA Hard Drives connected to Hardware raid configured at level 10.
We plan to use this box initially for NFS services but in the near future iSCSI targets so would like to make a setup optimal the first time.
What is the best way to layout the drive partition’s for this setup? My thought is
-100MB /boot ext3 -Rest in LVM --LVM Group ---LVM001 2048MB SWAP ---LVM002 10GB / ---LVM003 500GB /nfs ---LVM004 500GB /iscsi
Is this an efficient setup and provide a great deal of flexibility down the road? We will end up having more than one iscsi target running on this box in the end. Also does LVM experience a performance hit ?
1) I have one 80Gb HDD and one 250Gb HDD ( all are s-ata ). In which practical way they should be partitioned? I thought to setup OS on 80Gb HDD and /home on 250Gb HDD.
2) Which version of CentOS is currently the most stable for cPanel? I had an experince with CentOS 5, there were various problems with mail and mysql.. And now I want to install CentOS 4.6.