This articles describes the process for backing up instances of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk (hosted on-premise). The example is written using SpiraTeam, but applies equally well to SpiraTest, SpiraPlan or KronoDesk, you just need to change the database name in the SQL files.
We recommend backing up your SpiraTeam installation daily to ensure that in the event of a hardware failure you can always restore your system with as little data loss as possible. There are two parts of the system that need backing up:
- Backup the SQL Server database. This can be done manually by opening SQL Server Management Studio, right-clicking on the database name and then choosing Tasks > Backup Database. You should then perform a 'full backup' of the database to a file device and then copy the backed-up file to a remote storage device.
To perform this on a scheduled basis, if you have SQL Server Standard or Enterprise Edition, then the SQL Server Agent can do this for you. If you are using SQL Server Express Edition, you'll need to use a simple SQL backup script called from a Windows batch file. This batch file can then be scheduled using Windows Scheduled Tasks.
We have some sample backup scripts available at Sample Backup Scripts.zip
- Backup the file attachments. These attachments are stored in the C:\Program Files\SpiraTeam\Attachments folder, and can simply be copied to another remote storage device. This can be done manually using Windows Explorer, or on a scheduled basis by using either Windows Backup or a simple XCOPY command setup in Windows Scheduled Tasks.
Selected files will be attached to any email sent on saving ticket.
There was an error.