StorageGuy201

updated

18 years ago

0

951

September 15th, 2008 09:00

Ugh...can't create TimeFinder snap session

I created a VDEV with the same cylinders (127000) as the source device (RAID5 3+1). I then created a brand new SAVE device (2000 cylinders). I then tried to create the snap session using both SMC and SYMCLI:

symsnap -g DG1 create DEV001 vdev ld vdev2 -svp savepooltest

and I got "internal error". Symapi log shows:

===
09/15/2008 09:45:14.921 1200 3568 STARTING a Snap 'CREATE' operation for 1 [SRC-TGT] Pair:
09/15/2008 09:45:14.937 1200 3568 Symm xxxx Number of Pairs: 1 Operation Flags: None
09/15/2008 09:45:14.953 1200 3568 Source-Target Devices: [ 016F-0172 ]
09/15/2008 09:45:14.984 1200 3568 EMC:SMC emcSnapExecuteVdevCm 016F(S)-0172(T), SYMAPI: SYMAPI_C_SNAP_INTERNAL_ERROR, Order17: 0X79, flag: 0X00
09/15/2008 09:45:14.984 1200 3568 EMC:SMC snap_create_this_pai Error returned for device pair 016F(S)-0172(T) - The operation could not be completed because there is no space left on the Save Device(s)
09/15/2008 09:45:15.046 1200 3568 EMC:SMC SymLdevListBcvContro Snap failure with status: SYMAPI_C_SNAP_INTERNAL_ERROR
09/15/2008 09:45:15.046 1200 3568 The Snap 'CREATE' operation FAILED.
09/15/2008 09:45:15.062 1200 3568 The Snap control operation FAILED.
===

How can there be no space left on the Save device when I just created it.
  • MarcT2

    2 Intern

    •

    131 Posts

    452

    0

    Posted September 15th, 2008 10:00

    The save volume is most likely too small.

    I would suggest that your save pool should be approx 10% the size of the source volume(s).

    1 cyl is approx 0.5MB (assuming 32kb tracks, which is what Solutions Enabler works in by default).

    I'd recommend you work with your EMC CE to discuss SNAP sizing requirements & how best to lay out SAV volumes & VDEVs in the binfile.

    M
  • Allen Ward

    6 Operator

    •

    2124 Posts

    452

    0

    Posted September 15th, 2008 09:00

    I have to ask a really annoying question to start...

    Did you actually put the SAV device in the SAVE pool?
  • 452

    0

    Posted September 15th, 2008 10:00

    Yes it's in the pool and enabled.

    Speaking of size, well that's another issue. I have 300G of free space on the system but when I tried to create the SAVE device of (127000 cyls - same as source device) it said "there aren't enough disks to satisfy the raid/mirror requested". I tried RAID 5 and 2 way mirror to no avail. I then deleted a 127000 cyl RAID 5 device and tried to creae the SAVE device again...same exact error which makes no sense. So just for giggles I created a 2000cyl device and bam it did it but now it says the device is full.

    I guess my question should be how to create a SAVE device of 127000 cyls to match the source device? Let me know if you need output from any commands or logs.

    This is just a test snap I'm trying to set up.
  • Allen Ward

    6 Operator

    •

    2124 Posts

    452

    0

    Posted September 15th, 2008 10:00

    Would a SNAP session fail to create because the SAV device is too small? Wouldn't that just cause the session to fail sooner? I know the minimum 10% is a rule of thumb, but is there some hard and fast rule regarding minimum size?
  • Allen Ward

    6 Operator

    •

    2124 Posts

    452

    1

    Posted September 15th, 2008 10:00

    Are you creating your SAV devices RAID 5 or RAID 1. If it is RAID 1, that could explain why removing a RAID 5 STD wouldn't give the capacity required to create a RAID 1 SAV dev.

    Your RAID 5 device is made up of 127000 cyls spread over 3 drives (+1 for parity)... making the hypers approximately 42333 cyls. For a RAID 1 SAV dev of the same size you would need to be able to create 2 hypers that are 127000 cyls each. You don't have enough space on each individual drive to create the size hypers you need.
  • 452

    0

    Posted September 15th, 2008 11:00

    Apparently so. I was able to get it going this time and I made two changes.

    1. The src device was in "Not-Ready" state so I chose a different one that was in the Ready state.
    2. As suggested I bumped up the size to 10000cyls

    One last question, how do you guys manage snapshots automatically for doing backups? Say I have a database that I want to snapshot and then kick off a backup (Netbackup for e.g), then terminate the session? If you guys are using SYMCLI and cron jobs how do you ensure the process is atomic?
  • xe2sdc

    6 Operator

    •

    2831 Posts

    452

    0

    Posted September 15th, 2008 12:00

    The only integration I know is PowerSnap .. That blends symsnap and NetWorker together ;-) .. Anyone have better/different examples ??
  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    452

    0

    Posted September 15th, 2008 13:00

    do you have some kind of job scheduler, something more advanced than cron ? :) ..something like "tivoli workload scheduler" or "control-M" . You can still create bash/korn/perl scripts but use these type of schedulers to create job flows with proper dependencies.