Jump to content

dvenardos

Members
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dvenardos

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. dvenardos

    Cloud Backup Strategy

    Thanks for the response David! I am using the latest version of Retrospect for Windows. To clarify what is happening (for any readers of this post), native compressed SQL Server backups are going to a network file share via the Ola Hallengren SQL Server Maintenance Solution: https://ola.hallengren.com/sql-server-backup.html. The backups are retained for 3 months. Previously we have been doing tape backups via an old version of Symantec Backup Exec and System Center DPM, we are retiring those systems in favor of Retrospect due to numerous issues. However, we are moving to a colocation facility and tape backups are no longer viable. Our current monthly Iron Mountain costs are in the $500 - $700 month range. Looking at the options, Retrospect is not really viable as a cloud tape replacement at this point. It doesn't support AWS tape gateway or StarWind VTL. For this use case I am going to use RClone with the copy command (https://rclone.org/) on an encrypted remote site. This will achieve the objective which is to retain the SQL backups for at least one year. We are going to BackBlaze B2 and I can setup a lifecycle policy to delete old backups. The monthly cost is comparable to Iron Mountain and retrieval fees are also inline with Iron Mountain tape requests.
  2. I am trying to figure out how to backup a Window's network file share to cloud. The network file share is a target for native SQL Server compressed backups handled outside of Retrospect. Example file share path is: \\fileserverX\SQLBackup. The file share contains around 30 TB of backups which represents 3 months of compressed SQL Server backups. The subfolder structure in the file share is: \\fileserverX\SQLBackup\SQLInstanceX. Folders are created inside of SQLBackup for every SQL instance that is being backed up. The backups are automatically pruned after 3 months. I need to archive these native SQL Server backups to cloud and retain them for a minimum of one year, but potentially two. The maximum cloud backup set size is 100 TB and Retrospect supports strongly discourages using a backup set size that large. All I really need to do is encrypt the backups and copy them to cloud storage, they won't ever change once created. I can't really use multiple cloud backup sets because I can't easily subdivide the network share into smaller subfolders. Any ideas on a strategy for archiving this data to cloud?
×