On 5/16/19 4:12 PM, Derek Atkins wrote:
> Jorick Astrego <[email protected]> writes:
>
>> Maybe split it in 2 disks? One OS and one APP/DATA? You can then backup
>> only one.
>>
>> I prefer to do this anyway as I then can just redeploy the OS and attach
>> the second disk to get things back up and running.
> Are you suggesting that /etc and /var should go onto their own disks?
> There is lots of configuration in /etc (which is usually in the root
> disk) that needs to be backed up.
>
> Also, different apps store configuration and data in different places,
> so saying "just put it on a second disk" can be hard.
>
> Sure, it works fine for /home -- but mysql? imapd? ...
>
> -derek
/etc for us is mostly generated by deployment and provisioning, in
production at least so that is not a problem. All changes have to go
through puppet/ansible.
The /var I have been putting on a seperate disk for a long time. And a
lot of VM's have separate disks for /data or /home.
So this combination works for us but it depends on your layout and
whether you have any provisioning/config management tools an procedures
running.
Regards,
Jorick Astrego
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
----------------
Tel: 053 20 30 270 [email protected] Staalsteden 4-3A
KvK 08198180
Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede
BTW NL821234584B01
----------------
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/YEUDZEG6VDQMESWGQ4UJOKS77ACVB6ZW/
