Linux VM: A place to back up MySQL

Source: Veeam

What does it take to back up MySQL on a Linux VM? This is a riddle we sometimes hear at Veeam: When running on a Linux VM, how does one quiesce MySQL databases? Unfortunately, there are not many new ways to answer this riddle, and the answers we currently have are already tried and tested!

The answers can be found in our popular white paper Consistent protection of MySQL/MariaDB with Veeam, written by Solutions Architect Pascal Di Marco. The paper is available for download on our website and describes three different methods for backing up MySQL/MariaDB on a Linux VM. Two hot backup methods running pre- and post-snapshot scripts, and cold backup using database shutdown. This makes use of VMware tools installed on the Linux VM. It is not straightforward like a Microsoft SQL quiescence, because Linux doesn’t have a VSS mechanism like Windows does.

Described are methods of backing up MySQL/MariaDB on a Linux VM using activated scripts local to the database. VMware can run a script to act before the snapshot is created, known as the pre-freeze script and can run a script to do things after the snapshot is created, known as the post-thaw script.

Here’s a quick summary:

Option 1: Hot backup — Database online dump

The mysqldump command copies a database to storage accessible from the MySQL server, taking an online dump of each database without disrupting the MySQL service. This method lets you take a transaction consistent backup of databases but more steps are needed to perform a restore. As with Option 1, the pre-freeze-script will only run if you have the VMware tools running.

Advantage: This allows for 100% uptime; the MySQL service does not stop and the dumped databases are in a transaction-consistent state.

Disadvantage: Depending on the size of your databases, the process may take a considerable amount of time to achieve. A second copy of the database means extra storage space is required to maintain it.

Option 2: Hot backup — Database freezing

Stop the MySQL service for a few moments while the snapshot is created, then start it again. The post-thaw script will not run until the snapshot is created. The pre-freeze script and post-thaw script will only be able to run if you have the VMware tools running in your MySQL server.

Advantage: This is quick and simple, allowing you to take a transaction of all databases with no additional disk usage local to the MySQL server.

Disadvantage: Databases running on the MySQL server will briefly be unavailable, and applications that need 100% uptime may not find this suitable.

Option 3: Cold Backup — Database shutdown

In this method, the application service will be stopped during snapshot creation and restarted once the VM snapshot has been created. It requires permission to start and stop application services but does not require MySQL user permissions. You can authenticate by either using the MySQL default configuration file or hardcoding the username and password in the script.

Advantage: This is easy to set up and doesn’t take extra space. It provides a short RTO, since no further action is required aside from booting the restored guest.

Disadvantage: The databases will be totally unavailable while the guest snapshot is created.


Guest recovery: The cold backup and freeze method will leave the database consistent and able to start up without additional operation, so restoring the VM from the backup files is the only operation to perform. The guest recovery may benefit from Veeam’s Instant VM Recovery feature, which lets you boot up the guest directly from the Veeam Backup Repository in minutes.

Additional dump restoration: The extra task of injecting the dump file into the database using file redirection is necessary if the following is true: The issue is not limited to a database outage, the entire VM must be recovered from the Veeam Backup file and the database dump method has been used.

Veeam U-AIR database restoration: Whether it is a granular or a full database restoration, Veeam U-AIR wizard can be used in conjunction with any relevant database management tool such as MySQL Workbench to recover a database item.


See also:

The post Linux VM: A place to back up MySQL appeared first on Veeam Software Official Blog.

Linux VM: A place to back up MySQL

Restore from a cloud provider with Veeam Agent for Microsoft Windows

Source: Veeam

In my previous blog, we walked through Veeam Agent for Microsoft Windows configurations and ways it provides for backing up data on travelers’ laptops to a cloud provider. Now should you need to recover your data, let’s see how to do it and which options you have with Veeam Agent.

Restoring files and volumes from a cloud backup

Now that we have a full backup in the cloud, we are able to restore individual files along with volumes to our workstation using the Veeam Agent console. To restore individual files, simply open the Veeam Agent console, click on whichever restore point you intend on using, and select the “Restore files” icon. Should you have a need, you can also restore entire volumes from the cloud using the “Restore volume” icon.

Restoring volumes directly from the Agent console can be useful for imaging a secondary or attached drive; however, if the boot volume is in need of restore, we must rely on the Veeam bootable media we created earlier. At its core, Veeam bootable media is nothing but a stripped-down Windows image that includes a number of useful utilities outside of the Veeam functionality.

