Managing Volumes - Create, Expand & Configure Storage | Nife Docs
This guide covers all operations for managing persistent storage volumes for your applications.
Viewing Volumes#
Accessing Volumes Dashboard#
Navigate to Volumes
- From main dashboard, click Volumes in navigation
- Dashboard loads with all applications and their volumes
- Summary cards show volume statistics
- Applications listed with volume counts
Volume List Organization#
Volumes are organized by application:
- Each application shows as a collapsible card
- Displays application name, status, and regions
- Shows count of volumes for each app
- Expandable to see detailed volume information
Expanding Applications#
View Volume Details#
Expand Application
- Locate application in the volumes list
- Click on the application card row
- Application expands to show volume table
- Volume details become visible
- Shows all volumes for this application
What Displays
- Volume name and purpose
- Storage size in GB
- Geographic region
- Creation date
- Snapshot action button
Collapse Application#
Hide Volume Details
- Click the expanded application row
- Application collapses
- Volume details hidden
- Shows only summary information
Volume Information#
Understanding Volume Details#
Volume Name
- User-defined identifier
- Describes the volume's purpose
- Examples: database, logs, cache, uploads
- Must be unique within the application
Volume Size
- Storage capacity allocated
- Measured in GB (gigabytes)
- Affects monthly costs
- Can usually be expanded
Region
- Geographic location of storage
- Matches or near application region
- Affects latency and compliance
- Examples: us-east-1, eu-west-1, ap-south-1
Created At
- Date volume was created
- Formatted as readable date
- Helps track volume age
- Useful for lifecycle management
Creating Volumes#
During Application Creation#
Add Volumes
- When creating new application
- Specify persistent volumes needed
- Define volume name
- Set volume size
- Choose region
Volume Configuration
- Volume name: Descriptive name
- Size: Initial storage capacity in GB
- Region: Geographic location
- Type: Storage type (if applicable)
Adding Volumes to Existing Applications#
Attach New Volume
- Navigate to application settings
- Find Storage/Volumes section
- Click "Add Volume"
- Configure volume details
- Apply changes
- Application may need restart
Configuration Details
- Volume name
- Initial size
- Mount path (if required)
- Region selection
Volume Snapshots#
Snapshot Overview#
Snapshots provide point-in-time backups:
- Capture complete volume state
- Enable quick recovery
- Support disaster recovery
- Useful before major changes
- Can be used to create new volumes
Creating Snapshots#
From Volume Row
- Locate volume in expanded application
- Click "Snapshots" button
- Snapshots dialog opens
- Click "Create Snapshot" button
- Enter snapshot details
Snapshot Creation Dialog
Snapshot Name
- Required field
- Must be unique for the volume
- Descriptive name recommended
- Examples: backup-2024-12-29, pre-update
Snapshot Description (Optional)
- Additional details about snapshot
- Reason for snapshot
- Context about data state
- Helpful for future reference
Creating Snapshot
- Enter snapshot name
- Add description (optional)
- Click "Create Snapshot"
- Snapshot creation starts
- Status shows in snapshots list
Snapshot Status#
Snapshot States
| Status | Meaning |
|---|---|
| Pending | Creation in progress |
| Completed | Ready to use |
| Failed | Creation unsuccessful |
| Restoring | Restore operation underway |
Viewing Snapshots
- Click Snapshots button on volume
- Dialog shows all snapshots
- See snapshot details
- Perform snapshot operations
Snapshot Management#
Snapshot List#
Information Shown
- Snapshot name
- Description (if provided)
- Status (completed, pending, etc.)
- Size in GB
- Creation date and time
Snapshot Table Columns
| Column | Description |
|---|---|
| Snapshot Name | User-defined identifier |
| Description | Optional notes about snapshot |
| Status | Current snapshot state |
| Size | Storage size of snapshot |
| Created | Date snapshot was created |
| Actions | Restore button |
Restoring Snapshots#
Before Restoring
warning
Restoring a snapshot will overwrite current volume data. Ensure you have a backup if needed.
Restore Process
- Open Snapshots dialog for volume
- Locate snapshot to restore
- Click "Restore" button
- Confirmation dialog appears
- Confirm restoration
- Restoration begins
- Wait for completion
Restoration Steps
- Snapshot data is copied
- Current volume data is overwritten
- Application may experience downtime
- Services restart after restoration
- Check application functionality
Restoring Confirmation#
Confirmation Dialog
- Warns about data overwrite
- Shows snapshot being restored
- Asks for confirmation
- Cannot be undone after confirmation
After Restoration
- Volume data returns to snapshot point
- Any changes after snapshot are lost
- Application continues with restored data
- May need service restart
Snapshot Best Practices#
When to Create Snapshots#
Before Major Changes
- Configuration updates
- Application upgrades
- Database migrations
- System patches
- Security updates
Regular Backups
- Daily snapshots for critical data
- Weekly snapshots for non-critical
- Monthly archives for compliance
- Before any risky operation
Recovery Scenarios
- Accidental data deletion
- Data corruption
- Application crash
- Failed update rollback
- Disaster recovery
Snapshot Naming Convention#
Recommended Format
Useful Information
- Date of snapshot
- Purpose of backup
- Related application version
- Recovery priority
Snapshot Retention#
Keep Snapshots For
- Production: 30+ days
- Staging: 14+ days
- Development: 7+ days
- Archive critical: 90+ days
Delete Old Snapshots
- Review quarterly
- Remove unnecessary snapshots
- Free storage space
- Reduce storage costs
Monitoring Volumes#
Volume Growth#
Track Size Changes
- Monitor volume size over time
- Identify growth trends
- Plan capacity upgrades
- Prevent running out of space
When to Expand
- Usage approaching 80% capacity
- Frequent storage warnings
- Growth trend indicates need
- Application requires more space
Application with Volumes#
View Volume Count
- Check badge on application card
- Shows number of volumes
- Updates in real-time
- Helps understand storage needs
Volume Distribution
- See how many volumes per app
- Identify storage-heavy apps
- Plan allocation strategies
- Optimize resource distribution
Volume Deletion#
Removing Volumes#
danger
Deleting a volume is permanent. Ensure all important data is backed up.
Before Deleting
- Create snapshot if data needed
- Export important data
- Notify team members
- Check for dependencies
- Get approvals if needed
Delete Volume
- Navigate to application settings
- Find Storage/Volumes section
- Select volume to delete
- Click "Delete" button
- Confirm deletion
- Volume is removed
After Deletion
- Volume data is permanently lost
- Cannot be recovered without snapshot
- Storage costs cease
- Application behavior changes
Troubleshooting#
Volume Issues#
Volume Not Appearing
- Refresh the dashboard
- Check application status
- Verify application has volumes
- Try different browser
- Contact support if issue persists
Snapshot Creation Failed
- Check available storage
- Verify sufficient disk space
- Confirm volume accessibility
- Review error message
- Try creating snapshot again
Restore Failed
- Check volume status
- Verify snapshot is valid
- Ensure sufficient space
- Check application status
- Review error details
Cannot Access Volume
- Verify application is running
- Check network connectivity
- Confirm proper permissions
- Review security settings
- Check cloud provider status
Volume Operations Summary#
| Operation | Purpose | Prerequisites |
|---|---|---|
| Create Volume | Add persistent storage | Application created |
| View Details | See volume information | Volume exists |
| Create Snapshot | Backup volume data | Volume exists |
| Restore Snapshot | Recover volume data | Snapshot exists |
| Expand Volume | Increase capacity | Volume created |
| Delete Volume | Remove persistent storage | Data backed up |
Best Practices#
- Naming: Use clear, descriptive volume names
- Sizing: Allocate appropriate size for workload
- Snapshots: Create before major changes
- Monitoring: Track volume growth and usage
- Cleanup: Delete unused volumes regularly
- Backup: Maintain snapshot retention policy
- Documentation: Keep records of critical volumes
- Testing: Test snapshot restoration regularly
Summary: Volume Management Workflow#
Managing volumes effectively involves:
- Planning: Determine storage needs based on application requirements
- Creation: Create volumes during application deployment or later
- Configuration: Set appropriate size, region, and naming conventions
- Monitoring: Track usage and plan for growth
- Maintenance: Expand, optimize, or delete volumes as needed
- Documentation: Keep records of all volume configurations
Regular reviews of your volume allocation ensure optimal performance and cost efficiency.
Next Steps#
- Snapshot Management - Backup volumes and implement disaster recovery
- Volume Details - View detailed storage information and properties
- Export and Analysis - Export and analyze volume data for reporting
- Volumes Overview - Return to volumes dashboard guide