Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/18/22 in all areas

  1. Hi, @tommy.cash! As @mark007 mentioned, you should first analyze your company's needs and then the needs of every employee. You should pay attention to the following aspects: business size storage requirements compliance requirements how advanced should be your security features what is the required collaboration level for your environment All of these aspects might help you choose the right option. You can check this blog post to find a detailed description of all the Microsoft 365 enterprise plans https://www.nakivo.com/blog/comparing-microsoft-office-365-enterprise-plans-e1-vs-e3-vs-e5/
    1 point
  2. Hi, @mark007! There are various ways to do that. If you're an end-user, the best solution for you is to use the Outlook web interface. To configure forwarding, follow these steps: In a web browser, open https://outlook.office.com Tap on the Settings (gear) icon to open Office 365 email settings. At the bottom of the Settings menu, select View all Outlook settings. Click on Mail > Forwarding. Check the Enable forwarding checkbox. Enter your destination email address to forward your emails to. Note: It is recommended to check the Keep a copy of forwarded messages checkbox. This way, your emails will be saved in your current mailbox. So, if something goes wrong and the destination email address doesn't receive your messages, you won't lose your emails. Click Save. If you want to use other options (using email client, Office 365 admin center, etc.) for moving your Microsoft Office 365 emails, check this blog post https://www.nakivo.com/blog/how-to-move-office-365-emails-to-other-email-accounts/
    1 point
  3. Hi! @eric_76 @mark007, I wouldn't recommend using snapshots as a backup method for your AWS EC2 instances as it has several limitations, such as: High security risks. If your cloud credentials leak, everything including EC2 instances, volumes and snapshots can be deleted within seconds, resulting in complete data loss and no way to recover it. Very basic retention policy for storing data. You can either keep a long chain of snapshots and overpay for storage or keep a short chain of snapshots and hope the older data won’t be needed. Another option is to spend time on manual snapshot administration. All of the choices aren't efficient. You can't perform granular recovery. EBS volume snapshots are exactly what they sound like: just snapshots. All you can do with a snapshot is restore it to an EBS volume. This means that you cannot perform any kind of granular recovery from the snapshots. AWS snapshots are only crash-consistent. A crash-consistent state is good for file servers, but not for applications and databases, which store portions of data in memory and have incomplete I/O operations at the time a snapshot is made. AWS snapshots store all data without using any data reduction techniques. Therefore, you spend much more money on your storage. For security reasons and budget savings (up to 4x times), I recommend you use a third-party solution. You can check NAKIVO's offer for your Amazon EC2 backup https://www.nakivo.com/aws-ec2-instance-backup/ Let me know if you have more questions.
    1 point
  4. Hi. Before I update to DSM 7.0.1-42218 Update 2 I was wondering if it will cause issues with Nakivo 10.4.0 (build 56979 from 30 Jul 2021). Do I need to update Nakivo first?
    1 point
×
×
  • Create New...