After booting into the Veeam Recovery Media, we are greeted with the main menu, and can select three options: Bare Metal Recovery, Windows Recovery Environment, and Tools (Figure 1).

Restore from a cloud provider with Veeam Agent for Microsoft Windows

Figure 1. Veeam Recovery Media main menu

Bare Metal Recovery is how we’ll be restoring our volume from the cloud. Windows Recovery Environment allows you to boot into a live version of Windows for use in recovery, but requires a valid Windows image to do so. Tools contains a number of useful utilities that may come in handy during restores.

The following tools are available in the Recovery Media:

  • Command Prompt – Just as you’d expect, this opens a Windows command prompt to run any native Windows commands that would be necessary.
  • Memory Diagnostic – A diagnostic utility for testing system memory.
  • Reset Password – A password reset utility to edit the Windows SAM file and reset local user account passwords.
  • Startup Repair – Windows startup repair utility.
  • Load Driver – Utility used to load storage or networking drivers should they be needed.
  • Export logs – Utility to export logs from the recovery appliance debug to attached storage.

As we can see, there are several incredibly useful utilities included with this bootable media, which makes it even more valuable to carry in your laptop bag.

Now, let’s assume this workstation had a failed hard drive. The new drive has already been replaced, and we’ve booted into our recovery USB media. Restoring the volume is easy, first we’ll head back to the main menu, and select “Bare Metal Restore.” We’re then asked where our backups are located. Since our backups exist in the cloud, we’ll select “Network storage.” Next, we’re asked what type of network storage. In our case, we select “Veeam Cloud Connect Repository.” You can also edit network settings using the “Configure network settings” icon to ensure you have access to the internet. After proceeding and entering the cloud gateway address of our cloud provider, we’ll need to enter the same credentials we initially used to configure our backups. These can be reset by the cloud provider if necessary, but it’s wise to keep them on hand to prevent any delays in the restore (Figure 2).

Restore from a cloud provider with Veeam Agent for Microsoft Windows

Figure 2. Credentials

Next, we’ll be shown any available agent backups in the cloud repository that were created under this specific subtenant account (or a tenant account depending on the user account type and credentials provided). As you can see, in our example, the backup is encrypted. We’ll need to attempt to expand the backup and enter the encryption password before being able to proceed (Figure 3). Unlike Cloud Connect credentials, this password cannot be changed by your service provider, and it’s critical that this encryption password is kept secure. Should this password go missing, there is little that can be done to recover the data inside (hence the nature of encryption).

Restore from a cloud provider with Veeam Agent for Microsoft Windows

Figure 3. Choose the backup

After we’ve entered our backup encryption file and continue to the next screen, we’re asked to choose which restore point we will restore from. Generally, in this instance we’ll be choosing the latest restore point, but in the event we’re restoring from a crypto virus incident we may have to choose an older point (Figure 4).

Restore from a cloud provider with Veeam Agent for Microsoft Windows

Figure 4. Restore point

Finally, we’re asked to select the restore mode. In our case, we have a small workstation with a blank hard drive so we’ll be restoring the entire computer, but notice the two other options available:

  • Restore System Volume – This option should be used if there is a problem with the workstation’s bootable partition, and we only want Veeam to restore the bootable system volume. This is the fastest way to restore a machine, especially if the workstation has a system volume and a data volume. In such an event, we’ll restore the system volume to get the workstation up and running as soon as possible so our user can work, then perform individual file restores or a full volume restore of the data volume using the Veeam Agent console.
  • Manual Restore – “For Advanced Users only” should there be a need to manually edit the partition table of the target disk. There are a number of use cases for this option, namely restoring to smaller or larger drives and adjusting partitions manually.

After selecting “Entire computer,” we simply enter the summary tab and proceed with the restore.  Depending on the size of the image and your bandwidth, this could take quite a bit of time, so it’s best to ensure the workstation is plugged in and has a reliable internet connection.

Wrap up

With our workstation fully restored, we’re now able to remove the bootable media, and our user can continue working as normal in record time. In the past, this same user may have needed to purchase a brand-new machine, remove the inevitable bloatware, re-install all of their applications, and finally download all of their files through the cloud. Since we’re using Veeam Agent for Microsoft Windows however, the entire process comes down to replacing a hard drive, booting from the recovery media, and restoring the backup. Our “road warrior” can now continue on with their travels relatively un-impacted by the loss of a critical workstation component.

