Volume Details and Properties | Storage Info | Nife
Access and understand complete information about your persistent storage volumes.
Viewing Volume Informationβ
Volume List Displayβ
Application Volumes Table
When an application is expanded in the Volumes Dashboard, a table displays all associated volumes with key information:
Table Columns
| Column | Shows |
|---|---|
| Volume Name | Name and identifier of volume |
| Size | Storage capacity in GB |
| Region | Geographic location |
| Created At | Date volume was created |
| Actions | Snapshot management button |
Volume Nameβ
Information Provided
- User-assigned identifier
- Describes volume purpose
- Unique within application
- Helps identify volume type
Common Volume Names
- database - Primary data storage
- logs - Application logs
- cache - Cached data
- uploads - User file uploads
- backups - Backup storage
- temp - Temporary storage
Using Volume Names
- Reference when managing
- Include in documentation
- Use in troubleshooting
- Reference in snapshots
Volume Sizeβ
Size Information
- Allocated storage capacity
- Measured in gigabytes (GB)
- Shows total available space
- Not actual usage amount
Understanding Size
- Larger size = more storage cost
- Application may not use all space
- Can usually be expanded
- May be reduced in some cases
Size Examples
- Small: 10-50 GB (logs, cache)
- Medium: 50-200 GB (database)
- Large: 200-1000 GB (user data)
- Very Large: 1000+ GB (media, archives)
Capacity Planning
- Monitor growth trends
- Plan for expansion
- Prevent running out of space
- Budget for storage costs
Region Informationβ
Geographic Location
- Where volume is physically stored
- Affects data latency
- Impacts compliance requirements
- May influence costs
Region Examples
- US East (us-east-1)
- US West (us-west-2)
- EU West (eu-west-1)
- EU Central (eu-central-1)
- Asia Pacific (ap-south-1)
- Asia Northeast (ap-northeast-1)
Region Considerations
- Should match application region
- Latency critical for performance
- Data residency compliance
- Disaster recovery planning
- Cost variations by region
Creation Dateβ
Timestamp Information
- When volume was created
- Formatted as readable date
- May show timezone
- Helps identify age
Using Creation Date
- Track volume lifecycle
- Identify old volumes
- Plan maintenance windows
- Support historical analysis
- Documentation reference
Application Informationβ
Application Contextβ
Application Details Shown
- Application name
- Current status (running, deployed, etc.)
- Organization ownership
- Deployment regions
Application Name
- Identifies application
- Helps group related volumes
- Reference for support
- Documentation purposes
Status Badge
- Shows application state
- Running = active
- Deployed = ready
- Stopped = offline
- Indicates volume accessibility
Organization
- Which team/organization owns
- Multi-tenancy support
- Access control reference
- Billing attribution
Regions
- Where application is deployed
- May have multiple regions
- Affects volume placement
- Impacts redundancy
Storage Informationβ
Capacity Detailsβ
Total Capacity
- Maximum storage available
- Sum of all allocated space
- Shows configuration
- Basis for cost calculation
Volume Count
- Number of volumes per app
- Shown in badge on application
- Helps identify storage-heavy apps
- Distribution indicator
Storage Typesβ
Persistent Storage
- Durable across restarts
- Survives deployments
- Data preservation
- Application-dependent
Volume Characteristics
- Attached to specific application
- Region-specific
- Backed by cloud provider
- Supports snapshots
Volume Metadataβ
Additional Informationβ
Volume ID (if displayed)
- System-assigned identifier
- Used for API calls
- Reference in support tickets
- Unique across platform
Volume Type (if available)
- Standard vs. premium
- SSD vs. HDD
- Performance tier
- Cost implications
Mount Path (if shown)
- Where volume mounted in application
- File system location
- Application specific
- Configuration reference
Multi-Region Volumesβ
Applications Across Regionsβ
Regional Distribution
- Same application in multiple regions
- Separate volume per region
- Independent snapshots
- Regional isolation
Volume Accessibility
- Volumes region-specific
- Only accessible from local region
- Lower latency access
- Meets data residency rules
Regional Snapshots
- Each region has own snapshots
- Separate snapshot list
- Independent retention
- Regional disaster recovery