547 |
over network) |
over network) |
548 |
|
|
549 |
=item - usage of C<.md5sum> files (compatible with command-line utility |
=item - usage of C<.md5sum> files (compatible with command-line utility |
550 |
C<md5sum> to keep file between snapshots hard-linked |
C<md5sum>) to keep file between snapshots hard-linked |
551 |
|
|
552 |
=back |
=back |
553 |
|
|
591 |
|
|
592 |
server/c_WinNT_fonts/yyyymmdd/.... |
server/c_WinNT_fonts/yyyymmdd/.... |
593 |
|
|
594 |
|
=head2 Won't I run out of disk space? |
595 |
|
|
596 |
|
Of course you will... Snapshots and logfiles will eventually fill-up your disk. |
597 |
|
However, you can do two things to stop that: |
598 |
|
|
599 |
|
=head3 Clean snapshort older than x days |
600 |
|
|
601 |
|
You can add following command to your C<root> crontab: |
602 |
|
|
603 |
|
find /backup/isis_backup -type d -mindepth 3 -maxdepth 3 -mtime +11 -exec rm -Rf {} \; |
604 |
|
|
605 |
|
I assume that C</backup/isis_backup> is directory in which are your snapshots |
606 |
|
and that you don't want to keep snapshots older than 11 days (that's |
607 |
|
C<-mtime +11> part of command). |
608 |
|
|
609 |
|
=head3 Rotate your logs |
610 |
|
|
611 |
|
I will leave that to you. I relay on GNU/Debian's C<logrotate> to do it for me. |
612 |
|
|
613 |
=head1 AUTHOR |
=head1 AUTHOR |
614 |
|
|