The post Restore from a cloud provider with Veeam Agent for Microsoft Windows appeared first on Veeam Software Official Blog.

Restore from a cloud provider with Veeam Agent for Microsoft Windows

Backup to a cloud provider with Veeam Agent for Microsoft Windows

Source: Veeam

One of the best things about Veeam Agent for Microsoft Windows is the ability to back up to and restore from one of the many Veeam Cloud Service Providers. This functionality opens up a new use case for Veeam Agent for Microsoft Windows, the business traveler.

Bridging the Availability Gap for “road warriors”

Anyone who has travelled extensively for work knows the hardships involved in ensuring your local data is secure and recoverable. Laptops, after all, are fragile and susceptible to fatal damage from short falls and bumps. To ensure the highest Availability of local data, a traveler would generally have to utilize two methods of backup: File-level backups to a provider, and volume-level backups to a USB drive. In this case, should data be accidentally deleted or over-written, it would be easy enough to pull down a previous copy using the file-level backup, and in the event of a hardware failure, the volume can be restored to a different hard drive or workstation from the USB drive. While this strategy did work, there are a number of short-falls that lead to an Availability Gap. For starters, travelers may not always have access to the internet, or may choose to disable file-level backups while on metered connections, preventing local backups from running. As for volume backups, USB drives can be cumbersome, require the user to remember to plug them in for backups to run, and not to mention that they are susceptible to being lost or damaged alongside the workstation, rendering the backup useless.

In order to address the issues that plague travelers, Veeam has introduced the following features into Veeam Agent for Microsoft Windows:

  • Backup directly to a cloud provider – This functionality provides the backbone of protecting traveler’s workstations. The user or administrator can now perform backups of the entire computer, individual volumes, or file-level backups, directly to a cloud provider from anywhere in the world with an internet connection.
  • Local backup caching – Having full knowledge that travelers may occasionally find themselves without reliable internet access, Veeam has introduced the ability to create a backup cache on local storage for use during these times. During times of unreliable internet access, Veeam Agent for Microsoft Windows will utilize this local storage to house any new incremental backups. Once unmetered internet access is available, it will immediately push these backups up to the cloud to ensure they are stored safely off-site.
  • Bare metal recovery from a cloud provider – In the event of hardware failure of a local machine, the traveler is able to utilize the Veeam bootable recovery media to connect to their cloud provider from new or replaced hardware, and initialize a full volume restore. You are able to import drivers into the bootable recovery media for easy recover to dissimilar hardware, and as long as there is adequate free space, you can restore to a smaller or larger disk.
  • Cloud provider subtenants – Previously, a cloud provider would generally create a single tenant for a customer with one large quota for all of their backups. To allow for ease of management and user isolation, Veeam has introduced the ability to create sub-tenants. Administrators can now assign individual quotas to each sub-tenant to ensure backup-happy users do not over-utilize all of the available cloud storage, while at the same time ensuring no tenants have access to each other’s backups.
  • Scheduled backups and backup events – For most traveling users, scheduled backups may not always be ideal. Who knows if at 10 PM will be the optimal time to backup, and what happens if the workstation is off at that time? With backup events, Veeam is able to schedule backups automatically if you either lock, or log off of the workstation. You can also force backups to complete if the workstation is powered off during the scheduled backup time, and Veeam will even shut the computer down for you once the backup has finished.

Configuring backups to a cloud provider

Now that we’ve covered all of the great things Veeam Agent for Microsoft Windows has to offer to “road warriors,” let’s go over some best practices for configuring these jobs. If you run into any hiccups, you can always review the Veeam Agent for Microsoft Windows User Guide.

Creating a recovery media

After installing Veeam Agent for Microsoft Windows, you are asked to provide some form of removable media to act as a backup target. Since we’ll be backing up directly to a cloud provider, this is un-necessary and can be skipped. You’ll then be asked to configure your bootable recovery media. In the event of any sort of hardware failure, this media will be used to restore the workstation from any available backups to either similar or dissimilar hardware. Should your organization have standardized hardware, you’ll likely want to choose to create an .iso of the bootable media, however, you may also choose to burn the image directly to an inserted USB key or CD-ROM/DVD. It is critical that this media is distributed to any traveling user. Not only is it vital in performing volume-level restores, but it also includes numerous utilities that will prove useful for system recovery. For our example, we’ll be creating an .iso of the recovery media which can later be burned to external media.

