Celeros EzSANFiler XD Series. Local redundancy and Backup Best Practices

Transcription

1 Celeros EzSANFiler XD Series Local redundancy and Backup Best Practices Last updated April 2009 Celeros Corporation 2008, 2009 All rights reserved

2 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 2 Table of Contents Hardware RAID... 3 Snapshot... 3 Backup and Restore... 8 Local Backup... 8 Restore Dynamic Volume Backup Remote backup to another SAN (through iscsi initiator) Tape Backup... 30

3 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 3 Celeros XD Series provides a variety of data redundancy features to help storage administrators ensure data protection. In this paper, we intend to cover best practices for local redundancy such as RAID and Snapshot as well as different forms of backup to assist the storage administrators. Hardware RAID All Celeros XD Series provide hardware RAID controllers, RAID will provide varying levels of redundancy at disk drive level. For example, RAID-5 group provide a single parity that will allow recovering from a single disk failure; while RAID-6 provides dual parity thus enable recovery from two concurrent disk failures. Celeros supports a number of different RAID groups for different levels of protection and efficiency. For more information on RAID groups please see Snapshot Snapshot is a powerful tool in any storage administrator arsenal. Snapshot provides a frozen image of a point in time of any volume (NAS or SAN) data. Snapshot, effectively, freezes the volume s data to the time the snapshot has taken place. Snapshot is an effective tool for recovering deleted files, virus attack or data preparation for backup. A metadata is created and attached to a volume as part of the process of volume creation on XD Series. Snapshot function takes advantage of this underling data structure by replicating volume s metadata to the snapshot volume. To that end, the snapshot needs to be created and assigned to the volume you intend to protect. For example, if you have a single volume (e.g.: lv000) and you intend to preserve the content of this volume three times a week and keep it for a week. Then you d need to create three snapshot volumes (e.g. snapshot000, snapshot001, snapshot002) and assign all three snapshots to the same volume. Note: once the snapshot volume is created, it s annotated by a capital S, but once the snapshot is attached to a volume, then it s annotated by the volume type and a small s. Once the snapshots have been created and assigned, then you may create schedule that s appropriate for your data protection strategy. In this example, we create a recurring weekly schedule for Monday, Wednesday and Friday that starts at 12:05am and terminate 12:01am.

4 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 4

5 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 5 To take snapshots (on-demand or by a scheduled tasks), select MAINTENENACE > snapshot. To take an on-demand snapshot, select on any snapshot volume. To schedule tasks to take snapshots at different times, expand the list of snapshots by pressing on the plus sign on the left of vg00 on the left pane. Once the list is expanded select a snapshot and schedule as appropriate.

6 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 6 Schedule a weekly snapshot to start every Monday at 12:05am and terminate next Monday at 12:01am; the termination is necessary for the snapshot volume to be available to be renewed for another week in about 4 minutes. The forgoing schedule should be repeated for other snapshots days (e.g. snapshot0001 on Wednesdays and snap0002 on Fridays). Note: Snapshot volume has to be allocated and unused before a snapshot (either on demand or scheduled) is taken. Snapshot status changes to in use/active and a timestamp is added as soon as snapshot is taken to indicate the exact time of the snapshot. In the example below, snapshots 000, 001, 002, 004, 005 are available, while 003 is already in use. In use/active snapshot must either expire or manually stopped ( unused ) prior to taking another snapshot. That s why there is an optional expiration time to accommodate automated scheduled snapshot tasks.

7 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 7 Note: XD Series Backup and Remote Replication takes a snapshot to freeze the volume content prior to staring the backup and replication process. Make sure snapshot is available for the duration of the process. Avoid overlapping snapshots, backup and remote replication task schedules if they share the same snapshot. Either stagger task schedules or create multiple snapshots to avoid overlap. Note: SAN snapshots work the same way, except, it s the storage users responsibility to make sure the application is in a consistent state prior to taking SAN snapshots. For example, acquiesce the database prior to taking snapshot.

8 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 8 Backup and Restore Celeros XD Series provides a built-in backup application to simplify administrator s data protection task. NAS shares and folders maybe backed up to: 1. Local Backup to a second RAID group on the same system 2. Dynamic Volume on the same system 3. Remote backup to another SAN (through iscsi initiator) 4. Tape device attached to the unit through SCSI/SAS interface Local Backup Local backup refers to backing up the data on the primary RAID group to a secondary RAID group within the system. Many find it convenient to create two sets of RAID groups. The primary RAID group is created to hold the data and the secondary RAID group is designated for backup. Usually, the primary RAID group is made up of a more resilient RAID protection such as RAID-10 or RAID-6; and the secondary is a more efficient RAID group such as RAID-5. For example, we created two RAID groups, S001 (a RAID-6 set) and S002 (a RAID-5 set). We allocated the more robust RAID set S001 for data and used RAID set S002 for backup. We then attached each RAID set to a different volume group and name them accordingly ( VolumeGroupDATA and vgbackup).

