CVS-only backup is often appropriate for development sites. If you are already using CVS and your data is not important, you probably don't need to do anything to back up your files. Just make sure that your current work is checked into the system. You can then roll back based on date - note the current system time, down to the minute. For maximum safety, you can apply a tag to your current files. You will still need to back up your database.

Note that, if you did the CVS options in this document, the /var/lib/aolserver/service0/etc directory is not included in cvs and you may want to add it.

[root root]# su - service0
[service0 service0]$ cd /var/lib/aolserver/service0
[service0 service0]$ cvs commit -m "last-minute commits before upgrade to 4.6"
cvs commit: Examining .
cvs commit: Examining bin
(many lines omitted)
[service0 service0]$ cvs tag before_upgrade_to_4_6
cvs server: Tagging bin
T bin/acs-4-0-publish.sh
T bin/ad-context-server.pl
(many lines omitted)
[service0 service0]$ exit
[root root]# 
su - service0
cd /var/lib/aolserver/service0
cvs commit -m "last-minute commits before upgrade to 4.6"
cvs tag before_upgrade_to_4_6
exit

To restore files from a cvs tag such as the one used above:

[root root]# su - service0
[service0 service0]$ cd /var/lib/aolserver/service0
[service0 service0]$ cvs up -r current
[service0 service0]$ exit
su - service0
cd /var/lib/aolserver/service0
cvs up -r current