Opened 13 years ago
Last modified 9 years ago
#10102 closed task
Mention hotcopy in UPGRADE document — at Version 5
| Reported by: | Thijs Triemstra | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0.5 |
| Component: | admin/console | Version: | 0.12-stable |
| Severity: | minor | Keywords: | |
| Cc: | Thijs Triemstra | Branch: | |
| Release Notes: |
UPGRADE document has a step to backup the environment. |
||
| API Changes: | |||
| Internal Changes: | |||
Description
The trunk/UPGRADE document explains the upgrade process but doesn't reference the hotcopy command as a way to do a backup of the environment (including the database) before doing the upgrade.
Change History (4)
comment:1 by , 11 years ago
| Milestone: | → undecided |
|---|
comment:4 by , 9 years ago
| Milestone: | undecided → 1.0.4 |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
comment:5 by , 9 years ago
| Release Notes: | modified (diff) |
|---|
I'll add as the first step Backup the environment, with a short description of how to do that using hotcopy.
Note:
See TracTickets
for help on using tickets.
All the tickets for {20} from last year have probably been seen multiple times by now, yet are still to be triaged…