Mirfster
Doesn't know what he's talking about
- Joined
- Oct 2, 2015
- Messages
- 3,215
FreeNas Server Specs:
ESXi Server Specs (Houses VM of SME Server):
So anyways, with the systems running I ran the following tests:
iPerf from SME Server to FreeNas Server (Got 8+ GB/Sec, so I was happy about that):
Command: iperf -p 5001 -c 172.20.1.6 -w 512k
Results:
------------------------------------------------------------
Client connecting to 172.20.1.6, TCP port 5001
TCP window size: 244 KByte (WARNING: requested 512 KByte)
------------------------------------------------------------
[ 3] local 172.20.1.5 port 41214 connected with 172.20.1.6 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 9.47 GBytes 8.13 Gbits/sec
DD on FreeNas (64 Gb File - Got ~ 350 MB/Sec)
Command: dd if=/dev/zero of=tmp.bin bs=4096 count=16777216 && sync
Results:
16777216+0 records in
16777216+0 records out
68719476736 bytes transferred in 187.602163 secs (366304288 bytes/sec)
Now, main purpose for all of this was because the SME Server used to take +24 hours to perform an initial Full Backup using DAR. Data on the SME Server is 400 GB.
So, theoretically I was thinking that with a 10 GB Pipe and ~350 MB/Sec write speeds I could drastically cut that time down. Backup is to a CIFs share on the FreeNas Server.
Now the initial backup ran and while it was faster; it wasn't near what I thought it would be. I know that other things may come into play, but it didn't even halve the time...
Report from SME Server (Looks like just below 14 hrs):
==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup of [name removed] started at Wed Nov 11 03:13:04 2015 Destination //172.20.1.6/SMEBackupsCIFs/[name removed]/set1
No existing reference backup, will make full backup Basename full-20151111031304 Starting the backup with a timeout of 24 hours
--------------------------------------------
354816 inode(s) saved
including 0 hard link(s) treated
0 inode(s) changed at the moment of the backup and could not be saved properly
0 byte(s) have been wasted in the archive to resave changing files
0 inode(s) not saved (no inode/file change)
0 inode(s) failed to be saved (filesystem error)
293 inode(s) ignored (excluded by filters)
0 inode(s) recorded as deleted from reference backup
--------------------------------------------
Total number of inode(s) considered: 355109
--------------------------------------------
EA saved for 0 inode(s)
--------------------------------------------
Destination disk usage 473G, 3% full, 16T available Backup successfully terminated at Wed Nov 11 14:56:31 2015
Wondering if I am missing something and will plan on at least doubling the RAM. But would appreciate and other suggestions.
Thanks.
- Chassis: Dell PowerEdge C2100 Server
- Build: FreeNAS-9.3-STABLE-201511040813
- CPUs: 2 - Intel Xeon E5506 SLBF8 2.13GHz/4MB/4.8GTs/Quad Core LGA1366 CPU
- Memory: 24 GB (6x4GB - 2Rx4 PC3-10600R - DDR3 - ECC)
- HBA: Dell H200 Mezzanine - Flashed to LSI 9211-8i IT Mode
- Network (1 GB): 2 - Intel 82576 GB Ethernet
- Running in "Fail-Over" LAGG
- Used just for Production Access
- Network (10 GB): Chelsio 110-1088-30 10GB 2-Port PCI-e HBA Adapter Card with SFP's
- Running in "Fail-Over" LAGG
- Used just for Backup Routine Access
- Is Direct Connected to ESXi Server w/Static IP Assigned (No Switch Involved)
- OS Hard Disk(s): 2 - 120 GB SSD (were a good deal, so I grabbed them...)
- Storage Hard Disk(s): 12 - Hitachi Ultrastar HUA723030ALA640 3TB
- Enterprise Rated 7200RPM 64MB SATAIII (6Gb/s) 3.5"
- Volume: Composed of 2 RAIDZ2 w/6 Disks in each one
ESXi Server Specs (Houses VM of SME Server):
- Chassis: Dell PowerEdge T31o Server
- Build: ESXi/vSphere 5.5 Update 3
- CPUs: 1 - Intel Xeon X3430 2.4GHz/8MB/2.5GTs/Quad Core LGA1156 CPU
- Memory: 32GB (4x 8GB) 800MHz DDR3 SDRAM RAM Memory
- RAID: PERC H700 1GB Cache SAS Raid Controller w/Battery Backup
- Running a RAID 6
- Network (1 GB): 2 - Broadcom NetXtreme Gigabit Ethernet
- Running in "Fail-Over" LAGG (in Virtual Network)
- Used just for Production Access
- Network (10 GB): QLogic QLE8152 10GB Dual Port PCI-E Fibre Channel Host Bus Adapter QLE 8152
- Running in "Fail-Over" LAGG (in Virtual Network)
- Used just for Backup Routine Access
- Is Direct Connected to FreeNas Server w/Static IP Assigned (No Switch Involved)
So anyways, with the systems running I ran the following tests:
iPerf from SME Server to FreeNas Server (Got 8+ GB/Sec, so I was happy about that):
Command: iperf -p 5001 -c 172.20.1.6 -w 512k
Results:
------------------------------------------------------------
Client connecting to 172.20.1.6, TCP port 5001
TCP window size: 244 KByte (WARNING: requested 512 KByte)
------------------------------------------------------------
[ 3] local 172.20.1.5 port 41214 connected with 172.20.1.6 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 9.47 GBytes 8.13 Gbits/sec
DD on FreeNas (64 Gb File - Got ~ 350 MB/Sec)
Command: dd if=/dev/zero of=tmp.bin bs=4096 count=16777216 && sync
Results:
16777216+0 records in
16777216+0 records out
68719476736 bytes transferred in 187.602163 secs (366304288 bytes/sec)
Now, main purpose for all of this was because the SME Server used to take +24 hours to perform an initial Full Backup using DAR. Data on the SME Server is 400 GB.
So, theoretically I was thinking that with a 10 GB Pipe and ~350 MB/Sec write speeds I could drastically cut that time down. Backup is to a CIFs share on the FreeNas Server.
Now the initial backup ran and while it was faster; it wasn't near what I thought it would be. I know that other things may come into play, but it didn't even halve the time...
Report from SME Server (Looks like just below 14 hrs):
==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup of [name removed] started at Wed Nov 11 03:13:04 2015 Destination //172.20.1.6/SMEBackupsCIFs/[name removed]/set1
No existing reference backup, will make full backup Basename full-20151111031304 Starting the backup with a timeout of 24 hours
--------------------------------------------
354816 inode(s) saved
including 0 hard link(s) treated
0 inode(s) changed at the moment of the backup and could not be saved properly
0 byte(s) have been wasted in the archive to resave changing files
0 inode(s) not saved (no inode/file change)
0 inode(s) failed to be saved (filesystem error)
293 inode(s) ignored (excluded by filters)
0 inode(s) recorded as deleted from reference backup
--------------------------------------------
Total number of inode(s) considered: 355109
--------------------------------------------
EA saved for 0 inode(s)
--------------------------------------------
Destination disk usage 473G, 3% full, 16T available Backup successfully terminated at Wed Nov 11 14:56:31 2015
Wondering if I am missing something and will plan on at least doubling the RAM. But would appreciate and other suggestions.
Thanks.
Last edited: