Hi,

I've a NAS storage with ServerMatrix (on smbackup01). It was down during 5 hours at least on Dec 4th. I asked for a SLA and was told "No SLA on NAS". Okay.

Now I see that there's only 90 GB free on the server although I'm using only 40 of my allowed 80 GB. So if I and some other customers use more storage space, the NAS server will be full.

I think it's time for action ...

What do you think the ticket system is for? Issues with SM and their network + other things such as NAS!

Put a ticket in and ask them to move you to the new NAS system.

Don’t you think they will just add more drives to the array if need be?

No as they are slowly moving people across to the new NAS system which (should) eliminate these problems.

70TB of storage per unit AFAIK.

Do you have to request to be moved to the new system, or will everyone be automatically moved eventually?

They are doing it (to some at least) as a while ago I got an e-mail that they said have moved me to a new NAS.

It sure is needed as my automated backups to NAS are failing more times than they are working. I know many people have exactly the same issue.

All users will be moved to the new NAS in time, but it is a slow process as each customer's data must first be bundled up, shipped over the wire to the new server, and then placed into its new home directory.

In another thread here on this forum, I invited anyone having difficulty with the older NAS systems to open a ticket if they would like to be moved to the new NAS server. This will ensure that those who have problems get moved sooner, rather than later.

It's definitely having some problems tonight. This is as far as I'm getting:

root@xxxxxx [~]# ftp smbackup01.dllstx3.servermatrix.com
Connected to smbackup01.dllstx3.servermatrix.com.
220 ProFTPD 1.2.10 Server (Server Matrix Manual Backup Server dllstx4) [70.85.125.5]
500 AUTH not understood
500 AUTH not understood
KERBEROS_V4 rejected as an authentication type
Name (smbackup01.dllstx3.servermatrix.com:root): cxxxxx-x
331 Password required for cxxxxx-x.
Password:



Then it just sits there....

Tim,

I identified the issue that was causing the trouble, and it has been eliminated. Please let me know with a ticket if this issue re-manifests.