3600 appliance opinions

PKH.

this is NOT a recommendation, it is a possibility which can be thought of..please read through the lines....

As i see its getting complicated,

Please PM me for any further points/issues/concerns, this ensures that the Ambiguity in understanding is eliminated and we may be able to help the primary concerns raised by the poster.

Rather making this a platform of mutual influences and moving away from the purpose of original post.

Regards,

Vishal Shinde

Just an FYI, changing the configuration is NOT supported, but the steps mentioned are from the Admin guide for 3600.

This expresses any users thought, knowing the Appliance, as evident from the used cases we have.

Please  do not hastily read the contents in bits and parts and get too anxious to post, please take your time..go through the entire content of what it is all about and them come up with technically relevant content, helpful to reader.

 Again I reiterate do not make this a ground for arguments. It is not really doing any good for the Symantec Brand.

Regards,

Vishal Shinde

An excerpt from my previous comment, for clarity:

===============================================================================

Having said that, we cannot stop a user (need not be a RAID guru) to think

of using Remote management Module to access the Appliance, by making the required changes in the BIOS for the baseboard LAN,Use the RAID web Console 2 utility to re-configure the 4 drives with RAID 0. And use the complete 8 TB of RAW space, but this will be without the parity.

Though not supported , but possible.:)

=============================================================================

I am sure, now that you have read it, you will find that it is neither a recommendation nor a suggestion too.

Just a possibility  ..(which is not supported..)

the steps mentioned are from the Admin guide for 3600.

What steps are you referring to?  Reconfiguring the RAID to RAID 0?

what did you find in Admin guide,in the above context?

We have two 3600 R2 appliances. One acting as a CASO, the other as an MMS. We are using them to backup our servers in one site then replicate to DR before writing to tape. Unfortunately we've been troubleshooting some niggles that have prevented us from going live, but are working on them. For example:

• Some jobs have stopped using client-side de-dupe when they used to use it (not a huge issue, more of an annoyance)
• The throughput on some jobs is very poor while others are great.This hasn't always been the case and we're looking into where the performance drop has come from.
• The change to the job monitor hasn't bothered me too much but it is a bit frustrating having to change the settings across 20 jobs rather than just 1. Am happy though that once it's working we won't have to touch it too much.
• We're also yet to backup to disk, then duplicate, then write to tape as setting up the job schedule is a bit fiddly. Working on that too.
• We also saw the services stopping from time to time. For example on a Monday morning we'd go to check how the backups performed to find the job engine hung on Friday and nothing had happened. I'm hopeful these are 'teething' problems while the system settles down.

We have just updated to SP3 so are keen to see if it helps with the issues above.

I think it's a good system, it just needs time and effort to get it fully going. I don't disagree that you can unbox it and be backing up within an hour but we've found that we're still not at the stage where we can confidently guarantee that it will perform our backups.