• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Additional disk drives

S

Strider@

Guest
I'm new to Plesk and *nix coming from an M$ background and I'm having a little trouble understanding how Plesk handles additional disk drives. I've searched all the forums here but can't seem to find an answer.

The original Plesk installation was on a 80Gb drive and I have added an additional 160Gb drive to the server, this is device ad4, with ad0 being the original disk. The drive is mounting to /storage, and here is where my knowledge of FreeBSD and Plesk falls down.

The server stores downloadable digital media from a web application in the directory /usr/local/psa/home/vhosts/domanin_name/subdomains/store and this sits on device ad0, but will Plesk recognize the device ad4 and the mount point /storage as additional disk storage space when the ad0 device becomes full? I expect to fill the disk space rapidly and will need to keep adding drives. I think I'm missing a fundemental link here somewhere. Can someone please help me get my head around this?

Thanks

Paul.
 
Can anyone help please?

I know this might sound like a dumb request to the Unix techies around here, but I'm new to all this and still learning. So any help would be appreciated.

TIA
 
Well, a really supportive community we have here - NOT! So much for moving to *nix and getting access to all this wonderful online support and help. Looks like I'm another migrating back to M$.

But then looking at the 4 pages of posts with zero replies I'm sure I'm not the only one turned off this "*nix is great" thing. Shocking forum support from SWSoft too. They should look at www.interaktonline.com to see how it should be done.
 
Keep in mind that most people here are not running FreeBSD. It's an entirely different flavor of Linux. Most popular distros for Plesk seem to be Red Hat (Fedora Core, CentOS, RHEL), Suse and Debian. FreeBSD is as different from those as Windows 98 is from XP.

Furthermore, if your enitre search for help started and ended here I pity you. I find that these forums are little more than a tool in a larger toolbox. If you had looked on Google for help I think you might have found it more easily.

best of luck to you with your Windows endeavours.
 
Highland,

Not enough of difference with regard to this posting request I suspect.

No need to pity me. Having searched through the whole of the Plesk site and Googled, and having found nothing helpful for my query I posted here as a last resort. The Plesk manual is next to useless in terms of a user manual.

Yes migrating back to M$ is in fact a better option. For one, the user community is much more tolerant of those trying hard to learn a new op system and control panel.

I see the benefits of *nix, but to be honest the reason most don't switch or return to a previous environment is because of the attitude of the 'gurus' out here who make you feel at best unwelcome, if not stupid. Maybe they should take a look back to when they first got their hands on a new Unix/Linux box. But then I guess to qualify for any type of response you need to have read the whole Unix user manual and spent many hours burning the midnight oil before daring ask a question - and god forbid it be a simple one that wouldn't tax the brains of the elite. It's no wonder that M$ has the huge market share it does, and will remain so as long as this elitist attitude exists in *nix community.

Thanks for replying by the way.
 
Hey Strider,

I agree - free support is not dependable. But, it is free.

Anyhoo, if your still interested in doing this, I would recommend looking at symlinks. This is what I would do:

Create a symlink called "store" in this directory:

/usr/local/psa/home/vhosts/domanin_name/subdomains/

That points to:

/storage/domain_name/subdomain/store/

The Linux command (that I know, might be different for your distro) to do this would be:

ln -s <source> <destination>

Now you can add other domains and subdomains to the storage drive by creating other symlinks. Then when the drive is full, add another one (storage2) and continue creating symlinks.

This is how I'd do it, but some of the more experienced linuxers out there might be able to offer a better solution.

Hope this helps.

Luke Pittman
Catch 22 Media
www.catch22media.com
 
so let me get this straight, you're looking to keep adding storage as you need it by adding hard drives? If you were on Linux, i would say go with LVM.

Personally, I find it easier to repartition the drive and simply move all the data over to the larger drive and remove the old HD. This way you can keep migrating until you reach the largest drives available, 750 G. Copying large volumes is pretty quick but still requires some downtime.

hope you found your answer.
 
Back
Top