Should you have skipped the initial recovery media creation step, you can also navigate to the “Tools” folder under the Veeam program files entry to start the wizard. The first screen (Figure 1) shows the available options for creating the bootable media. In our example, we see we have a 1GB USB drive, along with the option for creating an .iso image, which we’ve selected. We also have a number of options for this recovery media. I’ve chosen to not include decryption keys in the recovery media for security reasons, and I’ve also chosen to include the network connection settings and hardware drivers for this computer to allow for a seamless restore for my users. You may notice that we can also choose to include additional drivers for storage and network, should we be creating an image for other physical hardware, we can utilize this feature to automatically inject drivers into the recovery media. Don’t fret if you’ve skipped this step as you’ll be able to inject drivers into the bootable recovery media after booting as well.

Backup to a cloud provider with Veeam Agent for Microsoft Windows

Figure 1. Bootable media creation

After configuring our recovery media, we’re prompted to save the .iso. You can either save it locally or choose a CIFS share and enter the credentials needed to connect if necessary.

Click “Next” and you’ll be asked to verify the configuration, and then the .iso file will be created. Just a reminder that it is critical this image be burned to either a CD/DVD or USB and included in all traveling equipment.

Backup configuration

Now that we have the product installed, we’ll be asked to perform an initial backup job configuration. You’ll be prompted for what backup mode you’d prefer. For our purposes, we’ll be choosing an entire computer backup to ensure all of our volumes and files are backed up to the cloud. We’ll also want to choose the “Veeam Cloud Connect Repository” option (Figure 2).

Backup to a cloud provider with Veeam Agent for Microsoft Windows

Figure 2. Backup destination

Under the Service Provider tab, you’ll enter the DNS name or IP address of your preferred service provider, which should be supplied to you upon signing up. You’ll also be asked to supply a port. For our purposes the port will remain the default of 6180, but this may be different depending on the service provider you choose. On the next screen you’ll be asked to enter the credentials for connecting to the service provider. These should also be supplied to you by your chosen Veeam Cloud Connect service provider. In this case, we have a subtenant “bjervis” of the fake company “Jervis Holdings LLC.” Note that subtenant usernames are entered similarly to an Active Directory domain and user account. In this case, the main tenant account is “Jervis Holdings LLC” and the username is “bjervis,” separated by a “” (Figure 3).

Backup to a cloud provider with Veeam Agent for Microsoft Windows

Figure 3. Credentials

Next, we’ll see the allocated backup resources to our sub-tenant. Note that we will only see the resources allocated to the subtenant, and not the full resource allocation of the primary tenant. We can also configure retention period for this backup, which is different than a standard Veeam backup in that it keeps backups based on “how long since the machine has been running.” In this case, if the machine has not checked into the cloud service provider for a lengthy amount of time, backups will not be removed, even if they surpass the retention period (Figure 4). We also have the option to configure advanced settings. Here we can configure synthetic/active full backup settings, along with compression, deduplication, and encryption settings. Encryption should be used to secure your data while sending it across the internet, and avoid raw access to your backups for the service provider, however, the administrator should ensure the password is saved in a reliable, secure location. It is never fun having to tell a customer that their backup data is almost useless because they lost their encryption password.

Backup to a cloud provider with Veeam Agent for Microsoft Windows

Figure 4. Backup configuration

Next, we’ll configure our backup cache settings. As mentioned previously, backup cache is a local storage that will be used to store backups in the event a cloud provider is unavailable. In my example, I have a 1 TB spinning hard disk assigned to the D: letter that is separate from the SSD running my OS on C:. Since I’m already low on space on my D: drive, I’ve assigned it a total maximum size of 10 GBs which should be sufficient for the small incremental backups I generate while on the road and unable to connect to an un-metered internet connection. However, if you have the space, it’s wise to keep more space reserved for a cache (Figure 5).

Backup to a cloud provider with Veeam Agent for Microsoft Windows

Figure 5. Backup cache

