Comments on: Druvaa inSync v3.0 Feature List http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/?utm_source=rss&utm_medium=rss&utm_campaign=druvaa-insync-v30-feature-list Enterprise Data Backup and Beyond Thu, 26 May 2011 12:12:19 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Druvaa inSync v3.0 Feature List - Storage Informer http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-278 Druvaa inSync v3.0 Feature List - Storage Informer Tue, 24 Mar 2009 17:54:34 +0000 http://blog.druvaa.com/?p=73#comment-278 [...] Druvaa inSync v3.0 Feature List [...] [...] Druvaa inSync v3.0 Feature List [...]

]]> By: Carlos http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-277 Carlos Mon, 19 Jan 2009 15:56:51 +0000 http://blog.druvaa.com/?p=73#comment-277 Tony, you seem to be an expert on usability and HMI. Very Impressive :) We would work on this and see how much of this can we take care of in v3 Thanks, Carlos (PM, Druvaa) Tony,

you seem to be an expert on usability and HMI.
Very Impressive :)

We would work on this and see how much of this can we take care of in v3

Thanks,
Carlos (PM, Druvaa)

]]> By: Tony http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-276 Tony Fri, 16 Jan 2009 21:06:49 +0000 http://blog.druvaa.com/?p=73#comment-276 ""Usability is the key to success "" On the restore window, 1. No end user help (need a help button that quickly shows end user how to restore their own file/folder). We are open 24/7 in 28 country’s, I don’t want them calling me :) 2. Default restore location is bad, it’s going to the user folder, which most have no idea how to get their form Explorer . My suggestion, Default should be User Desktop inSync Restore (todays date). 3. Also no option to restore to original location, this could be good or bad. 4. Also you can put one line under the buttons as their description But overall I liked SIS .. it backs up lighting fast. - T “”Usability is the key to success “”

On the restore window,

1. No end user help (need a help button that quickly shows end user how to restore their own file/folder). We are open 24/7 in 28 country’s, I don’t want them calling me :)

2. Default restore location is bad, it’s going to the user folder, which most have no idea how to get their form Explorer . My suggestion, Default should be User Desktop inSync Restore (todays date).

3. Also no option to restore to original location, this could be good or bad.

4. Also you can put one line under the buttons as their description

But overall I liked SIS .. it backs up lighting fast.

- T

]]> By: Tony http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-275 Tony Fri, 16 Jan 2009 20:08:25 +0000 http://blog.druvaa.com/?p=73#comment-275 Some usability suggestions - 1. The server GUI does not give a very good on-gui help for storage and profile creation. The user should be guided towards SIS store, when thats your key selling feature 2. The server GUI looks like Windows 3.1 age, needs face-lift. The client GUI is good. 3. Sync Now without the key shows "No server configured". Your software is smart enough to realize nothing was configured. So give me a button to go the configure screen. 4. Now that I think of it, if there is no Key loaded (not configured), Why not go directly to the Conf. Screen. AND for that matter why not show just load key menu in the configuration menu. Anyways you can configure anything without loading the key. 5. Just have the end user prompt to load the KEY, the conf screen has some stuff on there we do not want them to do. - T Some usability suggestions -

1. The server GUI does not give a very good on-gui help for storage and profile creation.

The user should be guided towards SIS store, when thats your key selling feature

2. The server GUI looks like Windows 3.1 age, needs face-lift. The client GUI is good.

3. Sync Now without the key shows “No server configured”. Your software is smart enough to realize nothing was configured. So give me a button to go the configure screen.

4. Now that I think of it, if there is no Key loaded (not configured), Why not go directly to the Conf. Screen.

AND for that matter why not show just load key menu in the configuration menu. Anyways you can configure anything without loading the key.

5. Just have the end user prompt to load the KEY, the conf screen has some stuff on there we do not want them to do.

- T

]]> By: paulg http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-274 paulg Wed, 14 Jan 2009 06:44:57 +0000 http://blog.druvaa.com/?p=73#comment-274 Good point Borja. A good use case for data deduplication is higher retention and a time-period based retention of data and configuration would be good. Any plans for a tape support. You currently have a very basic support for tape. Or, you would only be concentrating on D2D ? Good point Borja. A good use case for data deduplication is higher retention and a time-period based retention of data and configuration would be good.

