Backups

There is a Synology device in the telco rack in Bancroft. Its IP is 192.168.1.55.

As of November 1, 2016, here's the deal:

1. On the OLD server, \\CANAS01\backup is mapped as the Z: drive using caadmin's credentials. A robocopy script copies C:\Users and the entire E: volume to "FSVR - Users" and "FSVR - Data" folders on the backup volume. Jobs are logged to C:\tools\logs. The script is run from Task Scheduler Mondays through Saturdays at 11pm.

NOTE: After a routine reboot in November 2016, the old server failed to mount the Z: drive. I was able to remap it as \\CANAS01 whereas \\192.168.1.55 did not work. WHY??

2. On the NEW server, \\192.168.1.55\backup is mapped as the B: drive using caadmin's credentials. A robocopy script copies C:\Users and the entire D: volume to "CR-2016-SRV-Users" and "CR-2016-SRV-Data" folders on the backup volume. Jobs are logged to C:\tools\logs. The script is run from Task Scheduler Mondays through Saturdays at 9pm.

As of November 23, NO. There had been an iSCSI connection between the old HyperV server and the Synology, so Lucas coopted that and remapped it for CA-2016-SRV to use via iSCSI Initiator and a scheduled Windows Server Backup task which does a disk image + bare metal and server config backup. Really no need for incrementals BECAUSE Shadow Copy is enabled on the server, thus you can right-click any file, Properties, Versions and restore an earlier version. FIXME ask Lucas how to restore when it's been deleted. <- I think you back up to the parent directory first. The other iSCSI LUN, which had been used by fsvr, is still there, but I removed/disabled the fsvr target, so that fsvr can't see it anymore. When/if we want more space, nuke this one.

IN ADDITION to the two 1.5TB iSCSI buckets, the Synology still has the remaining ~6 TB available across three shares: Backups, TechNetArchive, and web (the latter is probably just nonsense from my attempt to use this thing as a webserver.) Both Backups and TechNetArchive are accessible via regular SMB. Both are filled with defunct backups. Check with Amy and delete.

iSCSI crash course:

1. Make the bucket (LUN) on the Syno via Storage Manager

2. Define a target (some very unique string) <- not sure about this part because it was already done when I came along.

3. Go on the server, into Control Panel -> iSCSI initiator, find the Syno, Connect

4. OPTIONALLY, map it to make it visible in the OS. We have deliberately NOT done this so as to "hide" it.

(defunct) scripts are attached here.