9 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 9 Then created a NAS and a snapshot volume in VolumeGroupData and attached the snapshot to the NAS volume. We then create a share folder Data on the NAS volume.

10 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 10 Then we create an appropriate size NAS volume on vgbackup volume group as a destination volume for the backup process. Note: Backup destination should be much larger than data to accommodate changes to data overtime. For this example data is 125GB and backup is 400GB.

11 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 11 Then under CONFIGURATION > NAS settings, Local Backup settings is enabled; note the backup database was placed on vgbackup volume group or the destination NAS volume. A Share called DataBackup was also created on vgbackup volume group as a backup virtual tape destination share.

12 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 12 Next step is to create a new backup pool by allocating a name to the pool LocalPool and decide the tape retention period (60 days in this example). Next step is to create a Virtual Tape Backup device using the destination DataBackup share. Note, a Tape Drive device was already available on this system; we ll cover the Tape backup in the next section of this document.

13 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 13 Once VirtualTape device is created, then we create 4 new tapes on the LocalPool.

14 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 14 Next step is to create a Backup Task; by selecting a meaningful task name, select the source logical volume (LvVolumeGroupData00), select the share to be backed up (Data); select the snapshot for the source logical volume (snapvolumegroupdata00); backup level (incremental) and we chose to make a full backup every 10 backups. Note: for the purposes of this example, we chose incremental backup; although you may choose either full or differential; first incremental back up is equivalent to a full back. Also, compression was not selected in this example, you may select to compress as that may provide some space savings. Once the Backup Task (DataBkupTsk) is created, we select the task and assign the desired schedule and start time. In this example we have chosen a daily backup to start at 1am.

15 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 15 Once the schedule is created, it ll appear under Schedules for backup task To see more information, we go back to Backup Tasks and expand the task; it shows the start time, log and a short description of what will be backed up. Note: this task has not been executed yet, so there is no start time and no logs.

16 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 16 Backup task was manually tested at 4:57pm to make sure everything works properly and again it ran automatically on the set schedule. Backup and snapshots generated by backup status maybe viewed at STATUS > tasks

17 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 17 Restore In order to restore a backup volume, we first create a new share ( DataRestore ) on lvvolumegroupdata volume group. Once the share ( DataRestore ) is created, we may select the restore task to restore.

18 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 18 The restore selection criteria are either based on partial backup task name and a possible date range if the number of tasks were too numerous to decide; or a specific backup job date or dates. In the example below we chose all the jobs to be restored to the newly created share DataRestore. In this example, the restore task was performed twice, once at 17:47 and again at 18:01.

19 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 19 All scheduled tasks, including restore tasks may be viewed on STATUS > tasks. To view/copy the restored files, connect to the SANFiler, and then select the DataRestore folder. Each backup job will appear as a separate folder.

20 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 20

21 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 21 Dynamic Volume Backup Dynamic Volume is a special volume type created specifically for backup and restore only; Dynamic volume is the only volume group designed that s capable of being removed and reinserted again into the system. This is intended to create a portable backup media to be shipped outside for safekeeping. First create a pass-through drive or a JBOD drive on the RAID controller. Once the RAID is finished, allocate the new drive to a dynamic volume named dynamicdrive in this example.

22 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 22 Once the volume is created, you may create a new virtual backup device. To do that, select MAINTENANCE > backup > Backup devices and select Dynamic volume and press create. Once the Device is created, you need to create a Backup pool; we called the pool Removable.

23 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 23 Once the Removable pool is created, we ll need to create and assign new Tape to Removable pool. Please note, we limited tape size to the closest size available to the underlying disk capacity. MAINTENANCE >backup>backup devices>dynamicdrive