Finally, we reach the schedule configuration. Here we can see I have configured my workstation to backup daily at 12:30 AM. Since I rarely turn my workstation off, even while traveling, this will be sufficient for my needs. However, we can also configure the backups to kick off following a Lock, or Log Off. With our backup configured, we can kick off the initial full backup to the cloud. It is recommended this be performed over an un-metered, fast connection, as once it’s complete we’ll only need to send incremental to the cloud, unless active fulls have been configured to run (not recommended for cloud backup jobs).

Next comes restore from our configured and created cloud backups, and this will be the topic of my next blog — keep your eyes on the Veeam blog and don’t miss it!

The post Backup to a cloud provider with Veeam Agent for Microsoft Windows appeared first on Veeam Software Official Blog.

Backup to a cloud provider with Veeam Agent for Microsoft Windows

Veeam & HPE take recovery to the next level with storage snapshots!

Source: Veeam

Back up is the first step along the journey toward data Availability and backing up data is a day to day task many of us do without knowing it. The real value in those backups is achieving efficient and fast recovery to meet the crucial demands of the business. Over the years Veeam has become synonymous with data Availability and with the integration with Hewlett Packard Enterprise (HPE) storage, users gain industry-leading recovery capabilities to minimize data loss. This integration allows storage snapshots to become more purposeful through Veeam Explorer for Storage Snapshots, Backup from Storage Snapshots and On-Demand Sandbox for Storage Snapshots. Veeam Backup & Replication integrates with HPE 3PAR, Nimble and StoreVirtual snapshot capabilities to create a highly-available, cost effective, efficient environment for storing, protecting and recovering data.

Going one step further by leveraging data

I mentioned that backup was the first step in the journey of data Availability; automation is another step on that journey. The automation part comes here in the form of being able to take those storage-efficient snapshots and put them to use by way of offering them out to development teams in an isolated sandbox environment. The use of the On-Demand Sandbox for Storage Snapshots allows users to test VMs, troubleshoot issues, and perform testing scenarios. If you are already familiar with the On-Demand Sandbox feature, the set-up to utilize the snapshot integration will be similar. You will need to configure a virtual lab, Application group and a SureBackup job.

Leveraging storage snapshots through the On-Demand Sandbox is not the only way you can utilize this snapshot technology. Backup from Storage Snapshots is a way to optimize and enhance VM backups in an easy way. This technology reduces the impact on production data and allows for non-disruptive backups of VMs. With HPE 3PAR and with Nimble Secondary Flash Arrays, Veeam can provide backup from a secondary storage array to reduce impact on the production environment even further.

For Nimble environments, the introduction of the HPE Nimble Secondary Flash Array allows users to utilize this array to be used as a source for backup jobs, eliminating any performance hit on the production infrastructure during the backup window. The backup from the Nimble Secondary storage array is asynchronous, meaning the snapshot is first triggered on the primary array then copied or replicated to the secondary storage array. Snapshots and their replication between the primary array to the secondary array can be orchestrated through Veeam Backup & Replication. Should you want to learn more about Veeam’s integration with Nimble, this blog post is a great source to start. For HPE 3PAR StoreServ, the technology is a little different but can achieve the same outcome. To achieve this with an HPE 3PAR StoreServ array, you need to configure a peer persistence relationship between the two.

Peer Persistence

It’s one thing to be able to offer backup from storage snapshots but to be able to leverage synchronous storage replication technology allowing you to choose to take the backup from one site to another is an additional differentiator that the Veeam and HPE partnership brings to the table. Peer Persistence software allows HPE 3PAR StoreServ systems to act as peers to each other, with both arrays being active, holding primary production volumes and secondary volumes. When Veeam Backup & Replication is configured to use snapshots of secondary volumes, the storage snapshot is triggered directly on the secondary volume, meaning the primary one remains untouched from a backup activity perspective. This technology is not done by Veeam by default but needs to be configured correctly by the user. If you want to learn more about this Veeam configuration, this blog post is a great place to start.

Veeam Explorer for Storage Snapshots

Restoring from a storage snapshot can be a difficult, multi-task process taking quite some time, especially if you wanted to restore specific individual or application objects. The Veeam Explorer for Storage Snapshots takes this manual process and makes it much simpler. Through the Veeam Explorer, IT administrators can browse the storage snapshot to perform fast granular recovery of files and application items, even if these snapshots were not created by Veeam itself. Being able to recover from snapshots allows users to benefit from reduced recovery point objectives for application items.

Veeam Explorer for Storage Snapshots

