LATechNet Managed Backup is a fully managed service that secures your endpoint data with encrypted cloud snapshots, proactive monitoring, regular test restores, detailed audit logging, quarterly reviews, and annual disaster-recovery drills.
Backup Configuration (How we set it up)
1. Configure Backup Settings
-
Action: We sign in to the LATechNet Managed Backup dashboard for each contracted endpoint.
-
How We Do It: In the “Backup” section, we select Cloud as the destination and schedule the job to run daily at 5:00 PM (local device time). We also exclude removable drives so only the main system volumes and critical data are backed up.
-
Verification: We double-check that encryption is enabled and confirm our retention rules match the insurance requirements.
2. Define Retention Rules
-
Action: We establish how long each backup copy is kept.
-
How We Do It:
-
Daily backups are retained for 7 days.
-
Weekly backups are retained for 6 weeks.
-
Monthly backups continue until the 6-month limit is reached.
-
-
Verification: The dashboard’s retention summary shows the correct schedules and counts.
3. Apply Bandwidth Throttling
-
Action: We limit network usage so backups don’t slow day-to-day operations.
-
How We Do It: We set each device to 25 Mbps maximum throughput at all times.
-
Work hours: 7:00 AM–5:00 PM, Monday through Friday
-
Non-work hours: same 25 Mbps cap to maintain consistency
-
-
Verification: We confirm the throttling settings are applied per device and review any network-use alerts.
4. Monitor Backup Jobs
-
Action: We watch each backup run and immediately address any problems.
-
How We Do It: Every morning, we review the jobs dashboard for failed or missed backups and for any jobs that ran longer than expected.
-
Verification: Failed or stalled jobs trigger an alert email; we investigate until the issue is resolved.
5. Verify Backup Integrity
-
Action: We ensure backups remain reliable and restorable.
-
How We Do It: Once per month, we perform a test restore of a sample endpoint to an isolated machine. We check that files open correctly and that applications function as before.
-
Verification: We record each test’s outcome—date, endpoint name, and any discrepancies—in our internal log.
6. Cloud Backup Verification and Testing
-
Action: We confirm cloud backups are accessible and meet our recovery time objectives (RTO).
-
How We Do It: We restore data from the cloud into a virtual test environment, measuring how long it takes and checking data integrity.
-
Verification: We compare actual recovery times against our RTO targets and document results.
Restore Procedure (How We Perform It)
1. Initiate Restore Process
-
Action: We begin recovery when data must be returned.
-
How We Do It: In the LATechNet portal’s “Restore” section, we select the affected device and choose the backup date.
-
Verification: We verify the date and time of the backup before proceeding.
2. Select Backup Source
-
Action: We pick the exact backup set needed.
-
How We Do It: We browse the backup history—choosing either a specific day’s full system image or a point-in-time file set.
-
Verification: We confirm the correct backup source appears in the restore job summary.
3. Choose Restore Location
-
Action: We decide where to put the recovered data.
-
How We Do It: Options include:
-
Original location (overwriting existing files)
-
Alternate folder or test machine (for validation)
-
Full image to a clean endpoint (for total system rebuild)
-
-
Verification: We review the target path or device name before starting.
4. Initiate Restore Job
-
Action: We launch the restoration.
-
How We Do It: Clicking “Start Restore” triggers the job; we monitor its progress on the dashboard.
-
Verification: We watch for any errors and confirm the job completes successfully.
5. Verify Restored Data
-
Action: We confirm data integrity and system functionality.
-
How We Do It: We open representative files, launch key applications, and check system settings and user profiles.
-
Verification: If everything matches the original environment, we mark the restore as verified.
6. Document Restore Completion
-
Action: We log the details for compliance and auditing.
-
How We Do It: We record:
-
Device name or ID
-
Backup date/version
-
Restore start and end times
-
Verification notes
-
-
Verification: The completed log entry is stored in our secure records, ready for any insurance or regulatory review.
Additional Considerations
-
Security & Compliance: Every backup is encrypted in transit and at rest, meeting industry and insurance-carrier standards.
-
Notifications & Reporting: Automated alerts notify our team of any backup or restore issues, and regular reports keep stakeholders informed.
-
Quarterly Reviews: We revisit and update these procedures every quarter to align with changing requirements or best practices.
-
Disaster Recovery Drills: Alongside routine tests, we conduct full DR exercises annually to ensure end-to-end readiness.
Managed Backup Policy Summary
| Activity | Frequency | Time/Window | Notes |
|---|---|---|---|
| Full System Backups | Daily | 5:00 PM (local device time) | Cloud destination; excludes removable drives |
| Retention Pruning | Daily, Weekly, Monthly | N/A | Daily kept 7 days; weekly for 6 weeks; monthly until 6 months |
| Bandwidth Throttling Review | Continuous | 7 AM–5 PM & off-hours (25 Mbps) | Per-device cap; ensures consistent network performance |
| Backup Job Monitoring | Daily | First business hour | Alerts on failures, misses, or long-running jobs |
| Integrity Test Restores | Monthly | Scheduled during off-peak | Test restore to isolated machine; document findings |
| Cloud Recovery Tests | Monthly | Scheduled during off-peak | Measure RTO and data integrity via cloud test restores |
| Procedure & Policy Review | Quarterly | First week of quarter | Update schedules, retention rules, and security settings |
| Full Disaster Recovery Drill | Annually | As scheduled with stakeholders | Simulate end-to-end recovery in a controlled environment |