Prerequisites
- Polarion Administrator access or Project Admin role
- SVN client installed (
svn command available)
- Access to the Polarion server’s SVN repository
- Write access to backup storage location (local or network drive)
- For restore operations: empty target project or overwrite confirmation
Backup Project to SVN Export
Step 1: Export the Full Project Repository
# Export entire project to a timestamped backup folder
svn export https://pol2.prod.nextedy.com/svn/Sandbox/TestAuto2 \
/backup/TestAuto2-$(date +%Y%m%d-%H%M%S) \
--username your-username --password your-password
# Result: /backup/TestAuto2-20260215-091500/ (read-only snapshot, no .svn metadata)
SVN access requires active VPN connection to pol2.prod.nextedy.com. The Polarion UI at polarion.demo.nextedy.com is publicly accessible, but SVN operations always require VPN.
Step 2: Verify Backup Completeness
# Check critical directories exist in backup
ls -la /backup/TestAuto2-20260215-091500/
# Expected structure:
# .polarion/ (configuration root)
# .polarion/nextedy/models/ (RTM domain model YAMLs)
# .polarion/nextedy/sheet-configurations/ (Risksheet/PowerSheet YAMLs)
# modules/ (all LiveDoc documents)
# _wiki/ (wiki content)
For large projects (>1000 work items), use svn export with --depth files to backup only configuration first, then --depth infinity for full backup during off-hours to reduce server load.
Step 3: Archive and Compress (Optional)
# Create compressed archive for long-term storage
tar -czf TestAuto2-20260215-091500.tar.gz \
-C /backup TestAuto2-20260215-091500
# Verify archive integrity
tar -tzf TestAuto2-20260215-091500.tar.gz | head -20
Backup Project via SVN Checkout
For projects requiring version history preservation (audit trail, change tracking):
# Checkout full working copy (includes .svn metadata)
svn checkout https://pol2.prod.nextedy.com/svn/Sandbox/TestAuto2 \
/backup/working/TestAuto2 \
--username your-username
# Verify revision number
cd /backup/working/TestAuto2
svn info | grep Revision
# Result: Revision: 4523 (includes full SVN history for restore)
SVN working copies are 2-3× larger than exports due to .svn metadata. A 500 MB export becomes ~1.2 GB as a working copy. Use exports for archival, working copies only when you need commit history.
Restore Project from Backup
Method 1: Restore to New Project (Recommended)
Step-by-step:
# 1. Checkout empty new project
svn checkout https://pol2.prod.nextedy.com/svn/Sandbox/TestAuto2-Restored \
/restore/TestAuto2-Restored
# 2. Copy backup content (preserving structure)
cp -R /backup/TestAuto2-20260215-091500/* /restore/TestAuto2-Restored/
# 3. Add all new files to SVN
cd /restore/TestAuto2-Restored
svn add --force * --auto-props --parents
# 4. Commit restore
svn commit -m "Restore TestAuto2 project from backup 2026-02-15"
# 5. Verify project structure
svn list https://pol2.prod.nextedy.com/svn/Sandbox/TestAuto2-Restored
Method 2: Restore to Existing Project (Overwrite)
This method irreversibly overwrites the target project’s current content. Always backup the current state before proceeding. All work item signatures, approvals, and workflow states from the backup will replace current data.
# 1. Checkout target project
svn checkout https://pol2.prod.nextedy.com/svn/Sandbox/TestAuto2 \
/restore/TestAuto2-overwrite
# 2. Delete all content except .svn
cd /restore/TestAuto2-overwrite
find . -mindepth 1 -maxdepth 1 ! -name '.svn' -exec rm -rf {} +
# 3. Copy backup files
cp -R /backup/TestAuto2-20260215-091500/* .
# 4. Add new files, remove deleted files
svn add --force * --auto-props --parents
svn status | grep '^!' | awk '{print $2}' | xargs svn delete
# 5. Commit overwrite
svn commit -m "Restore project from backup 2026-02-15 (overwrite)"
Post-Restore Verification
Check Configuration Integrity
# Verify critical configuration files exist
ls -la .polarion/polarion-project.xml
ls -la .polarion/nextedy/models/*.yaml
ls -la .polarion/nextedy/sheet-configurations/*.yaml
# Count work item types
grep -r '<work-item ' modules/ | wc -l
# Expected: matches original work item count from dashboard statistics
Reindex Project in Polarion UI
- Log into Polarion as Administrator
- Navigate to Administration → Projects → select restored project
- Click Repository → Reindex Repository
- Wait for indexing completion (check Processing → Background Jobs)
After restore, users must clear browser cache and reload Polarion to see restored risksheet/powersheet configurations. Stale JavaScript modules can cause “configuration not found” errors.
Verify Risksheet/PowerSheet Load
- Open any FMEA risksheet (e.g.,
Risks/HAZID - AEB System)
- Verify column headers render correctly
- Check formula calculations execute (ASIL, Action Priority)
- Open a PowerSheet (e.g.,
Whole RTM Sheet)
- Verify expansion paths work (click ➕ icons)
Backup Strategy Recommendations
| Frequency | Method | Retention | Use Case |
|---|
| Daily | svn export (config only) | 7 days | Configuration changes, risksheet edits |
| Weekly | svn export (full) | 4 weeks | Work item creation, document updates |
| Monthly | svn checkout (with history) | 12 months | Audit trail, regulatory compliance |
| Before Major Changes | svn checkout (full) | Indefinite | Solution updates, RTM model changes |
Schedule automated backups using cron (Linux/macOS) or Task Scheduler (Windows):# /etc/cron.daily/backup-testauto2.sh
#!/bin/bash
BACKUP_DIR="/backup/polarion/TestAuto2"
DATE=$(date +%Y%m%d)
svn export https://pol2.prod.nextedy.com/svn/Sandbox/TestAuto2 \
$BACKUP_DIR/TestAuto2-$DATE \
--username automation-user --password $SVN_PASSWORD --no-auth-cache
find $BACKUP_DIR -name "TestAuto2-*" -mtime +7 -exec rm -rf {} +
Verification
You should now see:
- Backup folder at
/backup/TestAuto2-YYYYMMDD-HHMMSS/ with complete .polarion/ structure
- For restores: Project accessible in Polarion UI with all work items, documents, and dashboards intact
- Risksheet configurations loading without errors
- Traceability coverage metrics matching pre-backup state (check Home Dashboard statistics bar)
See Also