How it works

Veeam Explorer allows users to perform Instant VM Recovery, file-level restore, application items restore including objects from Microsoft Active Directory, Exchange, SharePoint, SQL Server, along with Oracle databases. Visit our Veeam Explorer for Storage Snapshots tool page to learn more!

… and it’s FREE!

It’s important to note that Veeam Explorer for Storage Snapshots is available in Veeam Backup Free Edition. This allows you to maximize your storage investments, making storage snapshots more useful in your environment with the recovery features the free edition has to offer. The functionality in the free edition allows you to utilize Instant VM Recovery, which once prompted can get machines up and running in minutes. Additionally, you can restore files and most application items through Veeam Explorer for Storage Snapshots. If you want to learn more about what the free edition has to offer, check out Hitchhiker’s Guide to Veeam Backup Free Edition.

The post Veeam & HPE take recovery to the next level with storage snapshots! appeared first on Veeam Software Official Blog.

Veeam & HPE take recovery to the next level with storage snapshots!

Getting started with Veeam Explorer for Microsoft SQL Server

Source: Veeam

Believe it or not, I used to work a lot with Microsoft SQL Server. While I did not call myself a database administrator (DBA), I did know my way around a database or two. Since I’ve been at Veeam, I have always enjoyed telling the Veeam story around using SQL Server as a critical application that needs the best Availability options.

That’s why I took particular interest in Veeam Explorer for Microsoft SQL Server that came in Veeam Backup & Replication. Veeam Explorer for Microsoft SQL Server allows application-specific restores of SQL databases, and also contents of tables, objects such as stored procedures, views and more. Additionally, you can also restore the databases to a specific transaction.

This is a great combination of functionality from the established application-aware image processing with a dedicated tool for database restores in Veeam Explorer for Microsoft SQL Server. Additionally, Veeam Backup & Replication and the Veeam Agent for Microsoft Windows also provide an image backup of the entire system.

For those who are not a DBA, sometimes dealing with low-level SQL Server topics can be a bit overwhelming. To help this process, I created a few scripts to help individuals learn this type of interaction with SQL Server. I put three (and a deleted script) up on the Veeam Github site. To use this script, only an S: drive is needed (the path can be changed) to create the sample database and put in a SQL Server Agent job to automatically run a few stored procedures that will insert and delete random data. This creates a database called SQLGREENDREAM.

After running the three scripts to create the database, implement the random number function and set the schedule to create the random data (2 records) and delete 1 record. The SQL Server Transaction Log Backup will show the new database being backed up after the next incremental backup:

Veeam Explorer for Microsoft SQL Server

Once the interval of the SQL Server Agent job runs (12 minutes in the GitHub script) and the Veeam Backup Job interval passes, the most selective restore point option can be selected in Veeam Explorer for Microsoft SQL Server. This selective option, to restore to a specific transaction, is shown in the figure below:

Veeam Explorer for Microsoft SQL Server

Once the interval of the SQL Server Agent job runs (12 minutes in the GitHub script) and the Veeam Backup copy interval process through a time when the test data has been run, the restore to a specific transaction option can be visible to the controlled scripting for the SQLGREENDREAM database in the GitHub repository. Then you can see the records in question being just as scripted, 2 records added then one record deleted. Those entries are done by the SQL Server Agent:

Veeam Explorer for Microsoft SQL Server

From there, the restores can be done with confidence to see how the SQL databases are restored with Veeam. With the sample scripts in the GitHub repository, one can become more comfortable with these restore situations when venturing out of normal comfort zones! If you are using Veeam Backup Free Edition and the SQL Server is a VM being backed up, you can still use Veeam Explorer for Microsoft SQL Server to restore the database to the time of the image-based backup; just no transaction rollback. You can use the NFR program for a fully functional installation also.

Have you used Veeam Explorer for Microsoft SQL Server to restore to a transaction? How did it go? Share your comments below.

The post Getting started with Veeam Explorer for Microsoft SQL Server appeared first on Veeam Software Official Blog.

Getting started with Veeam Explorer for Microsoft SQL Server

Go With Passphrases

Source: SANS security tip
Passphrases are the strongest type of passwords and the easiest to remember. Simply use an entire sentence for your password, such as “What time is coffee?” By using spaces and punctuation, you create a long password that is hard to guess but easy to remember.
Go With Passphrases