1 00:00:00,090 --> 00:00:00,930 In this lesson, 2 00:00:00,930 --> 00:00:02,850 we're going to cover data backups. 3 00:00:02,850 --> 00:00:03,900 When it comes to data, 4 00:00:03,900 --> 00:00:06,120 our golden rule is to never put all of our eggs 5 00:00:06,120 --> 00:00:07,200 in one basket. 6 00:00:07,200 --> 00:00:08,340 And so in terms of data, 7 00:00:08,340 --> 00:00:09,750 we should never keep all of our data 8 00:00:09,750 --> 00:00:11,550 on a single device or server, 9 00:00:11,550 --> 00:00:14,250 otherwise it could be lost due to an accidental deletion 10 00:00:14,250 --> 00:00:16,530 or the system failing prematurely. 11 00:00:16,530 --> 00:00:18,750 To prevent our data from being inadvertently lost, 12 00:00:18,750 --> 00:00:20,460 it's always considered to be a best practice 13 00:00:20,460 --> 00:00:22,170 to maintain backups of your data. 14 00:00:22,170 --> 00:00:24,360 And in the case of extremely important data, 15 00:00:24,360 --> 00:00:26,190 you should actually create multiple backup copies 16 00:00:26,190 --> 00:00:27,630 of that data too. 17 00:00:27,630 --> 00:00:30,480 So what exactly is a data backup? 18 00:00:30,480 --> 00:00:31,500 Well, a data backup 19 00:00:31,500 --> 00:00:33,390 is the process of creating duplicate copies 20 00:00:33,390 --> 00:00:34,560 of digital information 21 00:00:34,560 --> 00:00:36,840 to protect it against data loss, corruption, 22 00:00:36,840 --> 00:00:38,280 or unavailability. 23 00:00:38,280 --> 00:00:39,480 So in this lesson, 24 00:00:39,480 --> 00:00:42,150 we're going to cover both onsite and offsite backups, 25 00:00:42,150 --> 00:00:43,170 the recommended frequency 26 00:00:43,170 --> 00:00:44,670 that should be used for your backups, 27 00:00:44,670 --> 00:00:46,290 the use of encryptioning your backups, 28 00:00:46,290 --> 00:00:47,520 the concept of a snapshot 29 00:00:47,520 --> 00:00:49,440 and how it's different from a regular backup, 30 00:00:49,440 --> 00:00:51,180 how data recovery is going to be performed, 31 00:00:51,180 --> 00:00:52,560 how replication occurs, 32 00:00:52,560 --> 00:00:53,700 and how journaling can be used 33 00:00:53,700 --> 00:00:55,740 as a form of data backup too. 34 00:00:55,740 --> 00:00:59,040 First, let's talk about onsite and offsite backups. 35 00:00:59,040 --> 00:01:02,340 An onsite or offsite backup refers to a backup of your data 36 00:01:02,340 --> 00:01:04,860 where it's physically going to be stored in some place. 37 00:01:04,860 --> 00:01:07,470 Now, if you utilize onsite storage to hold your backups, 38 00:01:07,470 --> 00:01:09,390 this means your data will be physically located 39 00:01:09,390 --> 00:01:11,970 within your own data center or office environment. 40 00:01:11,970 --> 00:01:14,130 For example, if you conduct a full backup 41 00:01:14,130 --> 00:01:16,110 of your laptop to an external hard drive, 42 00:01:16,110 --> 00:01:17,670 and then place that external hard drive 43 00:01:17,670 --> 00:01:19,500 in the drawer of your desk in your office, 44 00:01:19,500 --> 00:01:21,480 this would be considered an onsite backup 45 00:01:21,480 --> 00:01:23,160 of your laptop's data. 46 00:01:23,160 --> 00:01:25,440 While having an onsite backup can be really convenient 47 00:01:25,440 --> 00:01:27,240 and it works well if you need to quickly restore some 48 00:01:27,240 --> 00:01:28,890 of those files that were accidentally deleted 49 00:01:28,890 --> 00:01:29,850 from your system, 50 00:01:29,850 --> 00:01:31,110 it is important to remember 51 00:01:31,110 --> 00:01:33,810 that your backed up data might be vulnerable to destruction 52 00:01:33,810 --> 00:01:36,480 in the case of an environmental outage or disaster though 53 00:01:36,480 --> 00:01:37,800 if it's onsite. 54 00:01:37,800 --> 00:01:39,630 For example, if your office building 55 00:01:39,630 --> 00:01:42,150 and its equipment was destroyed due to a fire or a flood, 56 00:01:42,150 --> 00:01:43,860 your backups will also be destroyed 57 00:01:43,860 --> 00:01:46,470 because they were sitting in your desk at that facility, 58 00:01:46,470 --> 00:01:49,020 and they were being kept as an onsite backup. 59 00:01:49,020 --> 00:01:50,580 So to overcome this risk, 60 00:01:50,580 --> 00:01:53,220 we want to utilize offsite backups too. 61 00:01:53,220 --> 00:01:55,260 Now, an offsite backup refers to the practice 62 00:01:55,260 --> 00:01:57,090 of storing duplicate copies of data 63 00:01:57,090 --> 00:01:58,950 at geographically separate locations 64 00:01:58,950 --> 00:02:00,510 from the primary data source 65 00:02:00,510 --> 00:02:01,950 in order to provide you with protections 66 00:02:01,950 --> 00:02:03,330 against physical disasters 67 00:02:03,330 --> 00:02:05,610 and to ensure your data continuity. 68 00:02:05,610 --> 00:02:07,230 Often, these offsite backups 69 00:02:07,230 --> 00:02:09,000 are created using cloud-based servers, 70 00:02:09,000 --> 00:02:11,100 so the data is simply backed up to remote server 71 00:02:11,100 --> 00:02:12,300 over the Internet. 72 00:02:12,300 --> 00:02:14,220 Or you can create a physical backup 73 00:02:14,220 --> 00:02:17,010 of the data using backup tapes or external hard drives, 74 00:02:17,010 --> 00:02:18,510 and then move those things physically 75 00:02:18,510 --> 00:02:21,240 by shipping them to a remote facility for storage. 76 00:02:21,240 --> 00:02:23,340 For example, I used to work as the Director 77 00:02:23,340 --> 00:02:25,440 of a Network Theater Security Operations Center 78 00:02:25,440 --> 00:02:27,600 for the US government during a time of war. 79 00:02:27,600 --> 00:02:29,220 Now, our network's data center was located 80 00:02:29,220 --> 00:02:31,320 within striking distance of our enemy's missiles. 81 00:02:31,320 --> 00:02:35,100 And therefore, we provided both onsite and offsite backups. 82 00:02:35,100 --> 00:02:37,590 Each day, we conducted a nightly onsite backup 83 00:02:37,590 --> 00:02:39,780 of all of our data to removable tapes. 84 00:02:39,780 --> 00:02:42,570 Then, once a week, we actually ship copies of those tapes 85 00:02:42,570 --> 00:02:43,650 to another facility 86 00:02:43,650 --> 00:02:45,570 that was located about a thousand miles away 87 00:02:45,570 --> 00:02:47,700 that was outside of the range of those missiles. 88 00:02:47,700 --> 00:02:50,220 That way, if our facility did come under attack, 89 00:02:50,220 --> 00:02:52,590 all of our data would still be available for restoration 90 00:02:52,590 --> 00:02:55,740 at another data center using those offsite backups. 91 00:02:55,740 --> 00:02:57,030 Now, this was all back in the days 92 00:02:57,030 --> 00:02:59,700 before cloud computing and super fast Internet connections. 93 00:02:59,700 --> 00:03:02,190 So these days, instead, we wouldn't ship those tapes off, 94 00:03:02,190 --> 00:03:04,470 and instead we would simply create a high-speed connection 95 00:03:04,470 --> 00:03:05,790 between the two locations 96 00:03:05,790 --> 00:03:08,280 and perform our offsite backups over the Internet 97 00:03:08,280 --> 00:03:10,350 instead of having to physically ship all those backup tapes 98 00:03:10,350 --> 00:03:12,450 to the remote site each and every week. 99 00:03:12,450 --> 00:03:13,890 Now, the second thing we need to talk about 100 00:03:13,890 --> 00:03:16,470 is the frequency of our backups that we need to consider. 101 00:03:16,470 --> 00:03:17,460 When it comes to determining 102 00:03:17,460 --> 00:03:19,350 how often you need to conduct a backup, 103 00:03:19,350 --> 00:03:21,990 you need to ask yourself one simple question, 104 00:03:21,990 --> 00:03:24,480 how much data am I willing to lose? 105 00:03:24,480 --> 00:03:26,460 Now, if you're willing to lose a week's worth of data 106 00:03:26,460 --> 00:03:28,290 or a day's worth or an hour's worth, 107 00:03:28,290 --> 00:03:30,180 that's going to dictate your backup plans 108 00:03:30,180 --> 00:03:31,800 and the architecture you need to build out 109 00:03:31,800 --> 00:03:33,840 to support your backup strategy. 110 00:03:33,840 --> 00:03:35,610 As you build out your backup strategy, 111 00:03:35,610 --> 00:03:38,280 it's important that you consider your organization's RPO, 112 00:03:38,280 --> 00:03:40,050 or recovery point objective. 113 00:03:40,050 --> 00:03:41,970 This will ensure that your backup plan will be able 114 00:03:41,970 --> 00:03:43,620 to maintain the amount of data required 115 00:03:43,620 --> 00:03:44,970 to make sure any data loss 116 00:03:44,970 --> 00:03:48,180 is staying underneath your organization's RPO threshold. 117 00:03:48,180 --> 00:03:49,950 So if your organization is willing 118 00:03:49,950 --> 00:03:52,320 to only accept an hour of data being lost, 119 00:03:52,320 --> 00:03:54,210 then you need to ensure you're conducting backups 120 00:03:54,210 --> 00:03:56,040 at least one time per hour. 121 00:03:56,040 --> 00:03:58,590 If instead, you could lose up to two days worth of data, 122 00:03:58,590 --> 00:04:00,090 you could run your backups every day 123 00:04:00,090 --> 00:04:01,410 or every evening instead. 124 00:04:01,410 --> 00:04:02,820 And that would be totally fine 125 00:04:02,820 --> 00:04:05,400 because you're still underneath the two-day threshold set 126 00:04:05,400 --> 00:04:08,070 as the RPO threshold for your organization. 127 00:04:08,070 --> 00:04:09,540 Now, another consideration is 128 00:04:09,540 --> 00:04:11,250 how frequently your data is going to be changed 129 00:04:11,250 --> 00:04:12,570 inside of your business. 130 00:04:12,570 --> 00:04:14,160 If you change the data every day, 131 00:04:14,160 --> 00:04:16,380 then daily backups may be just fine. 132 00:04:16,380 --> 00:04:17,579 On the other hand, if you're changing 133 00:04:17,579 --> 00:04:19,290 a large amount of data every hour, 134 00:04:19,290 --> 00:04:20,339 then hourly backups 135 00:04:20,339 --> 00:04:22,920 or backups occurring every 30 to 45 minutes 136 00:04:22,920 --> 00:04:25,350 might be more appropriate for your organization. 137 00:04:25,350 --> 00:04:27,390 The key here is to balance your organization's need 138 00:04:27,390 --> 00:04:28,710 for the up-to-date backups 139 00:04:28,710 --> 00:04:30,000 with the amount of resources, 140 00:04:30,000 --> 00:04:31,200 including things like time, 141 00:04:31,200 --> 00:04:33,300 storage space, bandwidth, and cost 142 00:04:33,300 --> 00:04:34,530 that you're willing to assign 143 00:04:34,530 --> 00:04:37,320 to the task of performing all of these backups. 144 00:04:37,320 --> 00:04:39,600 Third, we need to discuss the use of encryption 145 00:04:39,600 --> 00:04:40,800 with your backups. 146 00:04:40,800 --> 00:04:42,960 Now, encryption is a fundamental safeguard 147 00:04:42,960 --> 00:04:44,580 that will help protect your backup data 148 00:04:44,580 --> 00:04:47,520 from unauthorized access and potential data breaches. 149 00:04:47,520 --> 00:04:48,960 By encrypting your backup files, 150 00:04:48,960 --> 00:04:50,700 you can ensure that even if your backup media 151 00:04:50,700 --> 00:04:52,560 or files do fall into the wrong hands, 152 00:04:52,560 --> 00:04:54,570 the data on them will remain unintelligible 153 00:04:54,570 --> 00:04:56,640 without the proper decryption key. 154 00:04:56,640 --> 00:04:58,380 Now, this ensures your sensitive information 155 00:04:58,380 --> 00:05:01,260 remains confidential and safe from prying eyes. 156 00:05:01,260 --> 00:05:02,970 Now, your backups should also use 157 00:05:02,970 --> 00:05:04,260 both data-at-rest encryption 158 00:05:04,260 --> 00:05:06,150 and data-in transit encryption. 159 00:05:06,150 --> 00:05:08,010 Data-at-rest encryption is going to be used 160 00:05:08,010 --> 00:05:10,620 to encrypt the data as it's written to the storage device. 161 00:05:10,620 --> 00:05:12,510 Data-in-transit encryption, on the other hand, 162 00:05:12,510 --> 00:05:13,980 is going to be used to protect the data 163 00:05:13,980 --> 00:05:16,890 during its transmission to or from the backup destination 164 00:05:16,890 --> 00:05:18,600 in order to maintain the confidentiality 165 00:05:18,600 --> 00:05:20,040 and integrity of your backups 166 00:05:20,040 --> 00:05:21,450 while they're moving across your network 167 00:05:21,450 --> 00:05:24,240 or across your system's internal data bus. 168 00:05:24,240 --> 00:05:26,940 Fourth, let's explore how snapshots are going to be used 169 00:05:26,940 --> 00:05:28,590 as a form of data backup. 170 00:05:28,590 --> 00:05:31,410 Now, snapshots are point-in-time copies of your data 171 00:05:31,410 --> 00:05:32,850 that captures a consistent state 172 00:05:32,850 --> 00:05:35,130 that's going to be essentially a frozen in time copy 173 00:05:35,130 --> 00:05:36,390 of your data. 174 00:05:36,390 --> 00:05:37,500 Unlike traditional backups 175 00:05:37,500 --> 00:05:38,880 that involve copying all of your data 176 00:05:38,880 --> 00:05:40,200 at a specific moment, 177 00:05:40,200 --> 00:05:42,060 snapshots are much more efficient 178 00:05:42,060 --> 00:05:43,980 because they're only going to record the changes made 179 00:05:43,980 --> 00:05:45,750 since the previous snapshot. 180 00:05:45,750 --> 00:05:48,660 This efficiency not only reduces your storage requirements, 181 00:05:48,660 --> 00:05:50,760 but it also allows for a quicker backup process 182 00:05:50,760 --> 00:05:53,430 and more frequent capture of any data changes. 183 00:05:53,430 --> 00:05:55,380 Snapshots are particularly valuable for systems 184 00:05:55,380 --> 00:05:57,840 where data consistency is considered to be critical, 185 00:05:57,840 --> 00:06:00,420 such as the inside of databases or file servers, 186 00:06:00,420 --> 00:06:02,310 because this will enable you to restore your data 187 00:06:02,310 --> 00:06:03,750 to a specific point in time 188 00:06:03,750 --> 00:06:06,180 to effectively roll back to a known good state 189 00:06:06,180 --> 00:06:08,040 in case of any kind of data corruption, 190 00:06:08,040 --> 00:06:09,840 accidental deletions, or other issues 191 00:06:09,840 --> 00:06:11,250 that might have occurred. 192 00:06:11,250 --> 00:06:12,570 Fifth, we need to consider 193 00:06:12,570 --> 00:06:14,790 how data recovery is going to be performed. 194 00:06:14,790 --> 00:06:17,100 Recovery is the ultimate goal of any backup strategy 195 00:06:17,100 --> 00:06:18,690 that's used within our organization 196 00:06:18,690 --> 00:06:21,420 because recovery is used to regain access to your data 197 00:06:21,420 --> 00:06:24,240 in the event of a data loss or a system failure. 198 00:06:24,240 --> 00:06:26,610 A well-defined and thoroughly tested recovery plan 199 00:06:26,610 --> 00:06:29,160 is essential for ensuring a swift and effective response 200 00:06:29,160 --> 00:06:31,530 to any unexpected data incidents. 201 00:06:31,530 --> 00:06:33,930 There are several key steps in the data recovery process, 202 00:06:33,930 --> 00:06:35,820 including the selection of the right backup, 203 00:06:35,820 --> 00:06:37,470 initiating the recovery process, 204 00:06:37,470 --> 00:06:40,110 data validation, testing and validation, 205 00:06:40,110 --> 00:06:43,050 documentation and reporting, and notification. 206 00:06:43,050 --> 00:06:45,780 Now, depending on the nature of the data loss or issue, 207 00:06:45,780 --> 00:06:48,270 you must first identify the appropriate backup copy 208 00:06:48,270 --> 00:06:49,530 to restore from. 209 00:06:49,530 --> 00:06:52,020 This selection may involve choosing from a snapshot, 210 00:06:52,020 --> 00:06:54,960 an offsite backup, or another copy onsite 211 00:06:54,960 --> 00:06:57,960 based on the specific circumstances of your organization. 212 00:06:57,960 --> 00:07:00,600 Then once the appropriate backup copy is chosen, 213 00:07:00,600 --> 00:07:02,460 the recovery process will be begun 214 00:07:02,460 --> 00:07:04,530 by accessing the backup storage location 215 00:07:04,530 --> 00:07:07,080 and initiating the restoration of that data. 216 00:07:07,080 --> 00:07:09,150 After that, the data must be validated 217 00:07:09,150 --> 00:07:10,410 to verify the integrity 218 00:07:10,410 --> 00:07:12,840 and consistency of the restored data. 219 00:07:12,840 --> 00:07:14,220 This validation will ensure 220 00:07:14,220 --> 00:07:16,470 that the recovered data matches the expected state 221 00:07:16,470 --> 00:07:19,320 and hasn't been corrupted during the restoration process. 222 00:07:19,320 --> 00:07:21,150 In addition to data validation, 223 00:07:21,150 --> 00:07:24,180 testing the entire recovery process is also essential. 224 00:07:24,180 --> 00:07:26,340 By regularly testing your recovery procedures, 225 00:07:26,340 --> 00:07:29,070 you can help to identify any potential issues or bottlenecks 226 00:07:29,070 --> 00:07:31,860 that may arise during a real recovery scenario. 227 00:07:31,860 --> 00:07:34,500 Next, you must perform documentation and reporting 228 00:07:34,500 --> 00:07:36,870 by keeping detailed records of the recovery process 229 00:07:36,870 --> 00:07:39,900 for post-incident analysis and compliance purposes. 230 00:07:39,900 --> 00:07:41,310 Documenting the steps taken, 231 00:07:41,310 --> 00:07:42,780 the time required for recovery, 232 00:07:42,780 --> 00:07:45,630 and any challenges encountered can provide valuable insights 233 00:07:45,630 --> 00:07:48,360 for refining your backup and recovery strategy. 234 00:07:48,360 --> 00:07:50,730 Finally, depending on the nature of the incident, 235 00:07:50,730 --> 00:07:53,370 it may be necessary to notify relevant stakeholders, 236 00:07:53,370 --> 00:07:55,980 such as information technology teams, management, 237 00:07:55,980 --> 00:07:58,140 or your end users about the data loss 238 00:07:58,140 --> 00:08:00,600 and the progress of your recovery efforts. 239 00:08:00,600 --> 00:08:02,850 Now, ensuring that you can effectively recover your systems 240 00:08:02,850 --> 00:08:05,490 using data backups is also really essential, 241 00:08:05,490 --> 00:08:07,860 because otherwise, your backups are going to be useless 242 00:08:07,860 --> 00:08:09,960 if you're not able to recover the data from them 243 00:08:09,960 --> 00:08:12,090 when a disaster actually occurs. 244 00:08:12,090 --> 00:08:13,830 This is why practicing your data recovery 245 00:08:13,830 --> 00:08:14,910 at least once per month 246 00:08:14,910 --> 00:08:16,380 is considered to be a best practice 247 00:08:16,380 --> 00:08:19,560 in the world of cybersecurity and information technology. 248 00:08:19,560 --> 00:08:21,480 Sixth, we have replication. 249 00:08:21,480 --> 00:08:23,520 Now, replication involves making real-time 250 00:08:23,520 --> 00:08:25,980 or near real-time copies of your data. 251 00:08:25,980 --> 00:08:28,110 Unlike backups which are periodic in nature, 252 00:08:28,110 --> 00:08:29,700 replication will keep your data stored 253 00:08:29,700 --> 00:08:31,620 in two places simultaneously. 254 00:08:31,620 --> 00:08:32,940 If one server crashes, 255 00:08:32,940 --> 00:08:35,309 the other will be able to continue without interruption. 256 00:08:35,309 --> 00:08:37,440 A replication approach is a really good idea 257 00:08:37,440 --> 00:08:39,840 when you're architecting a high availability environment 258 00:08:39,840 --> 00:08:41,850 or for those who cannot afford any downtime 259 00:08:41,850 --> 00:08:44,159 or interruptions to their systems or their data. 260 00:08:44,159 --> 00:08:45,360 One of the primary benefits 261 00:08:45,360 --> 00:08:47,760 of using replication though lies in its ability 262 00:08:47,760 --> 00:08:49,350 to provide seamless data continuity. 263 00:08:49,350 --> 00:08:51,090 So keep that in mind too. 264 00:08:51,090 --> 00:08:52,830 Seventh, we have journaling. 265 00:08:52,830 --> 00:08:54,870 Now, journaling, also known as change tracking 266 00:08:54,870 --> 00:08:57,570 or logging, will involve maintaining a meticulous record 267 00:08:57,570 --> 00:09:00,780 of every change made to an organization's data over time. 268 00:09:00,780 --> 00:09:03,000 This comprehensive journal or log will serve 269 00:09:03,000 --> 00:09:05,460 as a historical account of the data modifications 270 00:09:05,460 --> 00:09:07,170 and will offer valuable insights 271 00:09:07,170 --> 00:09:09,210 to be able to enable the precise data recovery 272 00:09:09,210 --> 00:09:12,120 to a specific point in time if a disaster strikes. 273 00:09:12,120 --> 00:09:14,130 Journaling is really beneficial in scenarios 274 00:09:14,130 --> 00:09:16,800 which require a more granular data recovery capability, 275 00:09:16,800 --> 00:09:18,270 such as during a legal proceeding 276 00:09:18,270 --> 00:09:20,010 or a compliance audit. 277 00:09:20,010 --> 00:09:21,450 With a well-maintained journal, 278 00:09:21,450 --> 00:09:22,410 you're going to be able to track 279 00:09:22,410 --> 00:09:24,390 and roll back individual changes to ensure 280 00:09:24,390 --> 00:09:26,580 that data integrity and compliance is being maintained 281 00:09:26,580 --> 00:09:29,040 within the applicable regulatory standards. 282 00:09:29,040 --> 00:09:31,320 Journaling is a particularly valuable thing to use 283 00:09:31,320 --> 00:09:32,610 inside of your databases 284 00:09:32,610 --> 00:09:33,810 and for critical systems 285 00:09:33,810 --> 00:09:35,100 because it allows an organization 286 00:09:35,100 --> 00:09:36,660 to maintain a detailed audit trail 287 00:09:36,660 --> 00:09:39,780 of all of your data modifications and alterations. 288 00:09:39,780 --> 00:09:41,610 Journaling can be implemented effectively 289 00:09:41,610 --> 00:09:43,770 if you maintain a strong attention to detail, 290 00:09:43,770 --> 00:09:45,030 including selecting the appropriate 291 00:09:45,030 --> 00:09:46,560 data tracking granularity, 292 00:09:46,560 --> 00:09:49,080 managing the journal size and retention policies, 293 00:09:49,080 --> 00:09:52,020 ensuring its security to prevent any kind of tampering. 294 00:09:52,020 --> 00:09:53,280 By embracing journaling as part 295 00:09:53,280 --> 00:09:54,690 of your data management strategy, 296 00:09:54,690 --> 00:09:56,880 you not only enhance data recoverability, 297 00:09:56,880 --> 00:09:58,590 but you also reinforce the accountability 298 00:09:58,590 --> 00:10:01,410 and transparency in your data handling practices. 299 00:10:01,410 --> 00:10:03,450 So remember, data backups aren't just 300 00:10:03,450 --> 00:10:05,310 about copying your organization's data, 301 00:10:05,310 --> 00:10:06,540 but they're also focused instead 302 00:10:06,540 --> 00:10:08,910 on creating a robust, multi-layered strategy 303 00:10:08,910 --> 00:10:10,950 to combat any potential data loss. 304 00:10:10,950 --> 00:10:12,900 Data backup plans are created by mixing 305 00:10:12,900 --> 00:10:14,340 and matching different techniques, 306 00:10:14,340 --> 00:10:16,380 including onsite and offsite storage, 307 00:10:16,380 --> 00:10:17,760 setting the right frequency, 308 00:10:17,760 --> 00:10:20,430 encrypting your sensitive data, using snapshots, 309 00:10:20,430 --> 00:10:21,540 planning and recovery, 310 00:10:21,540 --> 00:10:24,000 and maybe even incorporating replication and journaling 311 00:10:24,000 --> 00:10:26,190 into your organization's backup strategy. 312 00:10:26,190 --> 00:10:28,440 By understanding and implementing these concepts, 313 00:10:28,440 --> 00:10:29,970 you're not just backing up data, 314 00:10:29,970 --> 00:10:32,040 but you're also securing your business's continuity 315 00:10:32,040 --> 00:10:34,050 and integrity well into the future. 316 00:10:34,050 --> 00:10:36,630 After all, in today's modern digital environments, 317 00:10:36,630 --> 00:10:37,980 there is nothing more valuable 318 00:10:37,980 --> 00:10:39,543 than your organization's data.