24 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 24 Once a virtual tape (RemDisk1) has been created, then the Removable backup pool is ready for pool setting criteria such as Tape retention policy and if you plan to use each tape only once. In this example, the retention policy is set to month (30 days) and we left the tape as reusable. Select Use each tape only once if you do not want the drive to be written over once the capacity is reached. The Removable backup pool is now ready to be used in a Backup task and Restore. Backup task and Restore for Dynamic volume are identical to local backup, so we don t repeat those steps here again. You may review Backup task creation and Restore again starting at page 13. Please note Dynamic volumes may come and go; Do Not schedule a backup task if you plan to remove the Dynamic volume.

25 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 25 Remote backup to another SAN (through iscsi initiator) Remote backup could provide a central backup repository for all remote offices NAS folders and share. It could also provide an opportunity to backup to a remote location for better Disaster Recovery. Remote backup procedure is identical to a Local backup except you use the iscsi initiator to attach to a remote SAN and then allocate NAS volume for the backup purpose. First create an appropriate size iscsi volume on the remote SAN you intend to backup to and add the volume to an iscsi target. Then use SETUP>iSCSI initiator and the SAN IP address to connect to the remote SAN. Please note the remote IP address needs to be reachable. If one or both SANs are behind firewall, then you may have to create a secure VPN between the SANs. Once the iscsi connection is established you should see the remote SAN under the portal. Select SETUP>iSCSI initiator>portals> IP address to see all the available volumes on remote SAN. In this example, there are four targets/volumes available on the remote SAN. We selected the remotebackup target as that was designated for remote backup. You may use Challenge Authentication Protocol (CHAP) to provide additional security for the iscsi connection between

26 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 26 the two units. If CHAP is used on that target, then you have to provide the CHAP user and secret to be able to connect to the remote SAN. Once iscsi is connected you d see the target (remotebackup) under the portal. Now if you go to CONFIGURATION>volume manager you ll find a new storage unit (S004) is available under unit Manager.

27 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 27 Add the new unit S004 to a new Volume group, in this example, we called the new volume group RemoteVolume. Once the new volume group is created, assign the entire volume group to a new NAS volume.

28 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 28

29 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 29 Create a share (RBU in this example) and assign it to NAS volume created for the remote backup (lvremotevolume00 in this example).

30 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 30 Again, as with Local backup, once the share was created, you may create Backup pools, devices and tasks. To review creation of backup pools, devices and tasks once again please see page 11. Tape Backup Tape backup is still used in many environments as the sole method of backup and DR. Celeros supports Tandberg StorageLoader LTO-4 a high capacity autoloader (two 4-Slot LTO-4 magazines) capable of storing up to 12.8TB. Although new tape media and tape autoloaders are much more reliable and can restore at high speed, Celeros suggest using Tape backup in conjunction with other backup capabilities for more reliability. XD Series support Tandberg StorageLoader with SCSI or SAS interface. You have to have a Tape SCSI or SAS interface option installed in your XD Series prior to connecting to the Tandberg StorageLoader. We have used a Storage Loader with SCSI interface for this example. Start by loading the tapes into the Storage loader. To load the tapes, affix the bar code labels provided with Tandberg unit to LTO-4 tapes prior to loading the tapes into the magazines. Connect Tandberg StorageLoader to XD Series SCSI interface using SCSI cable and a SCSI bus terminator that s included with your Tandberg unit. Please see Tandberg manual for host connection. Once all LTO-Tapes are labeled and installed in the magazine and cable and termination are installed the unit is ready to be connected to XD Series. Connect the SCSI cable to XD Series, and restart XD (please make sure the Tandberg unit is powered on and all installed tapes are available). Tape Drive will appear in your backup devices once the XD Series is fully booted.

31 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 31 Create a new Backup pool (TapePool in this example); select Tape retention policy and Tape reusability option as appropriate for your environment. Select the tape(s) you plan to add to newly created TapePool (Slot1 in this example), select With erase to clear up previous label on the tape if any and select Label with barcodes (please make sure all labels have barcode prior to loading the tapes) and press apply.

32 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 32 Please note, this process may take a number of minutes, length of this process depends on the size and number of tape you chose to label. Operation in Progress under Label new tapes indicated the tape unit is trying to label the tape you have selected. The Error on Backup Device tapes indicates there are no tapes available as yet (see the screen image below).

33 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 33 Once the labeling process is completed, the labeled tape will appear under Backup device tapes. You may continue to add tapes to your list as long as you have available tapes n the unit.

34 X D S e r i e s D a t a R e d u n d a n c y b e s t p r a c t i c e s P a g e 34 As with other backup capabilities, once the Backup pools and Backup devices have been setup, you may start Backup and Restore tasks. To review that process once again, please refer to page 13.