Any plans for a tape support. You currently have a very basic support for tape. Or, you would only be concentrating on D2D ?

]]> By: Jaspreet http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-273 Jaspreet Wed, 14 Jan 2009 06:27:41 +0000 http://blog.druvaa.com/?p=73#comment-273 Borja, Thanks for the comment and detailed explanation. We are working on disk based archival/replication system to work with current PC backup or future server backup. It would be a good idea to specify a different retention policy for the archival. For example it should be configurable to retain data older than 30 days for next 1 year. Very soon, we would be announcing plans for a server backup offering as well. Jaspreet Borja,

Thanks for the comment and detailed explanation.

We are working on disk based archival/replication system to work with current PC backup or future server backup.

It would be a good idea to specify a different retention policy for the archival. For example it should be configurable to retain data older than 30 days for next 1 year.

Very soon, we would be announcing plans for a server backup offering as well.

Jaspreet

]]> By: Borja http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-272 Borja Tue, 13 Jan 2009 21:14:17 +0000 http://blog.druvaa.com/?p=73#comment-272 Restore-Point Archival Option: Oposite to Restore-Point Deletion available today, Restore-Point Archival is a feature that will provide a Historycal Archive of customer's data providing at the same time an adequate ratio of storage amount used by the client. The idea behind, beyond the amount of days restorepoints are kept in the server and that is defined at user-group level, is to be able to have a yearly, monthly or weekly single Restorepoint for backups over the provided default retention time. Let's put an example of what could be achieved: Retention policy is set up for 30 days. Archival is configured for weekly+monthly+yearly After 18 months the Restorepoints available would be: - all the restorepoints of the last 30 days. - 4 weekly restorepoints (1 per each previous 4 weeks to these 30 days) - 12 montly restorepoints (1 per each previous 12 monts) - 1 Yearly restorepoints. So regardless the backup is performed every 20 minutes, with just 17 Restore-points extra the customer can get a good archival system. This feature would be really appreciated I guess in Server Backups. Restore-Point Archival Option:
Oposite to Restore-Point Deletion available today, Restore-Point Archival is a feature that will provide a Historycal Archive of customer’s data providing at the same time an adequate ratio of storage amount used by the client.
The idea behind, beyond the amount of days restorepoints are kept in the server and that is defined at user-group level, is to be able to have a yearly, monthly or weekly single Restorepoint for backups over the provided default retention time.
Let’s put an example of what could be achieved:
Retention policy is set up for 30 days.
Archival is configured for weekly+monthly+yearly
After 18 months the Restorepoints available would be:
- all the restorepoints of the last 30 days.
- 4 weekly restorepoints (1 per each previous 4 weeks to these 30 days)
- 12 montly restorepoints (1 per each previous 12 monts)
- 1 Yearly restorepoints.
So regardless the backup is performed every 20 minutes, with just 17 Restore-points extra the customer can get a good archival system.
This feature would be really appreciated I guess in Server Backups.

]]> By: Jaspreet http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-271 Jaspreet Mon, 12 Jan 2009 08:53:17 +0000 http://blog.druvaa.com/?p=73#comment-271 Borja, Thanks for bringing this out. We have some big plans for disaster recovery. You might see some good action on that front pretty soon. Jaspreet Borja,

Thanks for bringing this out.

We have some big plans for disaster recovery. You might see some good action on that front pretty soon.

Jaspreet

]]> By: Carlos http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-270 Carlos Mon, 12 Jan 2009 08:49:03 +0000 http://blog.druvaa.com/?p=73#comment-270 Dave/ Borja, We consciously did not allow name based configurations. Sometimes the internal host name matches to some other server over external link, and then it becomes very difficult to troubleshoot. Lets see if there is an alternative to this and if we can support this in future. Thanks for your comments. Dave/ Borja,

We consciously did not allow name based configurations.

Sometimes the internal host name matches to some other server over external link, and then it becomes very difficult to troubleshoot.

Lets see if there is an alternative to this and if we can support this in future.

Thanks for your comments.

]]> By: Borja http://blog.druva.com/2008/12/22/druvaa-insync-v30-feature-list/#comment-269 Borja Mon, 12 Jan 2009 08:31:00 +0000 http://blog.druvaa.com/?p=73#comment-269 What about the inSync Server protection itself?. I'm missing an fully automated solution where the server itself is Automatically Backed-up to a remote location. I don't think that NTBackup (Windows) or TAR (Linux) are good enough if at the end of the day someone needs to carry out a USB device or Tape off-site. What about the inSync Server protection itself?.
I’m missing an fully automated solution where the server itself is Automatically Backed-up to a remote location.
I don’t think that NTBackup (Windows) or TAR (Linux) are good enough if at the end of the day someone needs to carry out a USB device or Tape off-site.

]]>